Get personalized optimization tips, understand your account health and set up completion on the improved "My AdMob page".

আপনি যে পৃষ্ঠাটির জন্য অনুরোধ করেছেন সেটি বর্তমানে আপনার ভাষায় উপলভ্য নয়। আপনি পৃষ্ঠার নিচে অন্য কোনও ভাষা বেছে নিতে পারেন বা Google Chrome-এর বিল্ট-ইন অনুবাদ ফিচার ব্যবহার করে আপনার পছন্দের ভাষায় যেকোনও ওয়েবপৃষ্ঠা অবিলম্বে অনুবাদ করতে পারেন।

Get started

Resolve common onboarding issues

Carefully review the details you receive from the Google Mobile Ads SDK to determine the issue you're having. Click on the error message you received to view more details about how to fix the issue. 

Expand all  Collapse all Account not approved yet

What this means:
Your account hasn’t been approved yet. When you first sign up for AdMob, your account is reviewed before it’s approved. This typically takes up to 24 hours, but in rare cases can take up to 2 weeks.

What you can do:
Check back later. In the meantime, make sure you’re in compliance with AdMob policies and restrictions. You’ll be notified via email if your account is not approved by AdMob.  

App not approved yet

What this means:
Your app hasn’t been approved yet. When you set up a new app in AdMob, your app must be reviewed and approved before it can fully serve ads.

What you can do:
Your app must meet the app readiness requirements before we can review and approve your app.

Ad request doesn’t meet size requirements

What this means:
The ad request doesn’t meet the size requirements for the banner ad format. 

What you can do:
Review the size requirements for banner ad units (Android, iOS, Unity). Verify and update your ad request parameters, then try again.

Ad request inconsistent with device platform

What this means:
The operating system (OS) platform specified in the ad request doesn’t match the device platform. For example, the ad request specifies Android but the device is iOS.

What you can do:
Make sure your SDK and device platform match.

Ad unit doesn’t match format

What this means:
The ad unit ID isn’t valid for the ad format you selected.

What you can do:
Check your ad unit ID to make sure it’s created for the right format, then try again. 

You must create the ad unit for a specific format. Learn more about ad units, ad formats, & ad types.

Asset uses ImageView, not MediaView

What this means:
Your native ad incorrectly uses ImageView to render the main image asset. Native ads must use MediaView, not ImageView. 

What you can do:
Update your image asset settings, then try again. Learn more about MediaView for native ads (Android, iOS).

Frequency cap reached

What this means:
A frequency cap is set for this ad unit. This means that this ad unit limits the number of ads shown to an individual user. 

What you can do:
To fix, update the ad unit’s frequency cap settings in AdMob, then try again.

Native ad request not valid

What this means:
The native ad request isn’t valid. 

What you can do:
Ensure that you’ve correctly followed the instructions for implementing native templates (Android, iOS), then try again. Also, make sure your native ad implementation follows the applicable policy guidelines.

No ads meet eCPM floor

What this means:
We can’t fill the ad request because no ads meet the eCPM floor for the ad unit. 

What you can do:
Consider setting a lower eCPM floor in AdMob.

Publisher data not found  

What this means:
Publisher data for this ad unit can’t be found. If you recently added the ad unit, keep in mind it can take some time for ads to appear.

What you can do:
Wait up to one hour for new ad units. If it’s been more than an hour or so since you’ve added the ad unit:

  • Verify the ad unit code is correct 
  • Check for account errors, like incomplete billing information or other setup issues
  • Resolve any policy issues in your Policy center

Note: If your account has been disabled due to invalid activity, you won’t be able to sign into your account. Learn more

Smart segmentation didn’t return an ad

What this means:
The ad unit is set up for smart segmentation, so the ad isn’t filled when the request is from a purchaser device.

What you can do:
Switch to a non-purchaser device to test ad requests for this ad unit.

Unsupported device

What this means:
The ad request comes from an unsupported mobile device.

What you can do:
Supported devices include Android and iOS mobile phones and tablets. Try again from a supported device.

Video ad request not valid

What this means:
The video ad request isn’t valid. This could be due to an invalid video duration or invalid ad type parameters.

What you can do:
Make sure your ad implementation follows the applicable guidelines (Android, iOS, Unity) then try again.

Was this helpful?

How can we improve it?
Show your support to promote DEI in Gaming by turning intentions into action!

Check out the newly launched Diversity in Gaming website, where you can find video stories and written pledges from global gaming developers. This campaign centers on 3 pillars: diverse teams, diverse games and diverse audiences showing how diversity is not just good for gamers, but for business as well. Show your support by taking the pledge to promote DEI in Gaming and share it on social!

Learn More

Clear search
Close search
Google apps
Main menu