How to read first- and last-touch attribution
First-touch fields describe the earliest observed acquisition context for an identity. Last-touch fields describe the latest observed context. Daily anonymous identity limits how far those observations can be connected.
Define the context you collect
The SDK captures selected UTM fields and normalized referral, ad-source, and click-ID information when available. It omits the full query string from page URLs. Campaign values still need a naming convention and should not contain personal information.
The profile presents first and last versions of attribution properties, rather than one generic first-touch or last-touch column. An empty value can mean that no matching parameter was observed; it does not establish that no marketing interaction occurred.
Read first and last as observations
Imagine an identified account first appears from a newsletter and later returns from a paid campaign. Its observed first source can remain newsletter while its observed last source becomes the campaign source. This is useful context, but it does not prove which touch caused the purchase.
For an anonymous visitor, daily rotation breaks continuity at midnight. A return on another day gets another anonymous identity, so the earlier anonymous touch cannot automatically be assigned to the new profile.
Keep attribution distinct from revenue reconciliation
Track a purchase_completed event with a numeric revenue property when your application confirms a purchase. The analytics report sums submitted values; it does not independently reconcile processor payouts, refunds, recurring invoices, or currencies.
Do not send a currency label and assume the report performs conversion. Adopt one reporting currency or an explicit conversion pipeline. Send a purchase once with an idempotent message ID at the ingestion layer where appropriate.
Audit campaign links and identity together
Use the UTM builder and checker before launching a campaign. Run a controlled landing-page visit, identify an account after login, and inspect the event context and profile fields. Keep a record of the parameters and timestamps.
Use attribution to generate a hypothesis, then evaluate it against conversions and collection coverage. Blockers, cross-device anonymous activity, missing tags, and daily rotation all affect what can be observed.
Frequently asked questions
Is first-touch the first time a person ever saw the brand?
No. It is the earliest touch observed for the reporting identity within the available data.
Can anonymous last-touch connect across days?
Daily anonymous identity does not provide that linkage. Explicit identified events use a separate account ID.
Does a revenue event reconcile payments?
No. It reports a numeric value supplied by your application; processor reconciliation is a separate integration.