At a glance
| Field | Detail |
|---|---|
| What | Link AppsFlyer to Google Ads and verify app conversion actions. |
| Who it matters to | App buyers using AppsFlyer events for Google Ads measurement. |
| Where | Google Ads and the app's AppsFlyer integration; iOS testing also requires attention to tracking permission. |
| When it applies | During integration setup or investigation of missing conversion events. |
| Action | Check ownership, event delivery, and bidding settings before using an action for optimization. |
The AppsFlyer Google Ads integration requires checks on both sides: the app must send events, and Google Ads must have the intended conversion actions. Our suggested workflow separates account linking, event verification, and bidding selection so that a working connection is assessed against the campaign's actual goal.
Check prerequisites and account ownership
| Prerequisite | Source-backed requirement | Suggested check |
|---|---|---|
| Google Ads access | Administrative access is required to create a Link ID. | Identify the account owner before setup. |
| Event source | Google requires a provider link and events configured in the provider account. | Confirm the intended app events exist. |
| Multiple buying accounts | Google recommends manager-level cross-account conversion tracking where applicable. | Decide which account owns conversion tracking. |
| iOS identifier testing | Apple requires tracking permission to access the advertising identifier. | Confirm the test device's permission state. |
Google recommends retaining ownership of app Link IDs in an account you control, including when working with agencies. Where cross-account conversion tracking cannot be used, the owner can share the link with another account. Review this arrangement before creating another link for the same app. See Google's linking documentation.
Create the link and activate AppsFlyer
In Google Ads, open Tools, then Data manager, select + Connect Product, and choose Third-party app analytics. Create a Link ID, select AppsFlyer, choose the mobile platform, and find the app. Copy the generated ID. Google says the link remains Unverified until the ID is added to the provider and conversion data starts flowing.
In AppsFlyer, open Collaborate, Partner Integrations, then Marketplace. Find Google Ads, select Integrate, and enable Activate partner in the Integration tab. Paste the Link ID and keep the partner activated while using the integration.
Enable In-app event postbacks, add the intended events, map them to Google Ads events, and save. AppsFlyer specifies All media sources, including organic for initial setup, with changes permitted after successful setup. Review attribution and data-sharing settings in the AppsFlyer setup guide.
Verify creation before importing manually
Google's automatic conversion documentation says conversion data sent through the App Conversion API can automatically create and enable actions. Those actions start as secondary, for observation rather than bidding.
Actions are placed in the appropriate conversion goal. A newly created goal is not an account-default goal. Our suggested check is to inspect both the action's primary or secondary setting and the campaign's goal selection before expecting optimization to use it. Move an action to primary only when it represents the intended bidding outcome.
If an action is still missing, use Google's conversion setup instructions: open Goals, Summary, and + Create conversion action; select Conversions on an app and set up Third party app analytics as the source. Select the relevant conversion category and use the suggested event or + add conversion actions. Google says newly imported actions begin reporting from import time; do not assume historical backfill.
Test delivery and investigate missing events
AppsFlyer's troubleshooting guidance calls for launching the app and performing the mapped events. It says conversions can take up to 6 hours to appear. Check the conversion summary after testing and retain the event names and test time for investigation. AppsFlyer's setup guide also specifies first_open for install measurement.
| Problem | Documented check or fix |
|---|---|
| Missing install attribution | Confirm the integration is active and the Link ID matches in both systems. |
| Missing in-app event | Review postback configuration, then trigger the mapped event. |
| Event hidden from the summary | AppsFlyer's setup guide says to view all conversion actions and set Status to All. |
| Action records but bidding does not use it | Review the secondary setting and campaign goal selection described by Google. |
| Missing clicks or impressions in AppsFlyer | AppsFlyer's FAQ says collection requires authentication in the Cost tab. |
Keep iOS permission separate from linking
AppsFlyer's test guidance requires IDFA collection for its iOS event test. Apple's privacy documentation says the advertising identifier remains all zeros without permission through App Tracking Transparency. Include the device's permission state in the test record when investigating missing events.
Apple also requires disclosure of third-party SDK data practices. Review tracking permission and SDK disclosures with the app team. For iOS measurement, also review the SDK and signal prerequisites in AppsFlyer's setup guide.
What to review
- Check that the correct app, platform, account owner, and Link ID are recorded.
- Confirm mapped events reach the conversion summary after a test.
- Review whether each action should remain secondary or support bidding.
- Check the campaign's selected conversion goal before changing optimization.
- Compare event definitions using the measurement data path.



