All docs

Funnel analytics

Read conversion, screen, variant, and device metrics.

Updated . 5 min read.

Funnel analytics measure how visitors move through a published /u/{slug} flow. Events are recorded server-side in funnel_events, so the dashboard keeps working even when browser pixels are blocked by privacy tools or ad blockers.

Metrics

The analytics endpoint returns four groups:

Group Meaning
totals Sessions, completed sessions, conversion rate, and conversion value.
per_screen View, next, and drop counts for each screen, plus next_rate.
by_variant Sessions, conversions, and conversion rate for each A/B variant.
by_device Session counts grouped by detected device type.

A session starts when a visitor lands on the funnel. A conversion is counted when a form_collect screen creates the underlying form submission. If the funnel has no form_collect screen, use CTA and redirect events to evaluate intent instead of submission conversion rate.

Screen drop-off

Use per_screen to find the step that blocks progress:

  • A high view count with a low next_rate usually means the screen is asking for too much too early.
  • A drop after a pricing or qualification question can be intentional if the funnel is filtering out poor-fit leads.
  • A drop on the final collection screen often points to form field friction, unclear value exchange, or a validation issue.

When you change screen order, copy, field requirements, or branching rules, compare analytics from before and after the edit. Screen edits clear the funnel analytics cache so the dashboard refreshes with the new structure.

Variants

When A/B testing is enabled, every session is assigned a deterministic variant. The by_variant section compares traffic and conversions for each variant key. Do not judge a variant from conversion rate alone if the session count is still small; first verify that the split is receiving enough traffic and that each variant reaches the same conversion goal.

Qualified leads and CRM outcomes

In the builder's Goals & tests tab, Lead qualification decides when a lead counts as qualified. A rule is either a score a lead must reach (the total, or one scoring bucket) or an outcome the visitor must land in. Choose whether all rules or any one rule must pass, and raise the rule version when you change them so earlier decisions stay traceable to the rules they used.

Try a sample answer runs the same check a real submission goes through, with the scores and outcome you enter, and shows which rules pass. Nothing is saved or recorded. A lead that qualifies is recorded once; a lead that later stops qualifying is revoked, but the earlier decision stays on record.

CRM outcomes maps the stages in your CRM to won or lost. When your CRM reports a stage through the outcomes API, Formspring looks it up here and applies it to the lead's journey exactly once. Revenue is tracked separately from qualification, so a refund changes net revenue without changing how many leads qualified.

Bookings and sales made during a journey are recorded against it. When the visitor started from a short link and allowed analytics, they are also reported to that link's outcomes, even when the booking or sale happened before they submitted the funnel. A visitor who refuses tracking is still counted, as unattributed.

From source to outcome

The From source to outcome table lists leads, qualified leads, bookings and orders by the source they came from, with net revenue per currency. Pick how a journey is credited:

Model Credit
Journey source (default) The whole journey counts under the source of the visit that started it.
First touch The whole journey counts under the earliest visit that carried a campaign or referrer.
Last touch The whole journey counts under the latest such visit.
Linear Every campaign or referrer visit gets an equal share, so counts can be fractions.

A direct visit never takes credit from a campaign or referrer visit; it is credited only when nothing else touched the journey. The Lookback window (7 to 90 days, or the whole history) leaves out visits that came more than that long before the visit that converted. It applies to the touch models, not to the journey source. Outcomes recorded before visit history was kept have one stored source, which every model credits in full. Visitors who did not allow analytics are always counted as unattributed.

Save the model and window you read most under Goals & tests > Attribution default in the builder; the report, the API and the agent tool then open with them, and you can still pick another model while you read.

The same report is available as GET /funnels/{funnel}/attribution?model=linear&lookback_days=14 and as the get_funnel_attribution agent tool.

Freshness

Aggregations are cached for five minutes per funnel. Event collection is immediate, but dashboard totals can trail recent traffic until the cache expires or a screen edit busts it. If numbers look stale after a campaign launch, wait for the cache window before assuming events are missing.

Troubleshooting

If analytics look empty, check that the funnel has been published and that you are viewing the funnel URL rather than only previewing screens inside the dashboard. For submission-based conversion, confirm the flow contains a form_collect screen and that the underlying form accepts the submitted payload. For advertising reports, compare server-side funnel totals with GA4, GTM, Meta Pixel, or TikTok Pixel data because each vendor can filter or sample traffic differently.