Use * syntax for faster search
Page History
...
| Multiexcerpt | ||
|---|---|---|
| ||
Bid Decision Flow is a diagnostic tool designed to help troubleshoot line item performance. It visualizes auction data and shows how the bidding system responded to auctions within a specified lookback window, helping users identify why a line item may not be bidding. |
...
- Targeting: Identifies if the targeting key caused a non-match for the auction.
- Solution: Expand targeting by adjusting segments, geo values, or inventory lists.
- Solution: Expand targeting by adjusting segments, geo values, or inventory lists.
- Creative Match: Captures whether the creative properties led to a non-match.
- Solution: Review creative setup, including attributes like MIME types, video bit rate, and size, and ensure they align with the targeted inventory.
- Solution: Review creative setup, including attributes like MIME types, video bit rate, and size, and ensure they align with the targeted inventory.
- Frequency Cap: Checks if the line item exceeded the frequency cap.
- Solution: Loosen frequency cap restrictions or add additional frequency cap ID types.
- Solution: Loosen frequency cap restrictions or add additional frequency cap ID types.
- Pacing: Verifies if the pacing algorithm held back bidding.
- Solution: If pacing is active, check if the line item is pacing too aggressively or not enough.
- Solution: If pacing is active, check if the line item is pacing too aggressively or not enough.
- Bidding Agent: Indicates if the bidding agent chose not to bid based on strategy.
- Solution: Adjust target values in optimized bidding strategies (e.g., CPC Goal, Video Completion Rate) or switch to a different strategy.
- Solution: Adjust target values in optimized bidding strategies (e.g., CPC Goal, Video Completion Rate) or switch to a different strategy.
- Budget: Determines if the line item had sufficient budget.
- Solution: Adjust daily or lifetime budget, and verify if the budget cap has been reached.
- Solution: Adjust daily or lifetime budget, and verify if the budget cap has been reached.
- Post-Processing: Identifies if the bid was dropped due to final processing issues (e.g., bid price lower than the floor price).
- Solution: Raise the CPM bid or ensure the bid exceeds the deal floor for targeted deals.
Reasons Bid Requests are Dropped
Opt-Out
Users may choose opt-out from being served ads by Beeswax, by clicking a link on the Beeswax Privacy Policy page.
If the user ID on a particular bid request is flagged as “opted out”, the bid request will be dropped.
Limit Ad Tracking
“Limit Ad Tracking” (LMT) is a device-level opt-out setting, that allows users to limit the amount of information sent from their device to ad exchanges (including omitting their device ID).
Bid requests flagged as LMT are eligible to bid on if they originate from iOS or tvOS operating systems. We drop all other bid requests flagged as LMT from other operating systems.
...
Situations Where Bid Requests Are Not Dropped
Do Not Track
The “Do Not Track” (DNT) setting is not honored. Requests marked as "DNT" are not dropped or altered in any way.
Drop-Reasons
Drop-reasons are available for certain stages and provide more granular insights into why a bid was dropped. To view these reasons, click the ‘Show Details’ button for Targeting Match and Post-Processing stages.
...