Promptwatch Logo

Google AdMob Reward Verification

Sends server-side verification callbacks to confirm users completed rewarded ad views.
WebhookAdvertisingVerification

What is Google AdMob Reward Verification?

Google AdMob Reward Verification is an HTTP callback sent to an endpoint chosen by the app developer. It arrives after a user interacts with a rewarded ad or rewarded interstitial. Despite appearing in bot catalogs, it does not crawl a website or discover links.

Each callback carries details about one reward event in its query string. These can include the reward item, amount, ad unit, timestamp, and a unique transaction ID. Google also sends a signature and key_id, allowing the receiver to validate the query data with a public key from the AdMob key server.

The configured endpoint should return HTTP 200 after handling a valid callback. When Google cannot reach it or receives another status, the service may retry up to five times at one-second intervals. Several requests with the same transaction ID can therefore be delivery attempts for one event.

This traffic has no search or training purpose. It does not fetch site content and cannot improve AI visibility. Its only documented job is to let an application verify an advertising reward on the server.

Not relevant for AI search

Is Google AdMob Reward Verification relevant for AI search?

No. Google AdMob Reward Verification is not part of AI search or training, so allowing or blocking it does not change your AI visibility.

Google AdMob Reward Verification is not a crawler. It delivers webhook notifications to endpoints you registered, so it never fetches public content for an AI product. Robots.txt does not apply, and allowing or blocking it has no effect on AI search or training.

How to handle Google AdMob Reward Verification

Route these requests only to the callback path configured in AdMob. Robots.txt is irrelevant even though the metadata has a compliance value: this is direct endpoint delivery and there is no stable crawler token to address in a robots group.

Verify the complete signed query data with an ECDSA-capable library. Use key_id to select the right AdMob public key, and do not cache Google's rotating keys for more than 24 hours. Store transaction_id as a unique value so retries cannot grant the reward twice.

Return HTTP 200 once the callback has been accepted and handled. Signature verification should be the main authenticity check; Google also documents reverse DNS as an origin check. Disabling the route stops server-side reward verification for the affected ad unit and does nothing to AI crawling.

Examples

  • A game receives a signed callback for five coins. Its server verifies the query string, inserts the transaction ID with a uniqueness constraint, and credits the account once.
  • During a deployment, the callback route responds with 500. Google retries the same transaction, and the recovered service recognizes the ID instead of issuing a second reward.

Frequently asked questions about Google AdMob Reward Verification

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

The app's ad unit has server-side verification enabled. Google calls the configured URL to report that a user should receive a reward.

Be the brand AI recommends

Monitor your brand's visibility across ChatGPT, Claude, Perplexity, and Gemini. Get actionable insights and create content that gets cited by AI search engines.

Promptwatch Dashboard