Ads
one build, four networks.

01How a rewarded video is credited

1. The app asks for a sessionIt calls requestAdSession, which checks the daily cap and the cooldown and returns a one-time nonce.
2. The app shows the videoIt passes the user id and the nonce to the ad SDK (app/lib/ads/native_adapters.dart).
3. The ad network calls your functionAfter the user watched, the network's server calls ssvAdmob, ssvApplovin, ssvUnity or ssvIronsource.
4. The function verifies and credits onceIt checks the network's signature (a bad signature gets 403), removes duplicates, matches the pending session of the same user and credits the points in one transaction. A mismatch opens a fraud flag that you review in the console.

02Choose the network

In the console open Ads and pick the Ad network. The default is AdMob. The app reads the choice from config/public, so switching needs no new build. All four SDKs are inside every build.

Users who bought remove-ads, and users with an active VIP subscription, see no interstitials and no banners (showsAds in app/lib/data/models.dart). Rewarded videos stay available because the user chooses them.

03Ids and keys per network

Each network has its own section in the console (AdMob units, AppLovin MAX units, Unity Ads units, ironSource LevelPlay units). The Status page warns when the chosen network lacks its required ids or its verification secret.

Secrets are write-only in the console, only an owner can change them, and they are stored encrypted with ADMIN_SECRET_KEY. The console writes them to config/private, which only Cloud Functions can read.

04Server-to-server callback URLs

Replace REGION-PROJECT with your region and project id, for example us-central1-my-project. The exact URLs are printed by firebase deploy and shown in Firebase console → Functions. Set the console's Backend → Cloud Functions base URL to https://REGION-PROJECT.cloudfunctions.net as well.

AdMob

Where: AdMob → Apps → Ad units → your rewarded unit → Server-side verification.

https://REGION-PROJECT.cloudfunctions.net/ssvAdmob

AppLovin MAX

Where: MAX → Manage → Ad Units → your rewarded unit → S2S Rewarded Callback URL.

https://REGION-PROJECT.cloudfunctions.net/ssvApplovin?user_id={USER_ID}&custom_data={CUSTOM_DATA}&event_id={EVENT_ID}&event_token={EVENT_TOKEN}&amount={AMOUNT}&currency={CURRENCY}&ad_unit={AD_UNIT_ID}&ts={TS}

Unity Ads

Where: e-mail Unity Ads support with your Game IDs and this URL. They reply with the secret; enter it as Unity S2S secret.

https://REGION-PROJECT.cloudfunctions.net/ssvUnity

ironSource LevelPlay

Where: LevelPlay → Settings → Server-to-server callback → Callback URL. Enable it for Rewarded, and set the Private Key you also enter in the console.

https://REGION-PROJECT.cloudfunctions.net/ssvIronsource

How each callback is checked

05Test ids ship by default

The package contains only Google's public AdMob test ids; a test enforces it. With AdMob selected and no unit ids entered, the app falls back to Google's test units (app/lib/ads/ad_adapter.dart), so you see test ads during development. They never earn anything. The other three networks show nothing until their ids are entered.

06Replace the AdMob test app ids

The Google Mobile Ads plugin needs an AdMob app id inside the app itself. The package ships Google's test app ids:

Replace both with your own app ids from AdMob → Apps → App settings (one Android app, one iOS app).

The Google plugin is in every build and also provides the consent form below, so keep a valid AdMob app id even if you serve ads from another network.

If you use another network on iOS, also add that network's SKAdNetworkItems entries to Info.plist as its integration guide describes. The package lists Google's entry only.

07Consent (UMP)

Before any ad request the app runs Google's User Messaging Platform (gatherConsent() in app/lib/ads/native_adapters.dart): it shows the consent form when required (GDPR, US states) and passes the result to whichever network is active. Users can reopen it in Settings → Ad privacy when their region requires it.

1. Create the messagesAdMob → Privacy & messaging. Create the GDPR message (and the US state regulations message if you serve the US) for your apps.
2. Add your ad partnersIf you use AppLovin, Unity or ironSource, add them to the ad partners list of the GDPR message.
3. iOS tracking textInfo.plist contains NSUserTrackingUsageDescription. Adjust the text to your app.

08Check it worked

• Console → Status shows no warning for "Ad unit ids set for the chosen network" and "Rewarded-ad verification secret set"
• Watch one video on a real device: the balance goes up within seconds and the console Ledger shows an ad row
• No new rows in Fraud flags for your own test views