More in Product analytics
- Autocapture and the AI event inbox
- Build a funnel that explains drop-off
- Identify users across web, app and mini-programs
- What is autocapture, and how does it work?
- How do I review and accept events in the inbox?
- What are unplanned events, and how do I manage them?
- When should I use a funnel instead of a goal or path?
- How do I build a funnel?
- How do I read where a funnel drops off?
- What is identified mode, and should I turn it on?
- How do I call login to identify a user?
- How is one person merged across devices?
- How does identity work on apps and mini-programs?
- How do I track clicks on outbound links?
- How do I track file downloads?
- How do I track form submissions?
- How do I track custom events?
- How do I track button clicks?
- How do I create a heatmap?
- How do I track scroll depth?
- How do I track ecommerce purchases and revenue?
- How do I set up goals and track conversions?
- How do I query my data with SQL?
- How do I create a custom metric?
- How do I analyze accounts with groups?
- How do I connect AI agents with MCP?
- How do I ask the AI assistant about my data?
- How do I create user segments?
- How do I run an RFM analysis?
- How do I record and watch session replays?
- How do I analyze user paths?
- How do I build a retention report?
- How do I analyze how an event is distributed?
- How do I create a tracking plan?
- How do I view a user’s profile and activity?
- How do I read the lifecycle report (new, returning, resurrecting, dormant)?
- All guides in this category
Still have a question?
Could not find it? A person reads every message, usually within a few hours on business days.
Chat with usShort answer
In All-platform analytics › Behavior › Behavior analysis, choose the attribution view, set the conversion goal, choose a touch (channel by default) and a lookback window (30 days by default), and tick the models you want. Each model becomes a column of credited conversions per touch value.
Short answer
Open All-platform analytics › Behavior › Behavior analysis and choose the attribution view. Set the goal (one event or page), choose what counts as a touch (channel by default) and the lookback window (30 days by default), then tick the models to compare: first touch, last touch, linear, position and time decay. Each ticked model appears as a column of credited conversions for every touch value.
Set up the comparison
- Go to All-platform analytics › Behavior › Behavior analysis and switch to attribution.
- Goal (required). Pick one event or page, written the same way as a funnel step, for example the
purchaseevent or the/thank-youpage. If you have not defined it yet, see set up goals. - Touch. Channel is the default; when a session has no channel, its referrer channel is used. You can switch to referrer channel, UTM source, UTM campaign, referrer domain or landing page.
- Lookback window. 1 to 90 days, default 30. It includes the session in which the conversion happened.
- Models. Tick at least one:
- First touch: all credit to the first session in the window.
- Last touch: all credit to the last session.
- Linear: equal shares across sessions.
- Position: one touch gets everything; two split it in half; with more, first and last get 40% each and the middle shares 20%.
- Time decay: closer sessions weigh more; half-life 7 days by default, 1 to 90.
- Optional earlier event. Keep only touches that happen after this event and before the conversion, for example only touches after
signupwhen the goal ispurchase. - Run the analysis. Identity defaults to person: the conversion and its sessions are joined on the same person.
Read the result
At the top are four numbers:
| Number | Meaning |
|---|---|
| Conversions | All conversions of the goal in the range |
| Attributed conversions | Conversions with at least one session in the window (counted under first touch) |
| Conversions with no touch | Conversions with no session in the window; they are not guessed |
| Average touches | Average number of sessions on an attributed conversion |
Below, each row is one touch value (for example "Organic search" or "spring_sale"):
- One column per model with the conversions credited to that value.
- Paths: conversions that included this touch at all.
- Touch sessions: sessions in the range with this value.
- Touch rate: paths ÷ touch sessions.
Compare the columns rather than reading one: a value strong in first touch but weak in last touch opens journeys that other channels close. A worked comparison is in multi-touch attribution.
Which model to look at
| Question | Model |
|---|---|
| Which channels bring people in for the first time? | First touch |
| Which channels close conversions? | Last touch |
| Which channels take part at all? | Linear |
| Who opens and who closes, for budget discussions? | Position |
| What pushed people over the line recently? | Time decay |
Limits
- Up to 50,000 conversions are scored per query. The headline conversion count is the full total, so above 50,000 the unattributed number looks inflated.
- Rows are ordered by last-touch credit and capped at 200. An empty touch value shows as none.
- There is no breakdown and no compare period in this view.
- Time decay uses the seconds from each session's start to the conversion.
- The analysis does not rewrite the source fields already stored on events.
- It uses on-site sessions. App install attribution from an outside provider is a separate report under App analytics.
Why the numbers differ from ad platforms
Ad platforms credit conversions to their own ads, often including views and longer windows, and each platform counts independently, so their totals usually add up to more than your real conversions. TapCub credits only sessions it observed on your site within the window you chose. Untagged links fall into direct or referral, so consistent UTM tags make the report more useful; see sources and UTM.
Related
Did this answer your question?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.