--- title: "Report Builder Reports" canonical: "https://hub.freewheel.tv/space/BC/114622863/Report%20Builder%20Reports" format: markdown --- --- # > Macro (anchor) Inventory Report > ℹ️ Lookback Range: 6 months The Inventory Report shows granular inventory details of campaign or line items and where they were served (i.e., where they were bid and won an impression). --- # > Macro (anchor) Bid Performance Report > ℹ️ Lookback Range: 6 months The Bid Performance Report allows users to see information about their bids and win rates, broken down using similar dimensions to the Performance Report. It allows customers to answer questions like: - What is the win rate for this Line Item, Campaign, or Advertiser? - How often am I bidding? - How did increasing or decreasing the bid price affect win rates? The Bid Performance Report includes the following measures: - Total Bids - Average Bid Price (in CPM) - Total Impressions - Win Rate (impressions/bids) Only bids submitted to the exchanges will be counted in the Bid Performance Report. These measures can be aggregated across most dimensions in other reports, such as the advertiser, campaign, line item, and creative levels. --- # > Macro (anchor) Billing Report > ℹ️ The Billing Report is only available for customers with standard Buyer Cloud configurations. The Billing Report is populated with all variable fees that a Buyer Cloud customer can be charged for. This information is broken out by Date, Account, Advertiser, Campaign, and Line Item, and is shown in Eastern Time Zone. The Billing Report fees align with the invoice when pulled for a complete month. The Billing Report has an 'Invoice Row' dimension that contains the following fees: - Media paid to the inventory source - DSP Fee - Professional Services Fee - Bid Shading Fee - Third-party data Fee (Broken out by vendor) - Small File Serving Fee - Large File Serving Fee - Cross Device Extension Fee (Broken out by vendor) - Cross Device Frequency Capping Fee (Broken out by vendor) The Billing Report will not include any recurring flat fees or any other additional service fees outside of the fees listed above. This report also does not include details on any minimum spend thresholds that are applied to an invoice. If a minimum spend threshold is not reached, then the 'DSP Fee' and 'Professional Services Fee' rows will still show the calculated % of media, not the minimum threshold shown on the invoice. This report will only be visible to 'Admin' roles by default. Admin users can [grant permissions](https://freewheel-knowledge-hub.atlassian.net/wiki/spaces/BC/pages/114786489) to this report to other roles. Multi-account Buyer Cloud clients can pull the Billing Report across all their accounts for a consolidated view by using Account Groups to manage access to all their accounts. --- # > Macro (anchor) Pacing Report The Pacing Report provides insight into the performance of campaigns, line items, or flights relative to their set budgets over a specified time period. This tool enables users to monitor whether line items are under-pacing, over-pacing, or on track to meet their budget goals, ensuring campaign deliverables are fulfilled according to the intended timeline. Access to the Pacing Report is granted based on user roles. ## Report Aggregation Details The Pacing Report provides aggregated data at three levels: campaign, line item, and line item flight for each Buzz Key account. Unlike time-series reports, the Pacing Report does not offer historical data such as "Pacing Data for the last 30 days." Instead, it presents a snapshot of the current state of campaigns, similar to line item quick stats. For comparison purposes, you can access both Today's On-Schedule Indicator (OSI) and Yesterday's OSI within the report. ## Pacing Report and On Schedule Indicator Metrics When using the campaign, flight, and line item OSI measures within the report, the following metrics are available and displayed in a color-coded manner to represent the health of the pacing. - OSI = 1 – Line item is 100% on pace as per its budget goal for the current time. - OSI < 1 – Line item is under-pacing compared to where it should be at this point in its pacing lifetime. For example, an OSI of 0.8 indicates that  the line item is 20% behind pace and only 80% of where it should be at this point in its pacing lifetime. - OSI > 1 – An OSI can exceed 1 and indicates that a line item is over-pacing compared to where it should be in its pacing lifetime. For example, an OSI of 1.5 indicates that the line item is 50% ahead of pace and has spent 50% more than it should have at this point in its pacing lifetime. The color codes indicate the health of pacing: [Green] – The OSI is >0.95 and <1.05 [Yellow] – The OSI is 0.90-0.95 or 1.05-1.10 [Red] – The OSI is <0.90 or >1.10 **Notes**:  - Pacing Report supports calculating OSI for Lifetime and Flight pacing. Currently, it does not support daily pacing. - Pacing Report calculates OSI in the native time zone of a given line item. This is relevant when you are setting queries across multiple accounts. - When pulling in Flight ID, clients may see a row with Flight ID = 0. This is an invalid Flight ID and instead signifies Programmatic Guaranteed impressions. In this scenario, if clients also pull in the Flight Impressions measure, the report will calculate PG impressions across the entire buzzkey, despite any line item or account-level filtering. Therefore, in this case, we suggest ignoring this measure. Pacing Data in Other Interfaces - Quickstats – You can see the On-Schedule Indicator (OSI) for a given line on the Line Item level. It shows only if the Line uses Lifetime Pacing. - Line Items API Endpoint – An OSI value is available in the API for `/line_item?view_name=line_item_stats`.