Tracking & Attribution Setup
Tracking tells you what happened after someone entered the app. Attribution tells you which channel, campaign, and creative should receive credit for bringing that user.
Takeaway
Before implementing tools
- Choose which events matter and write the exact moment each event fires.
- Decide which acquisition fields must remain attached to the user.
- Define how paid, organic, and unattributed users will be handled.
- Assign a source of truth to spend, attribution, product behavior, billing, and payouts.
Essential subscription journey: Install → signup → onboarding completion → paywall view → trial or purchase → trial conversion → renewal.
Build the event plan
| Event | Exact definition | Why it matters |
|---|---|---|
| Install | The app is opened for the first time | Connects acquisition sources to new users |
| Signup | An account is successfully created | Separates registered users from installers |
| Onboarding start | The first onboarding step is displayed | Shows how many users entered onboarding |
| Onboarding completion | The final required step is completed | Measures continuation through the initial journey |
| Paywall view | The subscription offer successfully renders | Confirms exposure to an offer |
| Trial start | The app store confirms a trial began | Identifies monetization intent |
| Purchase | The app store confirms an immediate paid transaction | Identifies customers who skipped a trial |
| Trial conversion | A trial generates its first successful payment | Separates trial starters from paying customers |
| Renewal | An existing subscription generates another payment | Connects acquisition to longer-term value |
| Cancellation | Automatic renewal is disabled | Signals intent to leave |
| Refund | Previously recorded revenue is returned | Prevents refunded revenue from appearing profitable |
Use the same event names everywhere: install, signup, onboarding_start, onboarding_complete, paywall_view, trial_start, purchase, trial_conversion, renewal, cancellation, expiration, refund.
Lock the firing rules
- Signup fires after account creation succeeds—not when the button is pressed.
- Onboarding completion fires after the final required step—not when onboarding is skipped or closed.
- Paywall view fires only after the paywall successfully renders.
- Trial and purchase fire only after confirmation from the store.
- Renewal, expiration, cancellation, and refund come from confirmed billing events.
- Use properties for variations instead of inventing new events.
| Shared property | What it describes |
|---|---|
| platform | iOS, Android, or web |
| country | User market |
| app_version | Version active when the event fired |
| product_id | Subscription or product purchased |
| price + currency | Revenue value in the transaction currency |
| paywall_id + offer_id | The exact paywall and offer shown |
| experiment_id | The active test variant |
Takeaway
Preserve the acquisition source
Attach the original source to the customer for their full lifecycle. Later campaign visits are re-engagements and must not overwrite the original acquisition record.
- Source and channel
- Campaign and ad set or ad group
- Ad or creative and keyword when relevant
- Country and platform
- Click-through or view-through attribution
- Original acquisition date
| Classification | Rule |
|---|---|
| Paid | A supported campaign received attribution. |
| Organic | No paid campaign influenced acquisition within the defined rules. |
| Unattributed | The source could not be determined. Do not silently relabel it organic. |
Standardize attribution rules
- Choose click-through and view-through windows and keep them distinguishable.
- Define new-user acquisition, re-engagement, and original-source rules.
- Use the same rules when comparing campaigns and channels.
- Treat attribution as a consistent crediting method—not proof that an ad caused the conversion.
A privacy restriction, broken link, missing identifier, or incomplete integration can all create an unattributed user. Unmatched does not automatically mean organic.
Standardize UTMs
| Parameter | Use |
|---|---|
| utm_source | Platform or partner: meta |
| utm_medium | Channel type: paid_social |
| utm_campaign | Campaign: us_ios_trial |
| utm_content | Creative, hook, creator, or version: student_procrastination_ugc_v01 |
Use lowercase values without spaces. Avoid vague names such as campaign1, new_test, or winning_ad. UTMs cover web links, but they cannot attribute a native app install without the MMP and deep-linking setup in the next section.
Set source-of-truth rules
| Data | Source of truth |
|---|---|
| Spend, impressions, and clicks | Advertising platform |
| Acquisition source | Attribution system |
| Signup, onboarding, and paywall activity | Product event tracking |
| Trials, purchases, renewals, and refunds | Billing provider |
| Final payouts after fees and taxes | App-store financial reports |
Takeaway