How to track app install to in-app purchase for Google Ads

Architecture

The exact event sequence

Five stages. The break here is imposed by platform privacy frameworks rather than by an implementation mistake. Post-install events can be linked back to a campaign only within the limits those frameworks allow, which means aggregate and delayed reporting rather than the per-user joins the web makes possible. The identifier has to survive all of them.

1. Step 1

   Ad click

   Where the identifier exists, and where privacy frameworks start constraining what can be carried.

2. Step 2

   Install

   Free to the user, easy to buy, and weakly correlated with revenue.

3. Step 3

   Registration or first open

   The first signal that a human rather than a bot arrived.

4. Step 4

   Activation

   The in-app action that predicts payment for your product specifically.

5. Step 5

   Purchase or subscription

   The money event, from your backend rather than the client.

Diagnostic sequence

What's specific to Google Ads

The funnel logic above is the same wherever you advertise. These are the parts that change because it's Google Ads.

1. 1

   Click identifier: gclid, gbraid and wbraid

   Three parameters, not one. gclid is the long-standing identifier; gbraid and wbraid arrive on iOS traffic where privacy constraints prevent the usual one. Capture code that names only gclid loses a growing share, silently, and the loss is invisible until you audit how many records carry an identifier.

2. 2

   Import mechanism: offline conversion import

   Uploaded against the click identifier, either through the Google Ads API or as a file. The upload is the easy part; what limits it is how many of your records carry an identifier at all. Verify the current column format against Google's own template — it has changed before.

3. 3

   Deduplication

   There's no shared event ID mechanism like Meta's. What matters instead is the counting setting on each conversion action — 'one' for lead-type conversions so a repeat submitter doesn't count three times, 'every' for ecommerce where a second purchase is a second sale. This is the single most common misconfiguration we find in Google Ads accounts.

4. 4

   Window and timing

   Google's offline import window is 90 days from the click. Anything older can't be matched, and rows outside it fail as unmatched without much explanation. Measure your median click-to-outcome time against that before designing anything.

5. 5

   The Google Ads gotcha

   A conversion action that stops receiving hits is flagged as inactive 30 days later — by which point a month of budget has already run against a missing signal. Check the last-received date on every action monthly; it takes two minutes and it's the cheapest monitoring available.

Source-of-truth validation

How to prove the chain works

One real journey, followed all the way, then a reconciliation. Neither on its own is enough.

• A live Google Ads ad clicked, and the identifier confirmed present on the landing URL.
• The same identifier confirmed on the purchase record in your app's backend, joined to the install attribution after a full real journey through every step.
• Purchase or subscription confirmed arriving at Google Ads, verified by the match rate on the upload, not the success message.
• Your app backend's purchases by date, reconciled against the app store's own payout reporting reconciled against Google Ads per record over a fully closed window.
• The same reconciliation repeated 30 days later.

Straight talk

When this doesn't apply to you

Worth checking before you build anything, because two of these are common and both mean the work isn't worth doing.

• If your app is free with no purchases and monetizes through advertising, this funnel does not apply and the measurement question is a completely different one.
• If you're running Performance Max exclusively and haven't separated your conversion actions, the import will work and the reporting won't tell you much. Worth sorting the account structure first.
• If your cycle from click to purchase or subscription regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward activation events, valued at your own activation-to-purchase rate instead and use the later data for budget decisions rather than for bidding.
• If almost none of your purchase records carry a click identifier today, that's the whole project. Fix capture first — the import is the easy half and no tooling rescues a record with nothing to reference.