Funnels, forms, bookings, surveys and short links all answer the same question in their reports: which visit gets the credit for this lead, booking or order? The answer is one model and one look-back window per workspace, set under Settings, Attribution. The owner can change it; everyone can read it.
Models
| Model | Who gets the credit |
|---|---|
last_non_direct (default) |
The latest visit that came from a campaign or another site. |
first_non_direct |
The earliest visit that came from a campaign or another site. |
linear |
Every such visit, in equal shares. Counts can then be fractions. |
A direct visit (no campaign, no referring site) never takes credit from another visit. It is credited only when nothing else touched the journey.
The look-back window is 1 to 90 days, 30 by default. A visit older than the window, counted back from the outcome, gets no credit.
Older names still work: first_touch is first_non_direct and last_touch is last_non_direct. A funnel keeps the model it saved, and its own journey_source view (the one source stored on the lead). A short link keeps its own conversion window if you set one.
Every report says which rule it used
Each report, export and answer from the API or an agent carries attribution_model, attribution_window_days and a sentence, attribution_label, for example "Last non-direct touch, 30-day look-back window." A CSV repeats them on every row, so a file taken out of Formspring still says what it measured. Reports take optional model and window_days to try another rule without changing the workspace setting.
Visitors who decline optional tracking
A visit is only known when the visitor allowed analytics. If they declined, the form, booking or survey works exactly the same, nothing optional is stored about the visit, and the response is counted as unattributed. It is never guessed into a source. Visits of the same person are linked only through a random visitor id that the page keeps while analytics is allowed.
What never counts
- Sample and test data.
- Spam, drafts, unfinished and imported responses.
- Bots, crawlers and link-preview fetchers, and your own team's visits to a funnel.
- Cancelled or declined bookings, and outcomes that were withdrawn.
What happened to the lead afterwards
A CRM or payment system can report back what became of a form response or a booking: qualified, won (with a value) or lost, and later a refund or dispute. Use POST /forms/{form}/outcomes/crm, POST /bookings/pages/{bookingPage}/outcomes/crm and the matching /outcomes/adjustments, or the agent tools record_form_crm_outcome and record_booking_crm_outcome. Each fact is applied once per source_fact_id. The outcome is credited to the same source as the response or booking, and a response marked as spam, deleted, or a booking that is cancelled, takes its facts out of the totals again. Refunds that add up to the whole value take the won deal out of the totals.
Agents can read and change the workspace rule with get_attribution_settings and set_attribution_settings.
