Integration · Ad monetization
RevenueDot verifies AdMob rewarded ads on its own server. AdMob calls RevenueDot's callback URL with a request signed by Google, a reward rule grants in-app currency or temporary access once, and your app polls for the result. A modified app cannot grant itself a reward. Connecting your AdMob account is optional and only loads ad unit names.
What teams do with it
ca-app-pub-…/5224354917.What RevenueDot sends
https://api.revenuedot.app/v1/ads/admob/ssv on RevenueDot Cloud, or <your server>/v1/ads/admob/ssv when self-hosted.https://www.gstatic.com/admob/reward/verifier-keys.json and records each reward once.reward_amount times a multiplier) or Temporary access to an entitlement. A project can have up to 200 rules.GET /v1/subscribers/{app_user_id}/ads/reward_verifications/{client_transaction_id} up to 10 times and gets pending, verified (with the reward) or failed.VIRTUAL_CURRENCY_TRANSACTION webhook goes out with source: "ad_reward". A callback for an ad unit that is not yours fails as unknown_ad_unit.Setup
In RevenueDot, open Ads > Rewards and copy the AdMob callback URL.
In AdMob, open each rewarded ad unit, turn on Server-side verification and paste the URL. AdMob's Verify URL button calls it without parameters, and RevenueDot answers 200.
After the ad loads, generate a reward verification token with the SDK and pass its appUserID and customData to AdMob's server-side verification options. When the reward callback fires, poll for the result.
Open Ads > Rewards > New rule. Choose In-app currency or Temporary access, and optionally limit it by app, ad unit or reward item.
Click Send test reward for an app user ID. It runs the same rules and grants as a real callback, marked sandbox in the ledger.
Open Integrations > Google AdMob, select Connect with Google and allow read-only access. RevenueDot loads up to 5,000 ad units and refreshes them once a day.
The same two calls exist on Android. With RevenueCat's iOS AdMob adapter, ad.enableRewardVerification() does these steps for you.
// After the rewarded ad loads
let token = Purchases.shared.generateRewardVerificationToken(impressionId: impressionId)
let options = ServerSideVerificationOptions()
options.userIdentifier = token.appUserID
options.customRewardString = token.customData
rewardedAd.serverSideVerificationOptions = options
// When the ad's reward callback fires
let result = await Purchases.shared.pollRewardVerification(clientTransactionID: token.clientTransactionID)
if let gems = result.verifiedReward?.virtualCurrency { showReward(gems.amount) }| Reason | What happened | What to do |
|---|---|---|
unknown_ad_unit | The callback's ad unit is not one of the project's | Connect AdMob, or name the ad unit on a reward rule |
missing_user | AdMob's callback had no user ID | Set userIdentifier (iOS) or setUserId (Android) to the token's appUserID |
user_mismatch | The poll came from a different customer than the reward's user ID | Generate the token after the customer logs in, and pass its appUserID |
grant_failed | The matching rule names a currency or entitlement that no longer exists | Fix or delete the rule |
Failure reasons in the rewards ledger.
REVENUEDOT_GOOGLE_OAUTH_CLIENT_ID and REVENUEDOT_GOOGLE_OAUTH_CLIENT_SECRET, or each project enters its own Google OAuth client ID and Google OAuth client secret on the AdMob page.https://www.googleapis.com/auth/admob.readonly, and the refresh token is stored encrypted. Disconnect deletes the tokens and the loaded ad units.FAQ
Copy the AdMob callback URL from Ads > Rewards in RevenueDot, turn on Server-side verification on each rewarded ad unit in AdMob and paste the URL. Pass the SDK's reward verification token to AdMob and poll for the result. RevenueDot checks Google's signature and applies your reward rule.
No. Only a callback signed by Google can trigger a reward, and RevenueDot accepts callbacks only for your ad units. Each reward is recorded once, so a callback Google sends twice never credits twice.
No. Connecting loads ad unit names and tells reward verification which ad units are yours. Without it, rewarded ads still work when each reward rule names its ad unit.
RevenueDot answers the same SDK calls and reward poll as the RevenueCat SDKs. RevenueCat does not publish its callback URL or how it configures rewards, so the callback URL and reward rules are RevenueDot's own (checked October 2026). Google's own steps are in its server-side verification guide.
Sources: Google AdMob · Google: AdMob server-side verification · Google: AdMob API. Google AdMob is a trademark of its owner, used to describe compatibility. RevenueDot is not affiliated with or endorsed by it.
Get started
Start free on RevenueDot Cloud, free up to $10,000 a month in tracked revenue. Integrations are included on every plan.
Already have an account? Sign in · Prefer your own servers? Self-host free