At a glance
| Field | Detail |
|---|---|
| What | Connect Firebase app measurement to Google Ads and select app events as conversions. |
| Who it matters to | App buyers implementing Firebase measurement or adding it alongside an existing analytics provider. |
| Where | Android and iOS apps using the Google Analytics for Firebase SDK and a linked Analytics property. |
| When it applies | Initial setup, missing conversion imports, or a planned change of conversion source. |
| Action | Verify event collection, account linking, and conversion settings before changing campaign goals. |
Firebase Google Ads integration requires checks at the app, analytics property, and advertising account. Our suggested workflow is to verify each stage separately, then decide which conversion actions campaigns should use. A working account link alone does not establish that the intended app event has been selected for bidding.
Prerequisites
Google's app measurement guide describes the SDK, project, and event requirements. Confirm the following before starting.
| Requirement | What to prepare | Check |
|---|---|---|
| App measurement | Firebase project and Google Analytics for Firebase SDK | Confirm Analytics is enabled for the project. |
| Account access | Google Ads administrative access and Analytics property Administrator or Editor access | Use an account with permissions on both products. |
| Android access | Google Play Console account ownership | Identify the owner before setup. |
| iOS conversion creation | App Store ID in the Firebase project | Confirm it is present before creating conversions from iOS key events. |
Connect events to the buying account
Step 1: Prepare the app events
Implement the SDK and log any additional events needed for your objective. In Analytics, open Admin, then Data display, then Events, and mark the intended bidding events as key events. Google's guide treats event implementation and key-event selection as separate setup tasks.
Step 2: Link the Analytics property
In the correct Analytics property, open Admin, then Product links, then Google Ads links. Select Link, choose the Google Ads accounts, confirm, and review personalized advertising and auto-tagging settings before submitting. Google's linking documentation explains the permissions and controls.
Check the property selector first: the documentation's console links open the last property accessed. If the intended advertising account is missing, review administrative access. Linking a manager account makes imported Analytics data available to its client accounts, so account selection deserves an explicit review.
Step 3: Create the app conversion actions
In Google Ads, open Goals, then Summary, then Create conversion action. Select Conversions on an app, choose Set up, and use Google Analytics as the source. Select the category matching the app action, choose the existing event, then select Select events and Save and continue. Follow Google's app conversion instructions for the available setup path.
That page requires the correct linked property and events marked as key events for import. It says account linking or key-event changes can take 24 to 48 hours to propagate. Allow for that stated delay when investigating an initially missing event.
Verify collection before investigating attribution
Firebase's DebugView documentation provides a collection check. Enable debug mode on the development device using the platform-specific instructions, then open Analytics > DebugView in Firebase. Perform the target action and select the corresponding device.
Inspect the event and its parameters. DebugView can expose error events and events carrying a firebase_error parameter; the latter require opening the event's parameter list. Device console logs can also explain rejected events or parameters.
Our interpretation: use this check to establish whether the app logs the intended action. Then verify the account link and conversion selection separately. Do not treat a DebugView appearance as confirmation that a campaign has attributed a conversion.
| Problem | Documentation-backed explanation | Suggested check or fix |
|---|---|---|
| Advertising account missing during linking | Linking requires Google Ads administrative access. | Check access and the selected Analytics property. |
| Event unavailable for import | Google requires key-event status; changes can take 24 to 48 hours to propagate. | Confirm the event's status and allow the documented propagation period. |
| Event appears with incomplete parameters | DebugView shows event parameters and logging errors. | Inspect the event details and device logs before changing advertising settings. |
| Firebase and AppsFlyer totals differ | AppsFlyer says Firebase imports are structured differently and are not fully comparable with AppsFlyer data. | Identify the conversion source before reconciling reports. |
Keep an existing measurement route deliberate
For campaigns already optimizing to third-party conversion actions, Google's app measurement guide says to make newly imported Analytics actions secondary. Adding Firebase should therefore prompt a review of existing campaign goals before any migration.
Adjust's account setup documentation adds an account-structure check: Firebase linking should use the same account level as the event imports. It also specifies Firebase-primary and Adjust-secondary actions for the particular Firebase configurations it describes. Treat that as configuration-specific guidance when planning a migration, rather than applying it automatically to an existing setup.
AppsFlyer's discrepancy guidance reinforces the reporting distinction: compare AppsFlyer reporting with its corresponding imported conversion source. Our suggested check is to record the provider, event, and account used for each comparison in your measurement data path.
What to review
- Check the Firebase project, Analytics property, app platform, and Google Ads account together.
- Confirm the intended action is collected with the expected parameters.
- Review key-event status and conversion creation separately from account linking.
- Check primary and secondary settings before changing existing campaign goals.
- Keep provider-specific conversion reports distinct when verifying the setup.



