Ads error codes

ads error codes

Error codes are generated in the event of an error during ADS access to an IO-Link device. are listed in table „Error Codes". Unknown service primitive e.g. Error Codes ; The given currency is invalid for usage with ads. ; Invalid call to update this adaccount ; Failed to create custom audience. ; VAST XML Document Errors · VAST Creative File Errors · VAST Ad Request Errors · VAST Linear Tag Errors · VAST Non-linear Tag Errors · VAST Companion Ad Errors · VPAID.

Ads error codes - urbanization

ironSource SDK Error Codes

Error CodesAd UnitDescriptionN/A• Init failure of the mediation/Network
• Calling a Demand Only API in non Demand Only mode
• Calling a non Demand Only API in Demand Only mode InterstitialShow Fail: No ads to showRewarded VideoOfferwallInterstitialLoad Fail: Server response failed
Load Fail: Adapters loading failureInterstitialShow Fail: No internet connection; 
ShouldTrackNetworkState is enabledRewarded VideoShow Fail: No internet connectionOfferwallInterstitialShow Fail: Placement %@ has reached its limit as defined per pace
Show Fail: Placement %@ has reached its capping limitRewarded VideoOfferwallInterstitialShow Fail: Ad unit has reached its daily cap per sessionRewarded VideoRewarded VideoShow Fail: Cannot show an RV while another RV is showingRewarded VideoShow Fail: Show RV called when there are no available ads to showInterstitialShow Fail: Cannot show an interstitial while another interstitial is showingInterstitialLoad Fail: Cannot load an interstitial while another interstitial is showing

Common VAST Error Codes and How to Resolve Them

VAST error codes continue to disrupt publishers’ experience as they try to leverage video advertising for increasing revenue.

Whether or not to experiment with video advertising  has almost become an outdated question for a publisher. In order to maximise their revenue, publishers must focus on experimenting with programmatic video advertising, 

According to Cisco, 82% of the entire consumer internet traffic will be online videos by the end of It is evident that users consume video content more than other forms, giving publishers the opportunity to insert ads in between. 

But video advertising comes with its own set of challenges. Despite the technological advancements made in measuring a video ad’s performance, publishers still face error messages in VAST. These VAST error codes are mostly cryptic in nature and render publishers with important time lost. 

If publishers want their video advertising campaigns to succeed, understanding how to interpret and resolve VAST errors is important. 

What is a VAST error?

A VAST error can occur due to a number of reasons and is reported back in case any issue takes place. Ideally, after the code is served for a video ad, the user should be served with that particular ad. However, if the code served request leads to a VAST error, the issue is reported with a numerical code. 

On the basis of the type of VAST error that is reported, the video ad may or may not be served to the user. If the error reported back comes under the ‘non-fatal’ category, then the video player may still play the ad. On the other hand, a ‘fatal’ error will cause the video player to either request for another ad or abort the failed ad request. 

The table below classifies which VAST errors are fatal and which are non-fatal.

Here are some common VAST errors and how publishers can resolve them:

Common VAST Error Codes and Their Resolution

VAST Error

This error stands for Timeout of VAST URI. This VAST error normally indicates timeout of an unresponsive or faulty URI inside a VAST creative. However, ad tech experts have often associated a poor network connection or a very high level of latency as the primary causes for this error. 

To resolve this error, publishers can look at a few possible options:

  • Check the validity of the VAST URI. In most cases, this error occurs because of an unreachable or invalid URI. Checking and making sure that the URI becomes reachable and without faults should resolve the error.
  • Checking the internet connection can also be a possible solution for this problem. Most likely due to a faulty internet, the request time out occurs. 
  • Checking protocol issues can also resolve this issue. Sometimes, the URI is being hosted on HTTP but being served on HTTPS. 

VAST Error

This VAST error is displayed when the wrapper limit has been exceeded. The video player of the ad often has a pre-defined wrapper limit. Whenever that limit is reached, this error is likely to occur. This can happen if there are too many wrapper responses that have been received, but there is no inline response. Some other possible causes are the existence of daisy chaining (explained in the resolution for this error), empty VAST responses, and others. 

Publishers can possibly resolve this by the following solutions:

  • To accommodate the creatives, buyers can work with SSPs or publishers to increase the wrapper limit. 
  • Avoid daisy chaining which is the process in which ad calls are passed from one network to another. This can cause too many redirects from a video player before an actual media file makes a return, making the video player abort any ad request. 

VAST Error

This error generally occurs when an empty VAST response is returned. It is a common error when the ad request is generally contained within a third-party wrapper. Here’s how to resolve this:

Third-party networks often offer a fill rate of less than %. To assume the percentage of times that this error can occur, just consider the leftover % of the fill rate. For example, if the fill-rate promised by your third-party network is 60%, there is a 40% chance of this error occurring. The best way for publishers to resolve this is by enabling fallback in Google Ad Manager. This can be enabled by:

  • Sign in to your Google Ad Manager account. 
  • Click on Admin >> Video >> Video Settings
  • Enable Video Fallback
  • Click on Save

VAST Error

This error generally stands for a timeout that occurs when a media file is problematic. When the ad creative takes a lot more time than usual to load, then this error occurs. Normally the VAST ad unit contains a creative that has issues such as large size, incompatibility of the platform it is trying to serve at. This can be resolved in the following ways:

  • Publishers can increase their page load speed by optimizing their website layouts. This can be done by partnering with an ad network (like AdPushup). 
  • Another possible solution is increasing the video player’s timeout limit. 
  • Adjusting the bitrate for serving on mobile can also solve this error.

Bonus: General VPAID Error

While this is a VPAID error, if video advertising is being considered, this is one of the most common errors that publishers come across. It is also known as Error and often leaves publishers confused because it can have many different causes. Some of the possible causes are:

  • An IMA Adapter Tag in Ad Exchange is used with the IMA SDK, but a VPAID ad is returned instead. Error will be a fatal error here.
  • VPAID wrapper timeout.
  • VPAID wrapper is not buying video files.

Though the causes can be more than the above listed ones, there are some solutions on how to resolve this error. Publishers need to make sure that whichever VPAID creatives they are using are supported across all devices and video players. Whether or not a VPAID creative is eligible to serve can be checked in Google Ad Manager. Here’s how to do it:

  • Sign in to your Google Ad Manager account.
  • Click on Video >> Video Creative Profiles >> New Video Creative Profile.
  • Configuration for the video creative profile is required. The criteria for this include Name, Restrictions, Bitrate, and Resolution. Setting bitrate is optional. Additionally, under Restrictions, if publishers are allowing VPAID, and a VPAID creative is served, setting a bitrate becomes redundant as ads at any possible bitrate can serve.
  • Click on Save

A List of All the VAST Error Codes

Even though we have already covered the most commonly occurring VAST error codes, there are a plethora of others as well. Here’s a list of all VAST errors and what they mean:

VAST Error CodeCode DescriptionPossibility of Fatability
XML Parsing ErrorYes
VAST Schema Validation ErrorYes
1o2VAST version of response not supportedYes
Trafficking ErrorMaybe
Video player expecting different linearityMaybe
Video player expecting different durationMaybe
Video player expecting different sizeMaybe
General Wrapper errorYes
Timeout of VAST URIYes
Wrapper limit reachedYes
Empty VAST responseYes
General linear error. Video player is unable to display the linear ad.Yes
Unable to find Linear/MediaFile from URIYes
Timeout of MediaFile URIYes
Problem displaying MediaFileYes
General NonLinearAds errorYes
Unable to display NonLinear Ad because creative dimensions do not align with creative display area (i.e., creative dimension too large)Yes
Unable to fetch NonLinearAds/NonLinear resourceYes
Could not find NonLinearresource with supported typeYes
General CompanionAds errorMaybe
Unable to display companion because creative dimensions do not fit within Companion display areaMaybe
Unable to display Required CompanionMaybe
Unable to fetch CompanionAds/Companion resourceMaybe
Could not find Companion resource with supported typeMaybe
Undefined ErrorYes
General VPAID ErrorYes

We have picked this information directly from the IAB’s wiki for VAST error codes. For more information, you can read here. 

Best Practices for Publishers to Follow

While publishers can individually do VAST troubleshooting for these errors whenever they occur, the best solution would be to make sure that these errors never occur. Here are some best practices that publishers can follow:

  • Collaborate with your SSPs, DSPs, ad network, and other partners to consistently improve the performance of your VAST creatives. An ideal scenario would be for the VAST error codes to never occur. This will allow seamless ad serving, resulting in increased revenue. Work with your partners to understand the problems that are incessantly causing these errors. 
  • Always make sure that the DSPs scan the creatives beforehand. This will also benefit them and resolve error-causing issues prior to ad serving.

Related Terms

What is VAST?

VAST (Video Ad Serving Template) is a script that allows video players and ad servers to run video ads. VAST further gives publishers control over which ad they want to serve, how long the ad should play for, or if the ad is skippable, among other things. 

What is VPAID?

VPAID (Video Player Ad Interface) enables the interaction between video ads units and video ad players. With VPAID, advertisers are able to show interactive or rich media ads to their users, which VAST doesn’t allow. 

What are VAST tags? 

VAST tags are essentially no different than third-party ad tags. While the latter are codes for serving display ads, VAST tags are codes that enable the serving of video ads. 


Related Posts

Admob Ads Error Codes &#; App Advertising

Error Code 0 : ERROR_CODE_INTERNAL_ERROR
This indicates that something happened internally; for instance, an invalid response was received from the ad server.

Newly created Ad Units can take upto 2 hours to become active (SpinUp Time). Any Ad requests from newly created Ad Units would also receive Error Code 0 in response to Ad requests until they are ready to serve live ads.

What to do? Test Ads!!

Error Code 1 : ERROR_CODE_INVALID_REQUEST
The ad request was invalid; for instance, the ad unit ID was incorrect.

This commonly suggests that the Ad Request implementation is not as per the SDK’s requirements &#; Resources like the sample codes and sample apps provided in the developer documentation can help in implementing the functions correctly.

Error Code 2 : ERROR_CODE_NETWORK_ERROR

The ad request was unsuccessful due to network connectivity.

This could be due to a user’s phone switching networks or network disturbances distorting the communication between the app and the Ad Server. Some Telecom providers may also limit specific traffic due to policy, which can also lead to such an error.

Error Code 3 : ERROR_CODE_NO_FILL
Description (Dev Docs Link) : The ad request was successful, but no ad was returned due to lack of ad inventory.

Why is it Happening : Advertisers can target specific regions, platforms and user profiles based on business relevance, which can sometimes result in lower availability of Ads for a particular region or user profile. Error code suggests that the implementation is correct, and that the Ad Request was not filled because of lack of availability of a suitable Ad at that particular instant of time when an Ad Request was sent from the app.

Policy related restrictions on certain Apps or Ad Units will also lead to Error Code 3 being returned in response to Ad Requests.

What Can The Pub Do About it :

→ As we cannot manipulate advertiser demand, there are no particular ‘fixes’ for this error &#; the pub can cross-check the Ad Unit implementation to ensure that the Ad Units are implemented correctly.

→ Mediation : In some instances, certain Ad Networks may have limited performance in some regions or for specific formats, in which case the pubs can try using mediation to add other Ad Networks that may potentially perform well.

→ Check for Policy status for the Pub ID, the App and the Ad Unit ID. Also check the Brand Safety flags and Coppa status.

→ If the Pub can obtain Test Ads for an Ad Unit (Instructions) &#; then their implementation is correct, and the Ad Units will serve Ads normally when an Ad is available depending on advertiser demand.

Error Codes 8 : ERROR_CODE_APP_ID_MISSING
The ad request was not made due to a missing app ID.

Error Codes 9 : ERROR_CODE_MEDIATION_NO_FILL
The mediation adapter did not fill the ad request. If this error is returned from sprers.eue(), check sprers.euse() for the underlying cause.

Error Codes 10 : ERROR_CODE_REQUEST_ID_MISMATCH
The AdInfo object inside the ad request has mismatching request IDs.

Error Codes

Negative-value error codes are internal Facebook errors. Check for the actual failure code.

An unknown error occurred

, subcode

An unknown error occurred. This error may occur if you set to but the correct value should be .

Application request limit reached Application does not have permission for this action User request limit reached Invalid parameter

, subcode

Unsupported post request.

This error may occur if your access token is not added as a system user with appropriate permissions to the ad account that owns a Custom Audience. Verify the ad account in Business Manager and verify all system users appear under the ad account as :


  • Click on
  • Click the ad account
  • Select
  • Search for system user and add them as Admins
  • Retry your API call

, subcode

Invalid parameter.

The category you selected is no longer available. Several behavior-based targeting categories are deprecated. If you try to use them to create ads, your requests fails and returns this error. Use Targeting Search to see categories available for targeting.

, subcode

Invalid parameter.

This Task Combination Is Not Supported. To assign a user for this ad account valid capabilities, you should pass in a combination of tasks defined in the mapping. See Business Manager API, Permitted Roles.

Session key invalid or no longer valid Incorrect signature Invalid OAuth Access Token Permission error

, subcode

Custom Audience Terms Not Accepted: You&#;ll need to agree to the Custom Audience terms before you can create or edit an audience or an ad set. See Facebook, Custom Audience Terms

, subcode

Audience Size too Low: You cannot remove users from this audience because it will result in a low audience size and may result in under-delivery or non-delivery of your ads. Managing advertisements requires the extended permission `ads_management` and an application that is in our allow list to access the Marketing API Unable to display a preview of this ad The given currency is invalid for usage with ads. Invalid call to update this adaccount Failed to create custom audience.

subcode

No write permission for this ad account. Developer making this call must have permissions for the ad account to create an audience for it. Unknown Error Code

One or more of the given URLs is not allowed by the Stream post URL security app setting. It must match the Website URL or Canvas URL, or the domain must be a subdomain of one of the App&#;s domains. Read more about Login Security to learn more about app settings related to security.

Ad Create Failed - Too Many Ads: The account &#;account_id&#; has reached the maximum number of ads &#;max&#; Invalid Parameter In Spec: Parameter has invalid value or missing required parameter: &#;param-value&#; Invalid Campaign ID: You must specify a campaign, and the campaign specified must belong to the account specified and must not be deleted. Campaign Ended: You can&#;t edit ads in a campaign that has ended. Please create a new ad within this campaign, update the campaign end time, pick another campaign, or create a new campaign. Ad Bid Too High: Your bid is above the maximum for its type and placement. Please try again with a value below the maximum if you would like to raise your bid. Bid Too Low: Your bid is below the minimum for its placement and type. If you don&#;t want your ad to run at the minimum bid rate, please pause it. Otherwise, please increase the bid to be within the suggested range. Campaign budget was too low. Please increase the daily budget to at least 2 times the amount of the highest CPC ad bid, which is at least &#;minimum_budget&#;. You bid &#;bid&#;. The ad creative is invalid Ad Missing Targeting Spec: Ad spec needs a targeting spec. Please use targeting field to specify what audience the ad should be shown to. Field &#;countries&#; is required; all others are optional. Ad Create Failed: The Ad Create Failed for the following reason: &#;reason&#; Target Spec Invalid: The target spec is invalid: &#;reason&#; Ad Edit Failed - Spec Errors: &#;error&#; Invalid Cities: Please check that the format in which you are specify the cities is correct, and if you specify IDs, that they are of the correct type. This can not be the the ID of the page for the city; city ids are returned by, `/search?type=adcity`. Invalid Connection: You can only specify connections to objects you are an administrator or developer of. Invalid Negative Connections: If you specify negative targeting, you must be the administrator or developer of the objects whose fans you want to specify to exclude. You are not an admin of the following specified connections: &#;connections&#; Could not save creative Invalid Image Hash: Invalid Image Hash - &#;hash&#; Permission Error: Either the object you are trying to access is not visible to you or the action you are trying to take is restricted to certain account types. Ad targeting does not match targeting of the story: The targeting specified for this ad is not compatible with the story being boosted. Check the privacy and language/country targeting of the story you are trying to sponsor. Invalid object - not admin or object not public: The user is not an admin of the object or the object is not publicly accessible. Invalid URL For Creative Destination: Creative must have a valid destination URL, and if attached object is page, destination must match page. Ad Creation Limited By Daily Spend: The number of ads you can create in a given period of time has a limit determined by your daily spend level. Higher spend levels allow creation of more ads. Increase your daily spend limit or create fewer ads per time period. Campaign Update Failed: Campaign &#;campaign_id&#;: &#;reason&#; Campaign Creation Failed: &#;reason&#; Targeting declined due to policy: Invalid ads targeting. The targeting spec was declined due to policy restrictions. Not Allowed To Use View Tags: Only some partners are allowed to use view tags. Please verify that you are using an approved account. Custom Audience Unavailable: The custom audience you&#;re trying to use hasn&#;t been shared with your ad account. Please create or choose a different custom audience, or ask the owner of the custom audience to let you use it. The post does not belong to the specified Page: Post to be promoted does not belong to the Page specified. The post belongs to &#;otherDestination&#;; try using this as the destination or using a post that belongs to the specified Page. Specified Page: &#;destination&#;. Custom Audience Has Been Deleted: Cannot use deleted custom audience. Please choose another audience. Conversion Spec Needed: For ads pointing to an offsite location with a non-zero bid on actions, you must specify the conversion spec. Invalid aggregation day for conversion data. The aggregation day must be larger than or equal to 1. Adcreative Create Failed: The Adcreative Create Failed for the following reason: &#;reason&#; Cannot Use Syndicated Audiences From Multiple Partners: When specifying partner-created custom audiences for an ad, all audiences must be from the same provider. Failed to update the creative: Failed to update creative &#;id&#;. Failed for the following reason: &#;reason&#; Ad Needs Exclusion Targeting: This ad cannot be created with the targeting spec you selected. Your ad has a conversion objective that users can only do once, so you must target the ad at those users who have not already converted. If you are using the Facebook API, consider including the following string in your targeting spec: &#;exclusion-targeting-spec&#;. Invalid CPA Bid: The action type you selected is not allowed for Cost-Per-Action (CPA) bidding: &#;&#;action_type&#;&#;. Please change your optimization goal or switch your bid type to regular Optimized CPM. This type of page post is not eligible to be promoted. &#;debug_info&#; Conversion Tracking Pixel Permission Error: The conversion tracking pixel you&#;re trying to use is owned by another user and hasn&#;t been shared with you. Please use a tracking pixel that&#;s been shared with you or create a new one. Too many async requests The new budget value is too low: The new budget value of &#;new_budget&#; is too low. The minimum acceptable is &#;minimum_budget&#;. No supported fields were provided for updating the campaign No supported fields were provided for updating the ad Ad Update Failed &#;reason&#; You must specify an object_id for this adcreative type (creative type 27) There have been too many calls from this ad-account. Wait a bit and try again. You have overlapping locations specified in the geo_locations field. Your broader option will override the narrower option, please remove one to proceed. The promoted object is invalid: it could have been deleted or never existed. The given prediction id in a reach and frequency campaign is not reserved. The given reservation in a reach and frequency campaign is not finalized yet. The given reservation in a reach and frequency campaign is already finalized The prediction in a reach and frequency campaign is already reserved. This indicates the operation fails for an unknown reason. The given page types are not supported by the inventory manager. A finalized prediction order can not be cancelled. You can create a new prediction or delete the campaign. Conversion Spec Targets Invalid ID: You are targeting an ID in your conversion spec without admin permissions on that object. &#;debug_info&#; This Promotion Can&#;t Be Edited: This can&#;t be edited because you promoted it from your Page. Find the post on your Page to pause, delete, or update budget for this promotion. This Promotion Can&#;t Be Edited: This can&#;t be edited because you promoted it from your Page. Find the post on your Page to pause, delete, or update budget for this promotion.

Your bid strategy is invalid. Current available bid strategies are , , and . Please choose a valid bid strategy to suit your business goals. Effective as of

You are trying to set a bid strategy on an ad set in an ad campaign with campaign budget optimization enabled. Setting bid strategy on such an ad set is not allowed. Either remove bid strategy on your ad set or disable campaign budget optimization on your campaign. Effective as of

You are trying to set a bid strategy on an ad set in an ad campaign that does not use Auction buying type. Setting bid strategy on such an ad set is not allowed. Effective as of

Bid amount required: you must provide a bid cap or target cost in bid_amount field. For you must provide bid_amount field to set a bid cap. For , you must provide bid_amount field to set an average target cost goal. Effective as of

You can&#;t set a bid cap on ad sets with bid strategy. Please either remove bid_amount or change to use with bid_amount. Effective as of

Optimization Goal Isn&#;t Available: You can&#;t use the selected optimization goal for your campaign objective. Please select a different goal and edit your campaign.

We disallow creation of empty product sets for Advantage+ catalog ads. Please add products to your catalog and create a set that contains at least one product.

Unable to Create Campaign Using This Ad Account. To create Collaborative Ads campaigns, Brand Advertisers must use a separate ad account for each seller they partner with. Make sure you use a separate ad account associated with the seller who owns this catalog segment. Under limited availability.

Unable to Create Campaign Using This Catalog Segment. You cannot use this ad account to run ads for this catalog segment. The business created this catalog segment for a Brand Advertiser to use in Collaborative Ads. Choose a different ad account, or use this ad account to run campaigns using a product catalog instead. Under limited availability.

You can&#;t edit your pixel, conversion event, custom conversion or optimization for an ad set after the ad set is published. To run an ad set with your desired changes, create a new ad set.

A Complete List of Video Advertising Error Codes

/ YesGeneral linear errorThis can be caused when a video player is unable to display the linear ad. It may occur when the MediaFile is not a valid video file of the specified format, or because the browser restricted autoplay with sound, or another unknown reasonPublisher – Check for player issues, enable your player to detect for restricted autoplay, or alert the buyer
Buyer – Ensure that the VAST response returns a valid creativeYesMediaFile not foundThis can be caused when a file cannot be found from a MediaFile URIPublisher – Ensure that all MediaFiles in the response return a valid video asset. If not, alert the buyer
Buyer -Ensure that the VAST response returns a valid creative / NoTimeout of MediaFile URIThis can be caused by a problem fetching or playing the MediaFile, and could be any of the following:
  • The loadVideoTimeout is set too low in the IMA SDK. (the default is 8 seconds)
  • Low bandwidth or poor website implementation with competing requests that delay loading of the MediaFile
  • A video auto-plays in a mobile environment, whereas it should be click-to-play (there are some exceptions)
  • Showing video ads in an auto-play environment (for example, a playlist), while the window is not in focus (either another tab is selected, or window is minimized) (Chrome only)
Publisher – Increase the timeout limit of your player
Buyer – Ensure that any CDN-hosted creatives are returned within the specified media timeoutYesCould not find MediaFile that is supported by this video player, based on the attributes of the MediaFile elementThis can be caused by a VAST response that declares unsupported MIME types for all available MediaFiles. For example:
  • Bidder did not respect mime types in bid request
  • Exchange did not send correct mime types
  • May indicate that the wrong creative type attempted to play such as a Flash creative attempted to play on a mobile device or WebM on iOS
Publisher – Ensure that the creative format or technology requested is supported by the video player’s device and platform. For example, VPAID creatives should not be requested from mobile apps
Buyer – Ensure that all returned creatives respect the video format in the bid requestYesProblem displaying MediaFileThis can be caused when a faulty creative is returned due to a mismatch between the MIME type and the video file type, a CORS configuration on the creative’s CDN, transcoding-related reason such as an unsupported codec, or unsupported delivery methodPublisher – Alert the buyer
Buyer – Ensure that all creative MIME types and CDN configurations are accurateNoMissing required mezzanine fileThis can be caused a VAST response is returned without a required mezzanine file. Publishers with server-side ad implementations (SSAI) often require mezzanine files, which are raw high-quality video files for ad-stitching, or to generate video files of appropriate quality (VAST 4)Publisher – Alert the buyer
Buyer – Ensure that a mezzanine file is included in your response when required by the publisherYesMezzanine file downloaded for the first timeThis can be caused when the mezzanine file is downloaded for the first time, so no ad is served. It can also occur when an ad insertion is missed because the creative is being transcoded. It continues to occur until the creative is available for insertion (VAST 4)No action requiredYesAd rejected in VAST responseThis can be caused when the ad returned in the VAST response is rejectedPublisher – Alert the buyer
Buyer – Ensure that only approved creatives are returned in your VAST response, or that any advertisers or agencies hosting the creatives are aware of rejectionsYesInteractive unit in the InteractiveCreativeFile node was not executedThis can be caused when a creative defined in the InteractiveCreativeFile node does not executePublisher – Alert the buyer
Buyer – Ensure that any interactive creatives returned in your response successfully play when requestedYesVerification unit in the Verification node was not executedThis can be caused when the code referenced in the AdVerification node does not execute (VAST 4)Publisher – Alert the buyer
Buyer – Ensure that the verification code referenced in the response is correctly implemented according to the verification vendor

Error Code

Error code

Instructions

Investigation hint

Please exec sprers.eu before load ad

Initialize the sdk and then initiate an ad request

load time out

The ad object is not successfully returned within the specified time, and it is not recommended to initiate the request again.

resource error

Resource loading failed due to network and other reasons.

No fill

BadRequest: Http request pb error

Indicates that some necessary parameters have invalid values. Please check the integration guideline on Pangle platform

BadRequest: Empty Slot ID

Indicates that the slotID is null

BadRequest: Invalid Ad Size

Indicates that the AdSize is missing or an unsupported size is passed.

Invalid Slot ID

Indicates that the length of the slotID is incorrect, or an empty string is passed.

BadRequest: Ad counts error

Indicates that the is invalid

BadRequest: Image size error

Indicates that the image size is not supported.

Invalid App ID

Indicates that the app id is invalid or app id is missing

BadRequest: Slot ID and App ID is not matched

Indicates that the relationship between App Id and Slot Id is invalid or App Id is missing.

Invalid Package Name

Indicates that the package name of your project does not match the package name you filled in Pangle platform.

BadRequest: Ad Type and Slot Id is not matched

Indicates that Ad Type and Slot Id is not matched. For example, try to load a rewarded ad with a banner ad slot id.

BadRequest: Invalid SHA1 value

Indicates that the SHA1 is not matched with the SHA1 you entered on the Pangle platform

BadRequest: Incorrect API method

Indicates that the API method is incorrect

BadRequest: The SDK version is too low

Please update to the latest SDK

BadRequest: verification failed

Update to the latest SDK

Unsupported regions

Indicates that your Pangle account only support China traffic. No ads returned when you try to load ads outside of china(non-china IP)

BadRequest: Incorrect API method

There are three situations: One: IOS: ad request method error, SDK rendering advertisement and self rendering ad request method are different. Solution: Use the SDK rendering method and the correct parameters to request SDK rendering ad. Two: The server slotID configuration is not effective: you need to wait minutes for the new slotID to request the ad. Three: Low SDK version: the SDK version used is too low (lower than ) and does not support personalized SDK rendering function. Solution: update to the latest version of the Platform SDK.

Incorrect Bidding Ad Placement

1. Bidding ad placement can not be used in non-bidding environment 2. Non-bidding ad placement can not be used in bidding environment.

Servers error

Server error, if the error could be % replicated, please give feedback to us via [email protected]

-1

Data parsing failed.

For the collection of client code problems, you can first check the following situations: One: show is called in the child thread. Two: ViewGroup is empty when registering click events. Three: The business logic of the media in the onFeedLoaded callback is abnormal, which causes the SDK to go to the onError callback. If the above ideas still can not solve your problem, you can contact the TS

-2

Network error

Indicates that your network connection is not stable enough.

Prohibit requesting ads

Pangle don't have Children ads, you can not get fill when coppa = 1

Data parsing failed for template ads

Please update to the latest sdk.

Template missing

Please update to the latest sdk.

Subtemplate missing

Please update to the latest sdk.

SDK rendering timeout

Please update to the latest sdk.

SDK rendering timeout

Please update to the latest sdk.

Template loads failed

Please update to the latest sdk.

Dynamic-Native JS parsing error

Re-request ads

Dynamic-Native JS parsing timeout

Re-request ads

Dynamic-Native rendering error

Re-request ads

Dynamic-Native SDK parsing error

Re-request ads

Dynamic-Native SDK parsing timeout

Re-request ads

Dynamic-Native SDK rendering error

Re-request ads

Link establishment failed

Check network status and request ads again

Link establishment timeout

Check network status and request ads again

Ads returned abnormally

Re-request ads

Ads parsing failed

Re-request ads

Ads parsing failed

Re-request ads

Ads parsing abnormally

Re-request ads

Ads read and write failed

Re-request ads

Ads read and write failed

Re-request ads

Ads download failed

Re-request ads

Ads download abnormally

Re-request ads

Ads request cancelled

Re-request ads

Image load abnormally

Re-request ads

Error Codes

AD_PARAM_INNER

0

Internal error.

  • Check whether the HMS Core (APK) version is or later.
  • Check whether the network connection is normal.

AD_PARAM_INVALID_REQUEST

1

The ad request is invalid due to specific causes, such as not setting the ad slot ID or invalid banner ad size.

  • Check whether the ad slot you have applied for is effective.
  • Check whether the app package name in the request is the same as the package name you have used to apply for the ad slot.
  • Check whether the ad size is set correctly.

AD_PARAM_NETWORK_ERROR

2

The ad request fails due to a network connection error.

Check whether the network connection is normal.

AD_PARAM_NO_AD

3

The ad request is successful, but the server does not return any available ad asset.

Check whether the country or region of the test device is correctly configured.

AD_PARAM_AD_LOADING

4

The ad is being requested and cannot be requested again.

Check whether the ad request is sent repeatedly.

AD_PARAM_LOW_API

5

The API version is not supported by the HUAWEI Ads SDK.

  • Check whether the HMS Core (APK) version is or later.
  • Check whether the value of minSdkVersion in the app is 19 or later.

AD_PARAM_BANNER_AD_EXPIRE

6

The banner ad has expired.

Request the ad again. Do not cache the ad.

AD_PARAM_BANNER_AD_CANCEL

7

The banner ad task is removed.

Request the ad again. Do not cache the ad.

AD_PARAM_HMS_NOT_SUPPORT_SET_APP

8

The HMS Core (APK) version does not support the setting of AppInfo.

Update HMS Core (APK) on your device to the latest version.

Error Codes

Negative-value error codes are internal Facebook errors. Check for the actual failure code.

An unknown error occurred

, subcode

An unknown error occurred. This error may occur if you set to but the correct value should be .

Application request limit reached Application does not have permission for this action User request limit reached Invalid parameter

, subcode

Unsupported post request.

This error may occur if your access token is not added as a system user with appropriate permissions to the ad account that owns a Custom Audience. Verify the ad account in Business Manager and verify all system users appear under the ad account as :


  • Click on
  • Click the ad account
  • Select
  • Search for system user and add them as Admins
  • Retry your API call

, subcode

Invalid parameter.

The category you selected is no longer available. Several behavior-based targeting categories are deprecated. If you try to use them to create ads, your requests fails and returns this error. Use Targeting Search to see categories available for targeting.

, subcode

Invalid parameter.

This Task Combination Is Not Supported. To assign a user for this ad account valid capabilities, you should pass in a combination of tasks defined in the mapping. See Business Manager API, ads error codes, Permitted Roles.

Session key invalid or no longer valid Incorrect signature Invalid OAuth Access Token Permission error

, subcode

Custom Audience Terms Ads error codes Accepted: You&#;ll need to agree to the Custom Audience terms before you can create or edit an audience or an ad set. See Facebook, Custom Audience Terms

, subcode

Audience Size too Low: You cannot remove users from this audience because it will result in a low audience size and may result in under-delivery or non-delivery of your ads. Managing advertisements requires the extended permission `ads_management` and an application that is in our allow list to access the Marketing API Unable to display a preview of this ad The ads error codes currency is invalid for usage with ads. Invalid call to update this adaccount Failed to create custom audience.

subcode

No write permission for this ad account. Developer making this call must have permissions for the ad account to create an audience c+ + runtime error wine it. Unknown Error Code

One or more of the given URLs is not allowed by the Stream post URL security app setting. It must match the Website URL or Canvas URL, or the domain must be a subdomain of one of the App&#;s domains. Read more about Login Security to learn more about app settings related to security.

Ad Create Failed - Too Many Ads: The account &#;account_id&#; has reached the maximum number of ads &#;max&#; Invalid Parameter In Spec: Parameter has invalid value or missing required parameter: &#;param-value&#; Invalid Campaign ID: You must specify a campaign, and the campaign specified must belong to the account specified and must not be deleted. Campaign Ended: You can&#;t edit ads in a campaign that has ended. Please create a new ad within this campaign, update the campaign end time, pick another campaign, or create a new campaign. Ad Bid Too High: Your bid is above the maximum for its type and placement. Please try again with a value below the maximum if you would like to raise your bid. Bid Too Low: Your bid is below the minimum for its placement and type, ads error codes. If you don&#;t want your ad to run at the minimum bid rate, please pause it. Otherwise, ads error codes, please increase the bid to be within the suggested range. Campaign budget was too low. Please increase the daily budget to at least 2 times the amount of the highest CPC ad bid, which is at least &#;minimum_budget&#. You bid &#;bid&#. The ad creative is invalid Ad Missing Targeting Spec: Ad spec needs a targeting spec, ads error codes. Please use targeting field to specify what audience the ad should be shown to. Field &#;countries&#; is required; all others are optional. Ad Create Failed: The Ad Create Failed for the following reason: &#;reason&#; Target Spec Invalid: The target spec is invalid: &#;reason&#; Ad Edit Failed - Spec Errors: &#;error&#; Invalid Cities: Please check that the format in which you are specify the cities is correct, and if you specify IDs, ads error codes, that they are of the correct type. This can not be the the ID of the page for the city; city ids are returned by, ads error codes, `/search?type=adcity`. Invalid Connection: You can only specify connections to objects you are an administrator or developer of. Invalid Negative Connections: If you specify negative targeting, you must be the administrator or developer of the objects whose fans you want to specify to exclude. You are not an admin of the following specified connections: &#;connections&#; Could not save creative Invalid Image Hash: Invalid Image Hash - &#;hash&#; Permission Error: Either the object you are trying to access is not visible to you or the action you are trying to take is restricted to certain account types. Ad targeting does not match targeting of the story: The targeting specified for this ad is not compatible with the story being boosted. Check the privacy and language/country targeting of the story you are trying to ads error codes Invalid object - not admin or object not public: The user is not an admin of the object or the object is not publicly accessible. Ads error codes URL For Creative Destination: Creative must have a valid destination URL, and if attached object is page, destination must match page. Ad Creation Limited By Daily Spend: The number of ads you can create in a given period ads error codes time has a limit determined by your daily spend level. Higher spend levels allow creation of more ads. Increase your daily spend limit or create fewer ads per time period. Campaign Update Failed: Campaign &#;campaign_id&#;: &#;reason&#; Campaign Creation Failed: &#;reason&#; Targeting declined due to policy: Invalid ads targeting, ads error codes. The targeting spec was declined due to policy restrictions. Not Allowed To Use View Tags: Only some partners are allowed to use view tags, ads error codes. Please verify that you are using an approved account. Custom Audience Unavailable: The custom audience you&#;re trying to use hasn&#;t been shared with your ad account. Please create or choose a different custom audience, or ask the owner of the custom audience to let achmed the dead terrorist mp3 use it. The post does not belong to the specified Page: Post to be promoted does not belong to the Page specified. The post belongs to &#;otherDestination&#;; try using this as the destination or using a post that belongs to the specified Page. Specified Page: &#;destination&#. Custom Audience Has Been Deleted: Cannot use deleted custom audience. Please choose another audience. Conversion Spec Needed: For ads pointing to an offsite location with a non-zero bid on actions, you must specify the conversion spec. Invalid aggregation day for conversion data. The aggregation day must be larger than or equal to 1. Adcreative Create Failed: The Adcreative Create Failed for the following reason: &#;reason&#; Ads error codes Use Syndicated Audiences From Multiple Partners: When specifying partner-created custom audiences for an ad, all audiences must be from the same provider. Failed to update the creative: Failed to update creative &#;id&#. Failed for the following reason: &#;reason&#; Ad Needs Exclusion Targeting: This ad cannot be created with the targeting spec you selected. Your ad has a conversion objective that users can only do once, so you must target the ad at those users who have not already converted. If you are using the Facebook API, ads error codes, consider including the following string in your targeting spec: &#;exclusion-targeting-spec&#. Invalid CPA Bid: The action type you selected is not allowed for Cost-Per-Action (CPA) bidding: &#;&#;action_type&#;&#. Please change your optimization goal or switch your bid type to regular Optimized CPM. This type of page post is not eligible to be promoted. &#;debug_info&#; Conversion Tracking Pixel Permission Error: The conversion tracking pixel you&#;re trying to use is owned by another user and hasn&#;t been shared with you. Please use a tracking pixel that&#;s been shared with you or create a new one. Too many async requests The new budget value is too low: The new budget value of &#;new_budget&#; is too low. The minimum acceptable is &#;minimum_budget&#. No supported fields were provided for updating the campaign No supported fields were provided for updating the ad Ad Update Failed &#;reason&#; You must specify an object_id for this adcreative type (creative type 27) There have been too many calls from this ad-account. Wait a bit and try again. You have overlapping locations specified in the geo_locations field. Your broader option will override the narrower option, please remove one to proceed. The promoted object is invalid: it could have been deleted or never existed. The given prediction id in a reach and frequency campaign is not reserved. The given reservation in a reach and frequency campaign is not finalized yet. The given reservation in a reach and frequency campaign is already finalized The prediction in a reach and frequency campaign is already reserved. This indicates the operation fails for an unknown reason. The given page types are not supported by the inventory manager. A finalized prediction order can not be cancelled. You can create a new prediction or delete the campaign. Conversion Spec Targets Invalid ID: You are targeting an ID in your conversion spec without admin permissions on that object. &#;debug_info&#; This Promotion Can&#;t Be Edited: This can&#;t ads error codes edited because you promoted it from your Page, ads error codes. Find the post on your Page to pause, delete, or update budget for this promotion. This Promotion Can&#;t Be Edited: This can&#;t be edited because you ads error codes it from your Page. Find the post on your Page to pause, delete, or update budget for this promotion.

Your bid strategy is invalid. Current available bid strategies are, and. Please choose a valid bid strategy to suit your business goals. Effective as of

You are trying to set a bid strategy on an ad set in an ad campaign with campaign budget optimization enabled. Setting bid strategy on such an ad set is not allowed. Either remove bid strategy on your ad set or disable campaign budget optimization on your campaign. Effective as of

You are trying to set a bid strategy on an ad set in an ad campaign that does not use Auction buying type, ads error codes. Setting bid strategy on such an ad set is not allowed. Effective as of

Bid amount required: you must provide a bid cap or target cost in bid_amount field. For you must provide bid_amount field to set a bid cap. Foryou must provide bid_amount field to set an average target cost goal. Effective as of

You can&#;t set a bid cap on ad sets with bid strategy. Please either remove bid_amount or change to use with bid_amount. Effective as of

Optimization Goal Isn&#;t Available: You can&#;t use the selected optimization goal for your campaign objective. Please select a different goal and edit your campaign.

We disallow creation of empty product sets for Ads error codes catalog ads. Please add products to your catalog and create a set that contains at least one product.

Unable to Create Campaign Using This Ad Account, ads error codes. To create Collaborative Ads campaigns, Brand Advertisers must use a separate ad account for each seller they partner with. Make sure you use a separate ad account associated with the seller who owns this catalog segment. Under limited availability.

Unable to Create Campaign Using This Catalog Segment. You cannot use this ad account to run ads for this catalog segment. The business created this catalog segment for a Brand Advertiser to use in Collaborative Ads. Choose a different ad account, or use this ad account to run campaigns using a product catalog instead. Under limited availability.

You can&#;t edit your pixel, conversion event, custom conversion or optimization for an ad set after the ad set is published. To run an ad set with your desired changes, create a new ad set.

Error Code

Error code

Instructions

Investigation hint

Please exec sprers.eu before load ad

Initialize the sdk and then initiate an ad request

load time out

The ad object is not successfully returned within the specified time, and it is not recommended to initiate the request again.

resource error

Resource loading failed due to network and other reasons.

No fill

BadRequest: Http request pb error

Indicates that some necessary parameters have invalid values. Please check the integration guideline on Pangle platform

lockmailbox failed error colspan="1">

BadRequest: Empty Slot ID

Indicates that the dnserrordiagoff_weboc htm ieframe dll is null

BadRequest: Invalid Ad Size

Indicates that the AdSize is missing or an unsupported size is passed.

Invalid Slot ID

Indicates that the length of the ads error codes is incorrect, or an empty string is passed.

BadRequest: Ad counts error

Indicates that the is invalid

BadRequest: Image size error

Indicates that the image size is not supported.

Invalid App ID

Indicates that the app id is invalid or app id is missing

BadRequest: Slot ID and App ID is not matched

Indicates that the relationship between App Id and Slot Id is invalid or App Id is missing.

Invalid Package Name

Indicates that the package name of your project does not match the package name you filled in Pangle platform.

BadRequest: Ad Type and Slot Id is not matched

Indicates that Ad Type and Slot Id is not matched. For ads error codes, try to load a rewarded ad with a banner ad slot id.

BadRequest: Invalid SHA1 value

Indicates that the SHA1 is not matched with the SHA1 you entered on the Pangle platform

BadRequest: Incorrect API method

Indicates that the API method is incorrect

BadRequest: The SDK version is too low

Please update to the latest SDK

BadRequest: verification failed

Update to the latest SDK

Unsupported regions

Indicates that your Pangle account only support China traffic. No ads returned when you try to load ads outside of china(non-china IP)

BadRequest: Incorrect API method

There are three situations: One: IOS: ad request method error, SDK rendering advertisement and self rendering ad request method are different. Solution: Use the SDK rendering method and the correct parameters to request SDK rendering ad. Two: The server slotID configuration is not effective: you need to wait minutes for the new slotID to request the ad. Three: Low SDK version: the SDK version used is too low (lower than ) and does not support personalized SDK rendering function. Solution: update to the latest version of the Platform SDK.

Incorrect Bidding Ad Placement

1, ads error codes. Bidding ad placement can not be used in non-bidding environment 2. Non-bidding ad placement can not be used in bidding environment.

Servers error

Server error, if the error could be % replicated, please give feedback to us via [email protected]

-1

Data parsing failed.

For the collection of client code problems, you can first check the following situations: One: show is called in the child thread. Two: ViewGroup is ads error codes when registering click events. Three: The business logic of the media in the onFeedLoaded callback is abnormal, ads error codes, which causes the SDK to go to the onError callback. If the above ideas still can not solve your problem, you can contact the TS

-2

Network error

Indicates that your network connection is not stable enough.

Prohibit requesting ads

Pangle don't have Children ads, you can not get fill when coppa = 1

Data parsing failed for template ads

Please update to the latest sdk.

Template missing

Please update to the latest sdk.

Subtemplate missing

Please update to the latest sdk.

SDK rendering timeout

Please update to the latest sdk.

SDK rendering timeout

Please update to the latest sdk.

Template loads failed

Please update to the latest sdk.

Dynamic-Native JS parsing error

Re-request ads

Dynamic-Native JS parsing timeout

Re-request ads

Dynamic-Native rendering error

Re-request ads

Dynamic-Native SDK parsing error

Re-request ads

Dynamic-Native SDK parsing timeout

Re-request ads

Dynamic-Native SDK rendering error

Re-request ads

Link establishment failed

Check network status and request ads again

Link establishment timeout

Check network status and request ads again

Ads returned abnormally

Re-request ads

Ads parsing failed

Re-request ads

Ads parsing failed

Re-request ads

Ads parsing abnormally

Re-request ads

Ads read and write failed

Re-request ads

Ads read and write failed

Re-request ads

Ads download failed

Re-request ads

Ads download abnormally

Re-request ads

Ads request cancelled

Re-request ads

Image load abnormally

Re-request ads

Admob Ads Error Codes &#; App Advertising

Error Code 0 : ERROR_CODE_INTERNAL_ERROR
This indicates that something happened internally; for instance, ads error codes, an invalid response was received from the ad server.

Newly created Ad Units can take upto 2 hours to become active (SpinUp Time), ads error codes. Any Ad requests from newly created Ad Units would also receive Error Code 0 in response to Ad requests until they are ready to serve live ads.

What to do? Test Ads!!

Error Code 1 : ERROR_CODE_INVALID_REQUEST
The ad request was invalid; for instance, the ad unit ID was incorrect.

This commonly suggests that the Ad Request implementation is not as per the SDK’s requirements &#; Resources like the sample codes and sample apps provided in the developer documentation can help in implementing the functions correctly.

Error Code 2 : ERROR_CODE_NETWORK_ERROR

The ad request was unsuccessful due to network connectivity.

This could be due to a user’s phone switching networks or network disturbances distorting the communication between the app and the Ad Server, ads error codes. Some Telecom providers may also limit specific traffic due to policy, which can also lead to such an error.

Error Code 3 : ERROR_CODE_NO_FILL
Description (Dev Docs Link) : The ad request was successful, but no ad was returned due to lack of ad inventory.

Why is it Happening : Advertisers can target specific regions, platforms and user profiles based on business relevance, which can sometimes result in lower availability of Ads for a particular region or user profile. Error code suggests that the implementation is correct, and that the Ad Request was not filled because of lack of availability of a suitable Ad at that particular instant of time when an Ad Request was sent from the app.

Policy related restrictions on certain Apps or Ad Units will also lead to Error Code 3 being returned in response to Ad Requests.

What Can The Pub Do About it :

→ As we cannot manipulate advertiser demand, ads error codes, there are no particular ‘fixes’ for this error &#; the pub can cross-check the Ad Unit implementation to ensure that the Ad Units are implemented correctly.

→ Mediation : In some instances, ads error codes, certain Ad Networks may have limited performance in some regions or for specific formats, ads error codes, in which case the pubs can try using mediation to add other Ad Networks that may potentially perform well.

→ Check for Policy status for the Pub ID, ads error codes, the App and the Ad Unit ID, ads error codes. Also check the Brand Safety flags and Coppa status.

→ If the Pub can obtain Test Ads for an Ad Unit (Instructions) ads error codes then their implementation is correct, and the Ad Units will serve Ads normally when an Ad is available depending on advertiser demand.

Error Codes 8 : ERROR_CODE_APP_ID_MISSING
The ad request was not made due to a missing app ID.

Error Codes 9 : ERROR_CODE_MEDIATION_NO_FILL
The mediation ads error codes did not fill the ad request. If this error is returned from sprers.eue(), check sprers.euse() for the underlying cause.

Error Codes 10 : ERROR_CODE_REQUEST_ID_MISMATCH
The AdInfo object inside the ad request has mismatching request IDs.

A Complete List of Video Advertising Error Codes

/ YesGeneral linear errorThis can be caused when a video player is unable to display the linear ad. It may occur when the MediaFile is not a valid video file of the specified format, or because the browser restricted autoplay with sound, or another unknown reasonPublisher – Check for player issues, enable your player to detect for restricted autoplay, or alert the buyer
Buyer – Ensure that the VAST response returns a valid creativeYesMediaFile not foundThis can be caused when a file cannot be found from a MediaFile URIPublisher – Ensure that all MediaFiles in the response return a valid video asset. If not, alert the buyer
Buyer -Ensure that the VAST response returns a valid creative / NoTimeout of MediaFile URIThis can be caused by a problem fetching or playing the MediaFile, and could be any of the following:
  • The loadVideoTimeout is set too low in the IMA SDK. (the default is 8 seconds)
  • Low bandwidth or poor website implementation with competing requests that delay loading of the MediaFile
  • A video auto-plays in a mobile environment, whereas it should be click-to-play (there are some exceptions)
  • Showing video ads in an auto-play environment (for example, a playlist), while the window is not in focus (either another tab is selected, or window is minimized) (Chrome only)
Publisher – Increase the timeout limit of your player
Buyer – Ensure that any CDN-hosted creatives are returned within the specified media timeoutYesCould not find MediaFile that is supported by this video player, based on the attributes of the MediaFile elementThis can be caused by a VAST response that declares unsupported MIME types for all available MediaFiles. For example:
  • Bidder did not respect mime types in bid request
  • Exchange did not send correct mime types
  • May indicate that the wrong creative type attempted to play such as a Flash creative attempted to play on a mobile device or WebM on iOS
Publisher – Ensure that the creative format or technology requested is supported by the video player’s device and platform. For example, VPAID creatives should not be requested from mobile apps
Buyer – Ensure that all returned creatives respect the video format in the bid requestYesProblem displaying MediaFileThis can be caused when a faulty creative is returned due to a mismatch between the MIME type and the video file type, ads error codes, a CORS configuration on the creative’s CDN, ads error codes, transcoding-related reason such as an unsupported codec, or unsupported delivery methodPublisher – Alert the buyer
Buyer – Ensure that all creative MIME types and CDN configurations are accurateNoMissing required mezzanine fileThis can be caused a VAST ads error codes is returned without a required mezzanine file. Publishers with server-side ad implementations (SSAI) often require mezzanine files, ads error codes, which are raw high-quality video files for ad-stitching, or to generate video files of appropriate quality (VAST 4)Publisher – Alert the buyer
Buyer – Ensure that a mezzanine file is included in your response when required by the publisherYesMezzanine file downloaded for the first timeThis can be caused when the mezzanine file is downloaded for the first time, so no ad is served. It can also occur when an ad insertion is missed because the creative is being transcoded. It continues to occur until the creative is available for insertion (VAST 4)No action requiredYesAd rejected in VAST responseThis can be caused when the ad returned in the VAST response is rejectedPublisher – Alert the buyer
Buyer – Ensure that only approved creatives are returned in your VAST ads error codes, or that any advertisers or agencies hosting the creatives are aware of rejectionsYesInteractive unit in the InteractiveCreativeFile node was not executedThis can be caused when a creative defined in the InteractiveCreativeFile node does not executePublisher – Alert the buyer
Buyer – Ensure that any interactive creatives returned in your response successfully play when requestedYesVerification unit in the Verification node was not executedThis can be caused when the code referenced in the AdVerification node does not execute ads error codes 4)Publisher – Alert the buyer
Buyer – Ensure that the verification code referenced in the response is correctly implemented ads error codes to the verification vendor

ironSource SDK Error Codes

Error CodesAd UnitDescriptionN/A• Init failure of the mediation/Network
• Calling a Demand Only API in non Demand Only mode
• Calling a non Demand Only API in Demand Only mode InterstitialShow Fail: No ads to showRewarded VideoOfferwallInterstitialLoad Fail: Server response failed
Load Fail: Adapters loading failureInterstitialShow Fail: No internet connection; 
ShouldTrackNetworkState is enabledRewarded VideoShow Fail: No internet connectionOfferwallInterstitialShow Fail: Placement %@ has reached its limit as defined per pace
Show Fail: Placement %@ has reached its capping limitRewarded VideoOfferwallInterstitialShow Fail: Ad unit has reached its daily cap per sessionRewarded VideoRewarded VideoShow Fail: Cannot show an RV while another RV is showingRewarded VideoShow Fail: Show RV called when there are no available ads to showInterstitialShow Fail: Cannot show an interstitial while another interstitial is showingInterstitialLoad Fail: Cannot load an interstitial while another interstitial is showing

 

ads error codes

0 Comments

Leave a Comment