message  Send Feedback


Under the Google EU User Consent Policy, you must make certain disclosures to your users in the European Economic Area (EEA) and obtain their consent to use cookies or other local storage, where legally required, and to use personal data (such as AdID) to serve ads. This policy reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR).

It is recommended that you determine the status of a user's consent at every app launch. The user consent status is held on the device until a condition changes which requires the user to consent again, such as a change in publishers.

For more information, see here.




  deviceIds: string[]
): Promise<void>;

If using a real device to test, ensure the device ID is provided to the Google AdMob SDK so any mock debug locations can take effect.

Emulators are automatically whitelisted and require no action.

If you are unsure of how to obtain a device ID, see react-native-device-info.


  • deviceIds: string[]
    An array of testing device ID.


getAdProviders(): Promise<AdProvider[]>;

Returns a list of ad providers currently in use for the given AdMob App ID.

If requesting consent from the user via your own method, this list of ad providers must be shown to the user for them to accept consent.


import { AdsConsent } from '@react-native-firebase/admob';
const providers = await AdsConsent.getAdProviders();



Returns the current consent status of the user.

The user consent status may change at any time, therefore don't reuse old values locally and always request the current value at any time consent is required.


import { AdsConsent } from '@react-native-firebase/admob';
const status = await AdsConsent.getStatus();


  publisherIds: string[]
): Promise<AdsConsentInfo>;

Requests user consent for a given list of publisher IDs.

The list of publisher IDs can be obtained from the settings panel on the Google AdMob console. If the list of publisher IDs has changed since the last time a user provided consent, their consent status will be reset to 'UNKNOWN' and they must provide consent again.

If the request fails with the error "Could not parse Event FE preflight response", this means the state of your Google AdMob account is not complete. Ensure you have validated your account and have setup valid payment information. This error is also thrown when a Publisher ID is invalid.

The response from this method provides request location and consent status properties.

If request location is within the EEA or unknown, and the consent status is also unknown, you must request consent via the showForm() method or your own means.

If the consent status is not unknown, the user has already previously provided consent for the current publisher scope.


import { AdsConsent } from '@react-native-firebase/admob';
const consent = await AdsConsent.requestInfoUpdate(['pub-6189033257628554']);
console.log('User location within EEA or Unknown:', consent.isRequestLocationInEeaOrUnknown);
console.log('User consent status:', consent.status);


  • publisherIds: string[]
    A list of publisher IDs found on your Google AdMob dashboard.


  geography: DISABLED | EEA | NOT_EEA
): Promise<void>;

Sets the debug geography to locally test consent.

If debugging on an emulator (where location cannot be determined) or outside of the EEA, it is possible set your own location to test how your app handles different scenarios.

If using a real device, ensure you have set it as a test device via addTestDevice() otherwise this method will have no effect.


import { AdsConsent, AdsConsentDebugGeography } from '@react-native-firebase/admob';
// Set disabled
await AdsConsentDebugGeography.setDebugGeography(AdsConsentDebugGeography.DISABLED);
// Set within EEA
await AdsConsentDebugGeography.setDebugGeography(AdsConsentDebugGeography.EEA);
// Set outside EEA
await AdsConsentDebugGeography.setDebugGeography(AdsConsentDebugGeography.NOT_EEA);



): Promise<void>;

Manually update the consent status of the user.

This method is used when providing your own means of user consent. If using the Google-rendered form via showForm(), the consent status is automatically set and calling this method is not required.

This method can also be used to reset the consent status, by setting it to AdsConsentStatus.UNKNOWN, which may be useful in certain circumstances.


import { AdsConsent, AdsConsentStatus } from '@react-native-firebase/admob';
// User accepted personalized ads
await AdsConsent.setStatus(AdsConsentStatus.PERSONALIZED);



  tag: boolean
): Promise<void>;

If a publisher is aware that the user is under the age of consent, all ad requests must set TFUA (Tag For Users Under the Age of consent in Europe). This setting takes effect for all future ad requests.

Once the TFUA setting is enabled, the Google-rendered consent form will fail to load. All ad requests that include TFUA will be made ineligible for personalized advertising and remarketing. TFUA disables requests to third-party ad technology providers, such as ad measurement pixels and third-party ad servers.

To remove TFUA from ad requests, set the value to false.


import { AdsConsent } from '@react-native-firebase/admob';
// User is under age of consent
await AdsConsent.setTagForUnderAgeOfConsent(true);


  • tag: boolean
    The boolean value to tag for under age consent.


  options?: AdsConsentFormOptions
): Promise<AdsConsentFormResult>;

Shows a Google-rendered user consent form.

The Google-rendered consent form is a full-screen configurable form that displays over your app content. The form allows the following configuration options:

  1. Consent to view personalized ads (via withPersonalizedAds).
  2. Consent to view non-personalized ads (via withNonPersonalizedAds).
  3. Use a paid version of the app instead of viewing ads (via withAdFree).

Every consent form requires a privacy policy URL which outlines the usage of your application.

You should review the consent text carefully: what appears by default is a message that might be appropriate if you use Google to monetize your app.

If providing an ad-free version of your app, ensure you handle this once the form has been handled by the user via the userPrefersAdFree property. The users preference on consent is automatically forwarded onto the Google Mobile SDKs and saved.

If the user is outside of the EEA, the request form will error.


import { AdsConsent, AdsConsentStatus } from '@react-native-firebase/admob';
async function requestConsent() {
const consent = await AdsConsent.requestInfoUpdate(['pub-6189033257628554']);
// Check if user requires consent
if (consent.isRequestLocationInEeaOrUnknown && consent.status === AdsConsentStatus.UNKNOWN) {
// Show a Google-rendered form
const result = await AdsConsent.showForm({
privacyPolicy: '',
withPersonalizedAds: true,
withNonPersonalizedAds: true,
withAdFree: true,
console.log('User accepted personalized: ', result.status === AdsConsentStatus.PERSONALIZED);
console.log('User accepted non-personalized: ', result.status === AdsConsentStatus.NON_PERSONALIZED);
console.log('User prefers Ad Free version of app: ', result.userPrefersAdFree);


  • options: (optional) AdsConsentFormOptions
    An AdsConsentFormOptions interface to control the Google-rendered form.

React Native Market

Looking for pre-built React Native apps to kick start your next project? Check out the React Native Market by Invertase.

Your purchases help support our open-source projects such as React Native Firebase. All items are currently 50% off to celebrate the release of React Native Firebase version 6.
shopping_cartVisit React Native Market