Metrickle

Funnels and goals

Last updated

Goals say what a conversion is: a sign-up, a purchase, a key page. Funnels show the steps people take to get there and the step where most of them give up. Start with a goal, then build a funnel to find the leak.

Goals

A goal is an event or a page that counts as a conversion. Goals power conversion rate, conversions and revenue attribution on every report, including the breakdowns on an app’s Overview. Each person counts as converted once in a period, however many times they reach a goal.

TypeMatchesExample
Custom eventAn event with exactly this namesignup
Page visitA page or screen with exactly this path, or every path that starts with it if you end it with */thank-you*

Page goals work for mobile apps too: screens count as pages.

Add a goal

  1. In your app, select Goals.
  2. Under Add goal, choose the Type.
  3. Enter the Event name or Page path. For a page, end the path with * to match a section, for example /thank-you*.
  4. Optionally, enter a Display name, such as “Signed up”. Without one, the goal is named after what it matches.
  5. Select Add goal.

Suggested from your events lists custom events your app already sends that aren’t goals yet, with how many visitors sent each one. Select one to add it as a goal.

To delete a goal, select the bin icon next to it. Reports stop counting it as a conversion, but your event data isn’t affected.

You need permission to change goals. If you can only view them, ask a workspace admin. See team and access.

Revenue

Revenue is the total value of the events you track, not something you set on a goal. Send a numeric revenue property with an event, such as an order, and Metrickle adds it up per app, page, source and campaign. You can also connect Stripe or RevenueCat under Integrations, so purchases, renewals and refunds arrive without custom events.

See tracking revenue and integrations.

Funnels

A funnel is 2 to 10 steps in order. Each step is a page or an event. For each step, Metrickle counts the people who reached it after reaching every step before it, in order, within the funnel’s time window.

Build a funnel

  1. In your app, select Funnels. A new funnel starts with example steps you can change.
  2. Give it a name in the box at the top of the builder.
  3. For each step, choose Page or Event, then enter what it matches:
    • For a page, a path such as /pricing. End it with * to match a section, such as /checkout/* or /blog/*.
    • For an event, its name, such as signup.
  4. Optionally, give the step a label. The label is what the results show.
  5. Select Add step for more steps, up to 10. Use the arrow buttons to reorder steps, and the remove button to take one out. A funnel needs at least 2 steps.
  6. Choose the conversion window: within 1 hour, within 1 day, within 7 days or within 30 days.

Results update as you edit. Screens from the mobile SDKs work as page steps, and events work on every platform.

The conversion window

The window runs from the moment someone enters step 1. Someone who reaches the last step after the window has closed doesn’t count as completing it. A short window suits a checkout. A long one suits a trial that should end in an upgrade. Funnels saved through the API or an AI assistant can use any window up to 90 days.

Read the results

The Conversion card shows the share of visitors who completed every step, then a chart and a table:

ColumnWhat it shows
VisitorsPeople who reached the step
OverallShare of people from step 1 who reached this step
From previousShare of people from the previous step who reached this one
DroppedPeople who reached the previous step but not this one
Median timeTypical time from the previous step, for people who carried on

Select Who dropped on a step to list the people who reached the step before and never reached it, newest first: when, the last page they reached, their device and accessibility settings. Each one opens their journey, and their replay if the session was recorded and you may watch replays. The list follows the date range and filters in force, so filter by an accessibility setting first to see only those people. People are shown by a short pseudonymous id, not the user id your app sends, and people still inside the funnel’s window aren’t listed until it closes. On a task, Who abandoned and Who took it back do the same for its attempts, and on friction, Who hit it does it for each hotspot.

Above the chart, Biggest drop-off names the two steps between which the most people leave, and how long those who carry on take. That’s usually the place to start. Open friction filtered to that page to see what gets in the way, or journeys to see where people go instead.

If the card says No visitors reached the first step, check the step matches what your app sends (the Events screen lists it), or widen the date range.

Split a funnel by segment

Every filter works on funnels. Select a row in an app’s breakdowns, such as a campaign, a device or an accessibility setting, and the funnel recalculates for just those people.

  • Source, medium, campaign and referrer filters apply to the whole session. A purchase five pages later still counts for the campaign that brought the visitor.
  • Other filters, such as a page, device or country, apply to every step. A page filter keeps only events on that page, so steps on other pages can’t match.

To compare people using an accessibility setting with people using none, see accessibility breakdowns.

Save and share a funnel

Select Save to keep a funnel. Saved funnels are listed under Saved funnels and are shared with everyone who can see the app. Select New to start another.

To delete a saved funnel, select the bin icon next to it. It’s removed for everyone on the app, but your event data isn’t affected.

You can build and run funnels with view access, but saving or deleting them needs permission to change funnels.

Doubt before deciding

Before people convert, or give up, they often hesitate. Doubt before deciding shows the signs of it on Funnels and Goals, and how the people who showed them converted against everyone else.

PatternWhat people did
Flip-floppedUsed the same control three or more times in one visit, such as a monthly and yearly toggle
Came back to a pageViewed the same page again later in the visit
Went back and forthMoved between the same two pages twice
Read it and went backSpent 30 seconds or more on a page, then returned to the one before
Bounced backLeft a page within 7 seconds, back to the one before
Came back to a formLeft a form part-way, then came back to its page
Paused before actingStopped for 30 seconds or more part-way through a page, then sent a form or left it (web)

Each pattern is shown for any page or control, and for the busiest pages, controls and forms where it happened. Only what people did before their first conversion counts. Reloads don’t count as coming back. A custom event that most visits send three times or more, such as a scroll tracker, is ignored for flip-flopping.

Converting means any goal, the goal you selected, the funnel’s last step, or a saved task’s success.

Long pauses

A pause only counts once someone has started on the page: it’s the time between two of their actions, such as typing in a field and pressing Send, not the time spent reading a page when it opens. Time with the tab in the background and time with sound or video playing don’t count. The action is a form being sent, leaving a form part-way, or a control you mark with data-mk-primary, such as a checkout button that isn’t in a form. See the web SDK.

Taking longer is normal for many people: listening with a screen reader, working by keyboard, or reading zoomed in or with large text. Pauses from sessions using any of those settings are never counted, here or in cases. Browsers don’t say when a screen reader is on, so on the web keyboard use stands in for it. A click from assistive technology with no key press or tap just before it isn’t counted either.

Read it

Each pattern is one sentence, such as “Visitors who went back and forth between / and /pricing converted half as often (4% vs 9%).”

  • Converted less: something there leaves people unsure. Patterns like this come first, with the conversions (and money, if your goals carry revenue) they fell short.
  • Converted more: people were deciding, not lost. Make the comparison easier, don’t remove it.
  • Too few to compare yet: fewer than 20 visitors on either side, or a gap chance could explain.

This is what went together, not what caused it. To find out what would help people decide, use Survey them or Plan a study on the pattern. See ask them why.

In cookieless mode, someone who comes back on another day counts as a new visitor, so doubt shown one day isn’t linked to a conversion the next. Surveys can’t reach cookieless visitors either.

Funnels, tasks and protected tasks

A funnel is for exploring. When you care whether people finish something that matters, such as checkout or sign-up, save it as a task under Tasks and protect it. Metrickle then judges it after every release and tells you when people using an accessibility setting, or a browser or device, fall behind. See protected tasks.