Playbook/Tracking & Attribution Setup

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

Define the measurement rules before installing tools. Every event needs one trigger, every customer needs a preserved acquisition source, and every data type needs one owner.

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.
1

Build the event plan

EventExact definitionWhy it matters
InstallThe app is opened for the first timeConnects acquisition sources to new users
SignupAn account is successfully createdSeparates registered users from installers
Onboarding startThe first onboarding step is displayedShows how many users entered onboarding
Onboarding completionThe final required step is completedMeasures continuation through the initial journey
Paywall viewThe subscription offer successfully rendersConfirms exposure to an offer
Trial startThe app store confirms a trial beganIdentifies monetization intent
PurchaseThe app store confirms an immediate paid transactionIdentifies customers who skipped a trial
Trial conversionA trial generates its first successful paymentSeparates trial starters from paying customers
RenewalAn existing subscription generates another paymentConnects acquisition to longer-term value
CancellationAutomatic renewal is disabledSignals intent to leave
RefundPreviously recorded revenue is returnedPrevents 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.

2

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 propertyWhat it describes
platformiOS, Android, or web
countryUser market
app_versionVersion active when the event fired
product_idSubscription or product purchased
price + currencyRevenue value in the transaction currency
paywall_id + offer_idThe exact paywall and offer shown
experiment_idThe active test variant

Takeaway

Event definitions do not change after campaigns begin. Changing an event’s meaning breaks comparison between historical and current data.
3

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
ClassificationRule
PaidA supported campaign received attribution.
OrganicNo paid campaign influenced acquisition within the defined rules.
UnattributedThe source could not be determined. Do not silently relabel it organic.
4

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.
5

Standardize UTMs

ParameterUse
utm_sourcePlatform or partner: meta
utm_mediumChannel type: paid_social
utm_campaignCampaign: us_ios_trial
utm_contentCreative, 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.

6

Set source-of-truth rules

DataSource of truth
Spend, impressions, and clicksAdvertising platform
Acquisition sourceAttribution system
Signup, onboarding, and paywall activityProduct event tracking
Trials, purchases, renewals, and refundsBilling provider
Final payouts after fees and taxesApp-store financial reports

Takeaway

The systems will not report identical numbers. The goal is to know which system should be trusted for each question—not force every dashboard to match.