AdMob Ads

AdMob lets you display Google ads inside your app to generate revenue. Appilix supports two ad formats: Banner Ads, which appear at the bottom of the screen, and Interstitial Ads, which are full-screen ads shown at natural transition points. You can control exactly which pages show each type of ad.

Consent for users in the EEA and UK is handled for you — see the EU User Consent section below.

AdMob Application ID

Every AdMob integration starts with your App ID — a unique identifier that connects the app to your AdMob account. You need a separate App ID for Android and iOS.

• Maximum length: 200 characters
• Allowed characters: a-z, 0-9, ~, -

Test App IDs

Use these during development to see real ad placements without affecting your live metrics:

Replace with your real App ID before publishing.

Banner Ads

Banner Ads appear as a rectangular strip at the bottom of the screen and remain visible while the user browses.

Banner Ad Unit ID

• Maximum length: 200 characters
• Allowed characters: a-z, 0-9, -, /

Test Banner Ad Unit IDs

Visibility Rules

Control which pages show the banner:

• Show Banner Ad Only on These URLs — The banner appears only on matching pages.
• Hide Banner Ad on These URLs — The banner is hidden on matching pages, visible everywhere else.

Enter one domain, full URL, or URL fragment per line. Supports wildcard patterns (*) and exact match brackets [ ].

Interstitial Ads

Interstitial Ads are full-screen ads that cover the entire display. They should appear only at natural pause points — between pages, after completing a task, or when the user is about to move on.

Interstitial Ad Unit ID

• Maximum length: 200 characters
• Allowed characters: a-z, 0-9, -, /

Test Interstitial Ad Unit IDs

Visibility Rules

• Show Interstitial Ad Only on These URLs — The interstitial is triggered only on matching pages.
• Hide Interstitial Ad on These URLs — The interstitial is suppressed on matching pages.

Triggering on Demand via JavaScript Bridge

You can also show interstitial ads programmatically from your website at any moment — not just on page load. See the Showing Interstitial Ads article for the JavaScript Bridge implementation.

EU User Consent

Google's EU User Consent Policy requires a certified Consent Management Platform to gather consent before ads are requested from users in the EEA and the UK. Appilix includes Google's own User Messaging Platform (UMP), so there is nothing to enable or configure — it works as soon as AdMob is set up.

When the app starts:

1. The app refreshes the consent information from Google.
2. If a consent form is required, it is shown before any ad loads.
3. Ads initialize only once Google reports that ads may be requested.

Users outside the EEA and UK never see a form, and ads load exactly as before.

Effect on Ad Revenue

If a user declines, the app requests no ads at all for that user — no banner, no interstitial. This is required behaviour, so expect some share of EEA/UK users to generate no ad revenue. If ads are missing for a European user, check the consent state before suspecting your Ad Unit IDs.

Letting Users Change Their Choice

Under TCF v2.2, withdrawing consent must be as easy as giving it, so apps serving EEA/UK users must offer a way back into the form. The app cannot place that link on your pages for you — your website has to render it, using two JavaScript Bridge actions:

• admob_consent_status — check whether the link should be shown at all, and whether ads are permitted
• admob_show_privacy_options — reopen Google's form when the user taps your link

See the AdMob Consent & Privacy Options article for the full implementation.