
Table of Contents
ToggleA broken AppsFlyer Google Ads conversion import looks the same almost every time. The SDK is live on iOS and Android, postbacks fire, the events are visible inside the AppsFlyer dashboard, and yet nothing shows up in Google Ads as an importable conversion action. The campaign team cannot optimize on installs or in-app events, even though every screen you open says the integration is fine.
The cause is rarely the SDK. It is usually one of three links in a chain that runs from AppsFlyer to Google Ads, and each link can fail without an error message. This guide walks through how the chain works, the three checks that find the break, and the secondary causes worth ruling out afterwards. Everything below follows AppsFlyer’s and Google’s documentation as checked in October 2026.
It helps to see the whole path before debugging one piece of it. According to AppsFlyer’s Google Ads integration guide for advertisers, the setup has four parts:
A failure in any of these four leaves the others looking healthy. That is why the AppsFlyer dashboard can show perfect event volume while Google Ads shows nothing. The dashboard only proves that events were recorded, not that they were forwarded, received or imported.
Match what you see to the checks below. Start with check one, because it is the cheapest to verify and the most often wrong.
The Link ID is the handshake between the two platforms, so if it is wrong or points to the wrong place, nothing downstream can work.
AppsFlyer’s Google Ads FAQ says it plainly: ensure the Link ID in AppsFlyer matches the Link ID in Google Ads. Copy it from Google Ads again and compare it character by character with the value saved in the AppsFlyer integration. A common cause is a Link ID created for a different app or platform, since Google requires a separate link ID for each app. Google also describes the status as Unverified until the ID is added to the provider account and conversion data starts flowing.
This is the check that catches the most expensive mistakes. The link must live in the Google Ads account, or under the manager account, that your campaigns run in. If your agency or media buyer works from a different account than the one where you created the link, you can have a perfectly healthy link that serves a different account than the one you are bidding in.
AppsFlyer explains the permitted structures: one Link ID can be shared across multiple Google Ads accounts. With a manager account, the manager should import first_open for its linked sub-accounts. For a sub-account, the manager account must share the Link ID, and the sub-account must also import first_open directly. Google’s guide to linking a third-party app analytics provider covers sharing a link by entering the other account’s customer ID. Agencies also need their own Google Ads accounts separate from the advertiser’s, according to AppsFlyer.
AppsFlyer’s documented route is the Link ID, and its setup guide does not list a Firebase or GA4 link as a required step. But many apps also have Firebase or GA4 linked to Google Ads for Google’s own signals. If yours does, confirm that link points at the same account that runs your campaigns. Otherwise you can end up reading conversion data in one account while spending in another, and nothing flags the difference.
AppsFlyer’s Google Ads postback partner configuration requires your Google Ads Customer ID, entered without hyphens, and you can add several separated by commas. Google Ads attribution must also stay enabled in AppsFlyer, since turning it off stops postbacks to these partners too.
The Link ID gets you installs. In-app events need their own configuration, and this is where most partial failures live.
Then confirm the event actually fires. Trigger each mapped event yourself in a test build. The mobile app attribution debugger can check an event payload against documented rules before you spend time re-testing blind, and the mobile attribution audit guide lists the other event-level problems worth ruling out.
Sending events is not the same as importing them. Google Ads will not use an event as a conversion action until you import it, and this step needs Google administrative access. A surprising number of setups stop here because the person who configured AppsFlyer never had that access.
If the three checks above all pass, look at these.
Once events import, expect AppsFlyer and Google Ads to disagree a little. The AppsFlyer FAQ lists the reasons, and none of them is a bug:
The point is to watch for a stable gap over time, not an exact match. For the wider concept, read what mobile attribution is, and if you are still setting things up from scratch, the AppsFlyer setup guide covers the SDK side.
Most cases of a failing AppsFlyer Google Ads conversion import come down to one of the checks above, and the fix is a setting rather than code. The slow part is usually access: the person who owns AppsFlyer is not the person who owns Google Ads. If that is your situation, the fastest route is for the Google Ads owner to share the Link ID, a screenshot of the conversion actions list and the linked accounts view, and for you to share an export of the events you expect to see.
The three most common causes are a Link ID that does not match between AppsFlyer and Google Ads or sits in the wrong account, in-app event postbacks that are off or limited to the wrong audience, and conversions that were never imported in Google Ads. The AppsFlyer dashboard only proves that events were recorded, not that they were forwarded and imported.
The Link ID connects your app in Google Ads to AppsFlyer. In Google Ads you open Tools and settings, then Data manager, choose Connect Product, select Third-party app analytics and create the link ID for AppsFlyer, your platform and your app. You then paste it into the Google Ads integration in AppsFlyer. You need a separate link ID for each app.
AppsFlyer states that new conversions can take up to 6 hours to be added to the queue before you can import them. The event must also be triggered at least once, by launching the app and performing the mapped event. Wait at least 6 hours before concluding that the import failed.
AppsFlyer’s documented setup uses the Link ID and does not list a Firebase or GA4 link as a required step. If your app also has Firebase or GA4 linked to Google Ads, check that it points at the same account that runs your campaigns so you are not reading data in one account while spending in another.
Import first_open for each app, which AppsFlyer lists as required for install measurement. Add session_start only if you want to measure re-engagements, then import each in-app event you want to optimize on, such as registrations or purchases.
Google Ads records conversions at click time and AppsFlyer records installs at launch time. Google Ads credits every install after a Google engagement in the window as a self-reporting network, while AppsFlyer credits the last click and treats earlier engagements as assists. AppsFlyer may also remove some installs under its validation rules. A stable gap over time is normal.
For the main integration the Link ID is what connects the two platforms. For Google Ads postback partners, AppsFlyer asks for your Google Ads Customer ID entered without hyphens, and you can add several separated by commas.
If your AppsFlyer events fire but never become usable Google Ads conversions, send your setup description to contact@alfahadhridoy.com and I will reply by email with what to check first.