Consent Mode v2 in Firebase Apps: Effect on EEA Conversion Reporting

Firebase can show a warning that consent indicators for ad personalization were not collected from users in the European Economic Area (EEA). A US subscription app sees it too, because some organic or paid traffic comes from Europe. Two questions follow: does the warning affect your conversion reporting, and which consent signals must your code send to clear it?

Missing EEA Consent Signals

The alert appears when your app sends events from users located in the EEA or the UK without attaching explicit end-user consent states. Google's stated effect is on advertising use: if you take no action, only users outside the EEA are included in audiences used by your linked advertising products, and personalized advertising and remarketing require affirmative consent signals.

Four Required Consent Parameters

While the original consent framework focused on local device storage, version 2 introduces two additional flags that govern how data is used downstream on the server side. Your app configuration must account for four distinct parameters:

• analytics_storage controls whether the SDK can read and write identifiers for general app usage and behavioral metrics.
• ad_storage governs whether advertising identifiers and cookies can be stored or accessed on the user's device.
• ad_user_data determines whether user-level data can be sent to the advertising platform for conversion measurement and attribution.
• ad_personalization specifies whether that user's activity can be added to remarketing lists and used for personalized ad targeting.

Passing Banner Choices to the SDK

Connecting a consent management platform (CMP) to your analytics SDK requires setting a safe default before any events fire. In your app's Info.plist on iOS or AndroidManifest.xml on Android, set the default state for EEA traffic—or globally, if you want a single rule—so that storage and ad parameters start as denied until the user interacts with your banner. When the user taps "Accept" or "Reject" on your CMP prompt, listen for that callback in your initialization code and invoke the SDK's setConsent method, mapping the CMP's boolean or string values directly to the four consent parameters so subsequent subscription events carry the updated status.

Impact on Audiences and Attribution

Leaving consent parameters unconfigured or having users decline them directly shrinks your European data visibility. When ad_personalization is denied or missing for EEA users, those profiles stop populating your remarketing audiences, leaving you unable to retarget trial drop-offs from Berlin or Paris. ad_user_data carries ads measurement consent, so EEA conversion reporting in your ad accounts can be limited when it is denied or missing.

Configuring MMP Consent in Airbridge

Using the Android SDK with a consent management platform, you send the user's consent data and location data to the Airbridge SDK before calling startTracking, and only call startTracking after the consent data has been stored in the consent management platform. Initialize the Android SDK with setAutoStartTrackingEnabled(false), then pass eea, adPersonalization, and adUserData using Airbridge.setDeviceAlias. In the Web SDK, adPersonalization is a string where 0 means the user did not allow tracking for ad personalization and 1 means the user allowed it. If you are setting up attribution for your subscription app, the Airbridge Core Plan offers a 30-day free trial, then $40+/mo with no annual lock-in, and you can cancel anytime.