Table of Contents
Overview
The Bid Decision Report creates the capability to analyze bidding behavior across all active campaigns and line items. This diagnostic report is an expansion of the Bid Decision Flow visualization, and gives access to more levels of granularity and flexibility in analyzing bidding behavior. The Bid Decision Report is aggregated on account, campaign, and line item levels, and has a lookback range of the last 7 days. Bid decisioning data is additionally aggregated at two levels; drop stage and drop reason. Drop stages are the thematically grouped sets of drop reasons, which in turn are the individual eligibility evaluations made by Beeswax in the bidding process. To learn more about what drop stages and reasons are, see Drop Stages with Reasons.
Reporting Fields
Both of the measures included in this report are based on sampled data and are highly directional.
Field Name | Field Type | Definition |
---|---|---|
Account ID | Dimension | Beeswax Account ID |
Campaign ID | Dimension | Beeswax Campaign ID |
Line Item ID | Dimension | Beeswax Line Item ID |
Drop Stage | Dimension | Thematically grouped sets of bid eligibility evaluations (drop reasons). |
Drop Reason | Dimension | Individual evaluations of eligibility to bid on a given request. |
Drop Order | Dimension | The order in which the evaluations occurred; used for ordering only. |
Auctions | Measure | The approximate count of bid requests eligible at a given stage/reason. |
Auctions Dropped | Measure | The approximate count of bid requests dropped in a given stage/reason. |
Drop Stages with Reasons
Drop stages are represented in the report to identify where there was a mismatch in the ad decisioning. For example, a drop stage may represent a mismatch in GEO, and will represent that with a "TARGETING_GEO_MISMATCH" drop stage reason. A numerical value will also display the number of bids associated with that drop stage reason, I.e. during the GEO drop stage, 50,000 bids were dropped due to the targeting mismatch.
Drop stage will represent when the mismatch occurs, but the drop reason will explain why the bid was dropped. These reasons are outlined in the Description column of this table.
Bid Decision Report Drop Stage | Description |
---|---|
TARGETING_USER_MISMATCH | Bid request mismatches line item targeting on a field in the user module. Likely targeting acting as intended. |
TARGETING_ENVIRONMENT_MISMATCH | Bid request mismatches line item targeting on a field in the environment module. Likely targeting acting as intended. |
TARGETING_PLATFORM_MISMATCH | Bid request mismatches line item targeting on a field in the platform module. Likely targeting acting as intended. |
TARGETING_EXCHANGE_MISMATCH | Bid request mismatches line item targeting on a field in the exchange module. Likely targeting acting as intended. |
TARGETING_GEO_MISMATCH | Bid request mismatches line item targeting on a field in the geo module. Likely targeting acting as intended. |
TARGETING_APP_SITE_MISMATCH | Bid request mismatches line item targeting on a field in the app/site module. Likely targeting acting as intended. |
TARGETING_CONTENT_MISMATCH | Bid request mismatches line item targeting on a field in the module. Likely targeting acting as intended. |
TARGETING_RANGE_TARGETING_MISMATCH | Bid request mismatches line item targeting on IP ranges. Likely targeting acting as intended. |
TARGETING_VIDEO_MISMATCH | Bid request mismatches line item targeting on a field in the video module. Likely targeting acting as intended. |
PG_DEAL_FILTERED | Bid request is for a Programmatic Guaranteed deal that the line item is not permitted to buy. Likely targeting acting as intended. |
TARGETING_TIME_MISMATCH | Bid request mismatches line item targeting on a field in the time module. Likely targeting acting as intended. |
PROCESSING_ERROR | Processing error. |
CREATIVE_MISMATCH | Bid request mismatches a line item's creative. Likely creative matching acting as intended. |
ID_NOT_AVAILABLE | The ID type selected for frequency capping is not available on the request. Likely frequency capping working as intended. |
FREQ_CAPPED | Frequency capping acting as intended. |
PROCESSING_ERROR | Processing error. |
PROCESSING_ERROR | Processing error. |
NO_AGENT_BID | Bidding agent did not respond. |
EXCEED_MAX_BID_PRICE | Bid price is very large and likely a mistake. |
ZERO_BID_PRICE | Bidding agent responded with a zero bid price. |
WRONG_BID_CURRENCY | Bidding agent's returned bid currency mismatches the line item's currency. |
PROCESSING_ERROR | Processing error. |
TRANSIENT_BUDGETING_ERROR | Beeswax was unable to determine if budget was available. Rare occurrences with low frequencies are expected. |
BUDGET_NOT_BIDDABLE | Bid price exceeds available budget. Likely budget system acting as intended. |
BUDGET_CAP_MET | Typically occurs when a line item or campaign is out of budget (any/all relevant budget levels). |
FLOOR_PRICE_FILTERED | Bid price is lower than the relevant bid floor passed from the exchange. |
FIX_PRICE_FILTERED | Bid price is lower than the bid floor in a fixed price deal. |
EXCHANGE_SEAT_ERROR | Error with Seat set up or Seat eligibility. |
DROPPED_GHOST_BID | Expected, ghost bid candidates will not submit an actual bid back to the exchange |
BID_TOO_LOW | Bid price is too low to be selected to be returned by Beeswax to the exchange. |
PROCESSING_ERROR | Processing error. |
OK | Bid is submitted. |
Interpreting Report Data
The lookback window for the Bid Decision Report data is 7 days. For a longer lookback window, use the report builder's scheduling capability to be sent a copy of the report.
When pulling a Bid Decision Report for a line item, there is a logical hierarchy that represents how requests are received, and then dropped. For instance, the report will display the amount of auction requests a line item has, then it will display the mismatch reasons for dropping in a hierarchical order. The mismatch data hierarchy is as follows:
- Targeting
- Relevant Creatives
- Frequency cap parameters
- Pacing parameters
- Bidding agent parameters
- Budget parameters
- Relevant post-processing criteria