Amami MCP docs

Goals and funnels

Pageviews tell you what people saw. Goals and funnels tell you whether the visit produced a useful outcome.

Use goals for business outcomes such as signup, install, checkout, demo request, documentation copy, or product activation. Use funnels when a conversion requires multiple steps.

Events vs goals

  • Event: a user action, such as Signup CTA click, Copy install command, or Plan selected.
  • Goal: an outcome you care about, such as completed signup, successful install, purchase, or high-intent lead.
  • Funnel: an ordered path of events or pages that should lead to a goal.

Good analytics usually starts with events, then promotes the important events into goals.

Common goal types

  • Destination: user reaches a page such as /welcome, /thank-you, or /checkout/success.
  • Event: user triggers a tracked event such as signup_completed.
  • Engagement: user stays longer than a threshold or views multiple pages.
  • Activation: user completes the first meaningful product action after signup.

For a developer tool or SaaS landing page, start with:

  • Signup CTA clicked.
  • Account created.
  • Tracking script copied.
  • Website connected.
  • First pageview received.
  • First event received.
  • Pricing CTA clicked.
  • Upgrade or checkout completed.

For a documentation-led product, also track:

  • Quickstart viewed.
  • Install command copied.
  • MCP config copied.
  • Troubleshooting section viewed.
  • Docs to dashboard click.

Funnel examples

Signup funnel:

  • Landing page viewed.
  • Signup CTA clicked.
  • Registration started.
  • Account created.
  • Website connected.

Activation funnel:

  • Account created.
  • Website created.
  • Tracking script installed.
  • First pageview received.
  • First growth question asked.

Paid conversion funnel:

  • Pricing page viewed.
  • Plan selected.
  • Checkout started.
  • Checkout completed.
  • First paid report or AI workflow used.

Ask AI to inspect the funnel

Analyze the signup funnel for the last 14 days. Find the step with the largest drop-off, compare mobile and desktop, and recommend one tracking event I should add next.
Compare visitors who copied the MCP config with visitors who only read the docs. Which group is more likely to reach signup?

Naming rules

  • Use stable event names, not UI text that changes every week.
  • Keep names readable: signup_cta_click, install_command_copy, website_connected.
  • Use properties for details: plan, source, page, campaign, placement.
  • Keep personally identifying information out of event names and properties.

AI-assisted goal review

Ask Amami to review your event list:

Review my current events and goals. Tell me which business outcomes are missing, which events are duplicated, and what I should track before the next launch.