Stay organized with collections
Save and categorize content based on your preferences.
When integrating a bidding partner that requires their SDK, the following
symptoms indicate an improper integration:
The
Ad Manager report
shows significantly fewer ad requests to that partner than you expect.
The a3p parameter in any request after the first ad request is missing.
Follow this checklist to make sure your setup is correct:
In the Ad Manager UI:
Confirm that you have followed the specific partner's
integration guide
to configure third-party bidding demand.
Confirm that you have an ad unit mapping for each creative format.
For example, if you're setting up both native and banner, you need an ad
unit mapping for native and another for banner.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-11-21 UTC."],[[["Low ad requests in Ad Manager reports and a missing `a3p` parameter after the first request signal improper SDK integration for bidding partners."],["Ensure proper Ad Manager configuration by following the partner's integration guide and setting up ad unit mappings for all creative formats."],["Verify your app code by updating the `Info.plist` file, matching ad unit IDs, initializing the Mobile Ads SDK, and using the latest adapter and SDK versions."]]],[]]
