Table of Contents
Overview
This page outlines the steps to take when a line item is not delivering as expected.
Troubleshooting Steps
If line item or campaign spend is not appearing in a report, follow these steps:
Check Real-Time Win Stats: In the Edit Line Item screen, review the real-time win stats to determine if the line item is actively winning. If it is, other reports will populate based on the timeframes indicated in the Object Population Timelines article. If bidding is occurring but no wins are recorded, the CPM may be too low to win against competition. Alternatively, if targeting a specific exchange or deal ID, the creative may be filtered by the exchange. In such cases, the exchange should be contacted for further details, and Beeswax Support can assist.
Check Account and Object Status: Ensure that the Campaign, Line Item, and Advertiser are all active.
Verify Dates: Confirm that the Start and End Dates for the campaign, line item, flight, creative, and creative-line-item association fall within the designated flight window.
Check Secure Attribute: Verify that the Secure attribute on the creative is properly set. Most inventory only supports secure creatives, and if the creative is marked as insecure, it may not match any traffic.
Check Continent Selection: If all continents are enabled for the account, ensure the correct continent is selected for the campaign in the "Continents" field in the Edit Campaign screen.
Check Performance Report: Use the Query Tool to pull a report with "Hour" as a field to verify that no spend is occurring. The campaign and line item screens may have a longer delay than the Query Tool, which typically has a one-hour delay before initial impressions appear.
Check PMP Deal ID:
- Ensure the bid is above the bid floor.
- Confirm that the deal ID is included in the targeting screen. If it's missing, the ad markup will not include the deal ID, and the bid will be blocked.
- Verify that the deal ID is being processed in the Metamarkets instance.
Check Lifetime Budget: Ensure that the lifetime budget has not been fully spent for the campaign or line item. This can be verified in both the Line Item and Campaign screens in the UI, as well as in the Performance Report in the Query Tool.
Check for Competing Line Items: If there are multiple line items within a campaign using the same targeting and creative sizes with Flat CPM bidding, the line item with the higher CPM will win unless it runs out of budget. In this case, pacing is recommended to allow the line item with the lower CPM to win more frequently. If Flat CPM is essential, frequency caps can be used to ensure the other line item wins.
Check Pacing: If the line item uses pacing, but other line items do not, the non-paced line items may consume the available budget and prevent the paced line item from serving.
Check List Targeting: If targeting a list, confirm that the list contains items. If the list is empty, the line item will not serve.
Review Targeting and Creative Properties: In the Metamarkets instance, set up a report to replicate the targeting parameters, creative size, and placement type, and check if matching bid requests are coming into the bidder. If no matching traffic is found, consult with the Beeswax account manager to ensure that no traffic is being missed. If traffic is being received, ensure that there is no confusion between Deal ID, Site ID, App ID, App Bundle, or Domain.
Check for Thumbnail (Pubmatic/MoPub): For delivery issues on Pubmatic or MoPub, ensure that a thumbnail has been added to the creative.
Check Segment Activity: If targeting a segment, confirm that the segments contain active users. This can be verified in the Segments screen.
Verify Augmentor/Bidding Agent: If using an augmentor or bidding agent, ensure that it is responding with status code 200 to Beeswax. This can be checked under Tools (beta) and Monitoring.
Check IAS Segment Targeting: When targeting IAS segments, ensure that only segments for one environment type are selected (e.g., in-app or web). If targeting both web and in-app IAS segments, the line item may not deliver properly. Additionally, ensure that the IAS segment's environment type matches the targeted environment type (e.g., in-app IAS segments for an in-app environment).
Check Advanced Segment Targeting: For line items using Advanced Segment Targeting with boolean logic, conflicting logic or empty segments can cause delivery issues. If the line item contains a large number of segments (7+), troubleshooting can be challenging due to the numerous interactions. It is recommended to temporarily remove the segment targeting, reduce the daily budget to a small amount (e.g., $1-$2), and check if the line item begins to spend. After a few minutes, reapply the segment targeting and return the daily budget to its original amount.
Contact Beeswax Support: If all the above steps do not resolve the issue, contact Beeswax Support for further assistance.