Various issues can prevent SDK bid requests from being matched.
For each SDK bidder, you can check for existing issues and review their impact under "Bid health." From there, you can use features such as Delivery Tools and Ad inspector, and review relevant Help Center articles to investigate further and find solutions.
The SDK Bid health data covers impacted bid requests over the last 7 days for all yield groups.
Review SDK bid health
- Sign in to Google Ad Manager.
- Click Delivery, then Bidders, and then Go to SDK bidding.
-
Click a bidder's name, and then Bid health.
- Under "Pretargeting matches with issues," review the table columns:
- Issue type: Shows the type of issue (Configuration, Regulatory, or Targeting mismatch) along with a brief description. Learn how to troubleshoot each issue type.
- App impacted: Shows the app impacted by the issue. Includes claimed and unclaimed apps.
- Issue details: Shows the specific configuration or regulatory details of the issue.
- Pretargeting matches (last 7 days): Shows the number of pretargeting matches for the last 7 days.
Troubleshoot SDK bid health
Review an issue type for more details and suggested troubleshooting.
Configuration
Issue | How to fix |
---|---|
SDK not found: Requests were filtered due to the SDK not being found or initialized. | Review your app using either Delivery Tools or Ad inspector. For more troubleshooting, visit Verify your SDK Bidding setup. |
Ad unit mapping missing: Requests were filtered due to missing ad unit mappings. | For each SDK Bidder configured to your inventory, be sure to add ad unit mapping. You can validate this using the Ad Inspector. |
Secure signals not shared: Requests were filtered due to secure signals not being shared. |
Ensure the following 3 steps are complete: You can also troubleshoot secure signal delivery. |
Regulatory
Issue | How to fix |
---|---|
Regulatory issue (GDPR): Indicates a bid request was blocked for non-compliance with GDPR policy. | Review Tools to help publishers comply with GDPR and make any needed changes to ensure compliance. |
Regulatory issue (CCPA): Indicates a bid request was blocked for non-compliance with CCPA policy. | Review the Integration with IAB CCPA Framework Technical Specifications and make any needed changes to ensure compliance. |
Targeting mismatch
Issue | How to fix |
---|---|
Targeting mismatch: Indicates there wasn't overlap between a bidder's pretargeting and the publisher's targeting. | Confirm certain protections aren't restricting access to your inventory. |