Bot intelligence record

Google AdMob Reward Verification

Usually allow

Use the google-admob-reward-verification identifier to separate Google webhook or service callback traffic from normal visitor requests in server logs.

Webhook Verified Bot Confidence: Medium Verified: Yes robots.txt: No
Operator
Google
Family
Google
Type
Webhook
Source type
Verified Directory
Last checked
2026-05-20

User-Agent Pattern

Google
google-admob-reward-verification
Verification note

User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.

Robots.txt Snippet

Click snippet to copy
User-agent: google-admob-reward-verification Disallow: /

Click the snippet to copy it, or highlight the text manually.

Handling Guidance

No

This bot is usually safe to allow when the request source is verified and the traffic matches your site policy.

Webhook notifications, callbacks, payment events, or service-to-service integration requests.

Record Details

Structured data
Operator
Google
Family
Google
Type
Webhook
Purpose
Webhook
Identity type
Verified Bot
Confidence
Medium
Last verified
2026-04-19
Last checked
2026-05-20
Source type
Verified Directory
Verification
Verified on bots.fyi. Treat as a webhook/service identifier rather than a browser-style crawl signature.
Spoofing risk
User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.

Notes

Google AdMob Reward Verification is listed in the Botcrawl directory as a webhook callback service from Google. The primary identifier for log review is google-admob-reward-verification.

Identification

  • User-agent pattern: google-admob-reward-verification
  • Family: Google
  • Type: Webhook
  • Kind: Webhook

Common use

Webhook notifications, callbacks, payment events, or service-to-service integration requests.

Verification and handling

Verified on bots.fyi. Treat as a webhook/service identifier rather than a browser-style crawl signature.

Directory guidance marks the risk level as Safe and the blocking decision as No. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.

Robots.txt handling: No.

Evidence and Source

  • Verified on bots.fyi. Treat as a webhook/service identifier rather than a browser-style crawl signature.
  • Match `google-admob-reward-verification` as a case-insensitive substring in HTTP user-agent logs. Do not treat a user-agent match alone as proof of identity for allow-listing.
  • Webhook notifications, callbacks, payment events, or service-to-service integration requests.
  • User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.

Monitor This Bot In Edge

Botcrawl Edge

Use Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.