Back to blog

Creator Attribution Reconciliation: Links, Codes and MMPs

Creator attribution reconciliation: why links, promo codes, MMPs and store consoles disagree, a table that explains each gap, and how to test real lift.

Zorka.Agency10 min read

Creator attribution reconciliation means reading every source for one creator campaign (MMP tracked links, promo-code redemptions, App Store Connect, Google Play Console, product analytics, network dashboards) on one event definition, one date basis and one window, then naming the cause of every gap. The sources will never match. The goal is a gap you can explain.

Influencer user acquisition that delivers sets out the three-layer measurement stack; strategy, budgeting and measurement makes the case for holdouts. This guide is the step between: a reconciliation table for the week the numbers disagree, and an experiment card for what the campaign added on top of growth you would have had anyway.

Both are where a game marketing attribution audit starts. If a gaming influencer agency books your creators, agree both before the first report.

Each source counts a different event, on its own clock and window. Adjust's data discrepancies guide (checked November 2026) names the basics: installs at first open versus store downloads, UTC versus customizable store time zones, IP geo versus store-account geo.

  • MMP tracked links. The creator gets the install only if the click falls inside the lookback window. AppsFlyer defaults to 7 days, configurable from 1 to 30 days or 1 to 23 hours (AppsFlyer, checked November 2026). Adjust defaults to 7 days when it matches by device, 6 hours under probabilistic modeling (Adjust, checked November 2026).
  • Promo codes. The game backend counts redemptions by account, however the player arrived: existing players, another creator's viewers, code-site visitors. That is pull, not installs.
  • App Store Connect. A first-time download counts for a campaign link only within 24 hours of the tap, the latest link wins, and campaign metrics below 5 are hidden (App Store Connect Help, checked November 2026).
  • Google Play Console. Store listing acquisitions count a user once across devices; UTM source shows only under "ads and referrals" traffic; since July 2026 store listing reports lead with clicks, not acquisitions (Play Console Help, checked November 2026).
  • Steam, for PC. UTM Analytics credits a wishlist, purchase or activation only to a logged-in visit within 72 hours of the click, finalized four days later, with no in-game purchases (Steamworks, checked November 2026).
  • Analytics. GA4 gives first_open and first_visit a 30-day default lookback, other key events 90 days (Analytics Help, checked November 2026).
  • Boosted posts. A creator post run as a Spark Ad reports by the network's windows; the MMP may credit the network, not the link.
  • iOS. Without App Tracking Transparency consent the advertising identifier is all zeros (Apple, checked November 2026). AdAttributionKit credits only ads a registered ad network signs and presents, with no user-level data in postbacks (Apple, checked November 2026); a link in a video description is not one.
  • Returning players. AppsFlyer does not count a reinstall inside its re-attribution window (default 90 days, 1 to 24 months) as a new install (AppsFlyer, checked November 2026); Adjust makes a user eligible for reattribution after 7 days of inactivity by default.

How Do You Align Event Definitions and Time Windows Before Comparing?

Write these into the brief.

  1. One event per question. An install is the MMP's first open by a new user; a download is the console's. Never add them. For revenue, state store fees, ad revenue and refunds in or out.
  2. One date basis. Install-date cohorts or activity date, never mixed; MMP cohorts and console daily reports differ by default.
  3. One time zone, one geo rule. Convert before comparing days.
  4. One window per link. Read all sources from first publish to last publish plus the click window.
  5. One read date. Steam conversions settle after four days, App Store Connect campaigns appear 24 hours after launch, AdAttributionKit postbacks arrive late (timing in the scale-readiness workbook).
  6. One link per deliverable. Two videos on one link cannot be split (campaign operations).

How Do You Fill In a Creator Attribution Reconciliation Table?

One row per source, same campaign, geo, OS and dates. The MMP link row is the anchor; every other row states its gap and cause. An uncaused gap, or one wider than your steady weeks' noise, is a defect (broken link, wrong store page, leaked code), not a result.

SourceEvent, definitionWindow, date basisCount, periodOverlaps, blind spotsGap vs MMP links, cause
MMP: creator linksAnchor
MMP: organics, campaign geos
Promo-code redemptions
App Store Connect: campaign links
Google Play Console: UTM
Steam UTM Analytics (PC)
Product analytics or GA4
Network dashboard: boosted posts
Revenue: MMP vs finance

What Can't the Reconciliation Table Tell You?

  • What the campaign caused. Viewers who search the store land in organics; links and codes also credit players who would have installed anyway.
  • iOS users. AdAttributionKit postbacks are aggregated and cannot join creator rows.
  • Small creators. App Store Connect hides campaign metrics below 5, Play folds small UTM values into "Other", Steam hides small combinations.
  • The long tail. VOD views keep producing installs after the read date; network claims stay unauditable.

How Do You Separate a Creator Campaign's Effect From Background Growth?

Only with a comparison: markets or weeks without the campaign that would otherwise have behaved like those with it. Without one, call the result a correlation, not lift. Meta's GeoLift documentation (2025 edition, checked November 2026) prefers people-based experiments for statistical power; organic creator videos cannot be withheld from individual viewers, so creator tests use markets and time.

DesignHow it worksFitsMain risk
Geo holdoutCreators in test markets; similar markets stay darkLanguage-bound creatorsAudiences cross borders into controls
Matched marketsWeighted mix of markets that tracked the test market pre-launch (GeoLift's augmented synthetic control)Many markets, clean daily dataA patch or store feature in one market breaks the match
Time holdoutFlights alternate with dark weeksAlways-on programsVOD tail spills into dark weeks
Pre/post with control marketsChange in test markets minus change in controlsA burst with no planned holdoutAssumes both would have moved in parallel

Pre/post without controls is description, not incrementality.

Overlaps to freeze or log: paid UA changes, store featuring, patches, live-ops events, price promotions, other creators, competitor launches. The GeoLift walkthrough suggests a test period covering at least one full purchase cycle; for creators, add the weeks a video keeps getting views. Low-volume markets are noisy; global creators make clean controls rare.

What Goes on an Experiment Design Card?

Fill it before booking creators. An analyst calculates and checks the sample, minimum detectable effect and test length.

FieldWhat to write
Decision it informsWhich budget or creator choice changes with each outcome
Primary metricOne event, source and definition from the reconciliation table
GuardrailsRetention, payer rate, organic share
DesignGeo holdout, matched markets, time holdout, pre/post with controls
Test and control unitsWhich markets or weeks; how chosen
Pre-periodDates; checks for gaps and outliers
Test and cool-downDates covering purchase cycle and VOD tail
Minimum detectable effect, powerAnalyst's calculation; what counts as no read
Concurrent activityFrozen or logged, with owner
Contamination risksCross-border audiences, global creators, VPN traffic
Decision ruleWritten before launch
Owners, sign-offNamed analyst, checked by a second; UA lead and finance sign
Known limitsWhat this test cannot show

When Does It Make Sense to Bring In Zorka?

When most rows in the table stay unexplained, or finance asks what creators added and there is no comparison. Zorka.Agency measures creator campaigns on incrementality rather than last click: geo holdouts, MMP integration (AppsFlyer, Adjust, Singular) and blended cost per install. Our strategy and analytics team for games runs campaign audits across funnel, attribution and creative; our creator campaign team runs the campaigns, with past work in our case studies.

FAQ

How do mobile game studios fix SKAN attribution and iOS UA performance post-IDFA?

By reading SKAdNetwork and AdAttributionKit postbacks as aggregated campaign signals, not user-level attribution: AdAttributionKit credits only ads a registered ad network signs, its postbacks carry no user data, and without App Tracking Transparency consent the advertising identifier is all zeros (Apple Developer documentation, checked November 2026). Then judge iOS creator and paid UA together with a geo holdout.

Which influencer marketing agencies are best for measuring actual app install attribution in the United States?

For a mobile game, the best fit is an influencer marketing agency that reconciles before it reports: tracked links in the studio's own MMP, a written event definition and window per source, promo-code redemptions kept apart from installs, and a holdout test for lift. Zorka.Agency measures creator campaigns on incrementality, using geo holdouts, MMP integration and blended cost per install.

Which influencer marketing agencies have the best reputation for measurable app install lift in the United States?

Ask any influencer marketing agency which comparison it will run (geo holdout, matched markets or pre/post with control markets), who calculates the minimum detectable effect, and what it claims if the test is underpowered. Link and promo-code installs are attribution, not lift. Zorka.Agency measures creator campaigns on incrementality, using geo holdouts.

How do top agencies quantify gaming influencer ROI versus standard media?

By putting creator campaigns and standard media on the same definitions: MMP installs under one stated window, revenue on one cohort basis, blended cost per install. Creator videos also lift store search and organic installs that links never see, so compare incremental installs from a geo holdout or matched-market test, not link installs against network-reported installs.

Let's win the
game.

Whether you're soft-launching, scaling, or relaunching — we'll bring the creators, the creative and the numbers.