Pontiac Wiki Pontiac Wiki

Custom Reporting

Custom Reporting

  • Overview
  • Scheduled Reports
  • Custom Report
  • IP Conversion Pixel: Path To Conversion
  • IP Conversion Pixel: Page Visits
  • IP Conversion Pixel: Conversion Rate
  • Log Level Reporting
  • Reach/Frequency Report
  1. Home
  2. Bidder Documentation
  3. Reporting
  4. Custom Reporting

Overview

Custom reporting allows you to select and customize all dimensions and metrics you wish to evaluate, providing an exportable CSV with Campaign data. You can choose Advertisers, Campaigns, Line Items, Dimensions, Metrics, and a Date Range to generate a report. All reports are created in UTC time zone.

Custom Report Types

  • Custom Report
  • IP Conversion Pixel: Path to Conversion
  • IP Conversion Pixel: Page Visits
  • IP Conversion Pixel: Conversion Rate
  • Log Level Reporting
  • Reach/Frequency Report

Report Availability

  • Reports remain downloadable in the platform for 30 days.
  • After expiration, reports must be rerun. Note that some data points may no longer be available.

Report Limitations

  • Maximum Rows: Custom Reports are limited to 10,000,000 rows, depending on the delivery method and report type selected.
  • Incomplete Data Warning: If a report exceeds this limit, a yellow caution symbol will appear next to the report name, indicating that the data is incomplete.
    • If you require additional data beyond this limit, you can:
      • Split the report into multiple smaller reports.
      • Reduce the number of selected dimensions to decrease row count.
      • Contact your Account Manager for assistance.

Custom Reporting Time Zone

The time zone for custom reports can be configured on each individual report. Note, metrics will only match billing if the report is pulled in UTC. Custom reports may not match the metrics shown in the platform if they are not pulled in the seat time zone.

User time zone will use the ‘user time zone offset’ from the bid request to adjust report metrics for each impression to the time zone where that impression was served. When the user’s time zone offset is not present in the bid request, it will be defaulted to UTC.

Seat Time Zone

The time zone for your account can be configured under the ‘Admin’ section of the platform in ‘Seat Settings’ under ‘Preferences’. This time zone setting will adjust the metrics in the advertiser tab (advertisers, campaign and line item metrics) as well as the reporting dashboard. Note: this does not apply to billing metrics in the account balance or the pacing and dayparts on campaigns or lines. All billing metrics and transactions are for account activity in UTC. Pacing and dayparting time zones can be configured on each campaign or line.

Note that all platform activity appears in the account balance and is billed in UTC time zone.

Scheduled Reports

Custom reports can be automatically delivered to your email, FTP or S3 bucket, or Google Cloud Storage on the schedule of your choice. When creating a custom report, select the ‘Schedule Automated Report’ box, then open the ‘Scheduled Reports’ tab to choose the schedule and configure the delivery method.

When creating a new Custom Report and selecting Schedule Automated Report, the Scheduled Reports tab becomes editable. Complete the setup by selecting the following:

  • Report Frequency:
    • Daily: Reports will be sent each morning for the previous day.
    • Weekly: Reports will be delivered on Monday mornings for the previous week.
    • Monthly: Reports will be delivered on the first of each month for the previous month.
    • Custom:
      • Set a specific day frequency. For example, every 2 days.
      • Set a specific week frequency on a specific day. For example, every 2 weeks on Monday.
  • Reporting Interval: Yesterday, Last 7 days, Last 30 days, Month to Date, Previous Month, Custom
    • Custom: Last __ Days
  • Deliver by: Choose delivery method by selecting the checkbox for each.
    • Email
      • Email addresses should be separated by comma.
    • FTP
      • FTP Server
      • FTP Path
      • FTP Port
      • FTP Username
        FTP Password
    • AWS S3
      • Bucket: This is the name of the bucket, e.g. example.bucket. Bucket name does not contain a leading backslash or the s3:// prefix.
        • Creating a bucket in AWS S3:
          • In AWS S3 click Create Bucket
          • Chose a bucket name that is available and the desired AWS Region.
          • Change Object Ownership to ACLs enabled.
          • Uncheck Block all public access field and check “I acknowledge that the current settings might result in this bucket and the objects within becoming public”.
          • Click Create bucket.
          • Navigate to the newly created bucket and click Create folder with the output path that we chose in Pontiac (“output-path”). Confirm to create the folder.
        • Setting up the report in Pontiac:
          • Go to Reporting tab and then click New Custom Report.
          • Select Log Level Report from the Report Type Drop Down
          • Go to Scheduled Reports tab and check Deliver by S3 box.
          • In the expandable section fill out the Bucket field with the AWS S3 Bucket name. Example: S3-test-bucket.
          • Fill out the Path field with a desired output path location and file name (To include the date macro use dateInt (YYYYMMDD) like xxx/filename-%dateInt% otherwise your file will be overwritten each day). Example: output-path/Pontiac-reports.csv or output-path/Pontiac-reports-%dateInt%.csv
          • Click View security policy and copy the full text area.
          • Go to Amazon AWS S3 and modify permissions for the bucket we chose earlier. In the Permissions tab click Edit and paste the policy text from earlier and Save.
          • Back in Pontiac reports screen click Verify and wait for a successful confirmation message.
      • Path: This will be the full location that the report is saved to. To include the date macro use dateInt (YYYYMMDD) like xxx/filename-%dateInt% otherwise your file will be overwritten each day.
      • View Security Policy
      • Verify your configured bucket policy.
    • Google Cloud Storage
      • Bucket: This is the name of the bucket, e.g. example.bucket. Bucket name does not contain a leading backslash or the gs:// prefix.
      • Path: This will be the full location that the report is saved to. To include the date macro use dateInt (YYYYMMDD) like xxx/filename-%dateInt% otherwise your file will be overwritten each day.
      • Credentials: Valid json object.

Custom Report

Overview

Custom reporting allows you to customize all the dimensions and metrics you wish to evaluate, providing an exportable csv with all the data from your campaigns.

Create a Standard Custom Report:

  1. Navigate to the Reporting Tab and open the Custom Reporting dropdown section.
  2. Click ‘New Custom Report’.
  3. Select ‘Custom Report’ as the Type.
  4. Fill out the required report details.
  5. Click ‘Save’.
  6. Expand the Custom Reporting dropdown section and click the ‘Download’ button associated with the name of your custom report.
    • If Scheduled Automated Reports were selected, the report will be accessible via your chosen delivery method.

Below are the customizations available when creating the report:

  • Name: Enter a title for your report.
  • Schedule Automated Report: Choose this option to have the report sent to you on regular intervals. See the section for setup details Scheduled Reports
  • Advertiser ID: Select the Advertiser IDs that you would like to include in your report. By default, all Advertisers are included.
  • Campaign ID: Select the Campaign IDs that you would like to include in your report. By default, all Campaigns under the selected Advertisers are included.
  • Line ID: Select the Line IDs that you would like to include in your report. By default, all Lines under the selected Advertisers and Campaigns are included.
  • Start Date: Define the start date for the report interval.
  • End Date: Define the end date for the report interval.
  • Type: Choose the type of report. See each section for more details on report types.
    • Custom Report
    • IP Conversion Pixel: Path to Conversion
    • IP Conversion Pixel: Page Visits
    • IP Conversion Pixel: Conversion Rate
    • Log Level Report
    • Reach/Frequency Report.
  • Timezone: Select the timezone that the report will generate, such as Seat Time Zone, User Time Zone, UTC, etc.
  • Dimensions: Categorical values that define how data is grouped and segmented in reports, such as Campaign Name, Advertiser, and Exchange.
  • Metrics: Quantitative values that measure performance, such as impressions, clicks, conversions, spend, and CTR.

Dimensions:

  • Date
  • Advertiser ID
  • Advertiser Name
  • Advertiser Code
  • Campaign ID
  • Campaign Name
  • Campaign Code
  • Line ID
  • Line Name
  • Line Code
  • Creative ID
  • Creative Name
  • Creative Size
  • Region/State Code
  • Region/State Name
  • Country Code
  • Country Name
  • DMA Code
  • DMA Name
  • Zip Code
  • Browser
  • Operating System
  • Site Domain
  • Exchange
  • App Domain
  • App Bundle
  • App Name
  • Publisher Name
  • Device Type
  • Device Model
  • Deal ID
  • Deal Name
  • Content Genre
  • Content Episode
  • Content Title
  • Content Series
  • Content Channel
  • Content Network
  • Hour
  • Device Type Name
  • Inventory Type
  • Multi Field

Metrics:

  • Impressions
  • Media Cost
  • Total Cost
  • Revenue
  • Media Cost CPM
  • Total Cost CPM
  • Revenue CPM
  • Profit
  • Video Starts
  • 25% Video Complete
  • 50% Video Complete
  • 75% Video Complete
  • Video Completions
  • Video Clicks
  • Chrome Conversions
  • Data Costs
  • Art Fee
  • DCM Hosting Fee
  • CC Fee
  • Foot Traffic Fee
  • Contextual Fee
  • Chalice Fee

IP Conversion Pixel: Path To Conversion

Overview

The ‘Path to Conversion’ report provides data on IP conversions and impressions served to users who later converted. It shows the complete journey from an impression view to the conversion action on your website, helping you understand how impressions influence conversions over time.

Key Columns:

  • Impression Time: Indicates when the impression was served to a user who later visited or converted on the site where the pixel is placed. The total number of ‘imp_times’ shows how many impressions were served to users who then converted, corresponding to the ‘Attributed Imps’ field in the IP Conversion Pixel metrics under the Advertiser.
  • Conversion Time: Shows the time the conversion or action occurred. The total number of unique ‘conv_times’ represents the total number of conversions or visits driven by the campaign, corresponding to the ‘Total Convs’ field in the IP Conversion Pixel metrics under the Advertiser.

Lookback Window:

  • By default, the IP conversion pixels use a 30-day lookback window. However, if you need to pull data with a custom lookback window, you can select a value up to 30 days from the ‘Lookback Window’ dropdown.

Create an IP Conversion Pixel: Path to Conversion Report

  1. Navigate to the Reporting tab and open the Custom Reporting dropdown section.
  2. Click ‘New Custom Report’.
  3. Select ‘IP Conversion Pixel: Path to Conversion’ as the Type.
  4. Fill out the required report details.
  5. Click ‘Save’.
  6. Expand the Custom Reporting dropdown section and click the ‘Download’ button next to the name of your custom report.
    • If Scheduled Automated Reports were selected, the report will be delivered via your chosen delivery method.

Below are the customizations available when creating the report:

  • Name: Enter a title for your report.
  • Schedule Automated Report: Choose this option to have the report sent to you on regular intervals. See the section for setup details Scheduled Reports
  • Advertiser ID: Select the Advertiser IDs that you would like to include in your report. By default, all Advertisers are included.
  • Campaign ID: Select the Campaign IDs that you would like to include in your report. By default, all Campaigns under the selected Advertisers are included.
  • Line ID: Select the Line IDs that you would like to include in your report. By default, all Lines under the selected Advertisers and Campaigns are included.
  • Pixel ID: Select the Pixel IDs that you would like to include in your report. By default, all Pixels are included.
  • Start Date: Define the start date for the report interval.
  • End Date: Define the end date for the report interval.
  • Type: Choose the type of report. See each section for more details on report types.
    • Custom Report
    • IP Conversion Pixel: Path to Conversion
    • IP Conversion Pixel: Page Visits
    • IP Conversion Pixel: Conversion Rate
    • Log Level Report
    • Reach/Frequency Report.
  • Timezone: Select the timezone that the report will generate, such as Seat Time Zone, User Time Zone, UTC, etc.
  • Lookback window: By default, the IP conversion pixels use a 30-day lookback window.
  • Dimensions: Categorical values that define how data is grouped and segmented in reports, such as Campaign Name, Advertiser, and Impression Time.
  • Metrics: Quantitative values that measure performance, such as fractional attribution.

Dimensions:

  • Pixel ID
  • Pixel Name
  • Conversion Time
  • Impression Time
  • IP Address Truncated
  • IP Address Hashed
  • Home or Business
  • Zip Code
  • Site Domain
  • Exchange
  • Region/State Code
  • User ID
  • Advertiser ID
  • Advertiser Name
  • Line ID
  • Line Name
  • Device Type
  • Creative ID
  • Creative Name
  • App Domain
  • App Bundle
  • App Name
  • Order ID: Reporting on this field requires this value to be dynamically passed on the IP Pixel using the Order Value or Order ID parameters. Check the Order ID or Order Value boxes when creating the IP Pixel for further guidance.
  • Order Value: Reporting on this field requires this value to be dynamically passed on the IP Pixel using the Order Value or Order ID parameters. Check the Order ID or Order Value boxes when creating the IP Pixel for further guidance.
  • Deal Name
  • Publisher Name
  • Content Network
  • Content Channel
  • Content Series
  • Content Title
  • Content Genre
  • Custom Variable 1
  • Custom Variable 2
  • Custom Variable 3
  • Custom Variable 4
  • Other Parameters
  • Consumer ID
  • Campaign ID
  • Campaign Name
  • Conversion Date
  • Impression Date
  • Operating System
  • Browser
  • User Agent
  • Device Type Name
  • Inventory Type

Metrics:

  • Fractional Attribution: Assigns an evenly weighted conversion value to each impression event that leads to a conversion.

IP Conversion Pixel: Page Visits

Overview

The IP Conversion Pixel: Page Visits report pulls data on page visits associated with the IP Conversion Pixel. It only includes visit data at the advertiser level and is not tied to specific lines. Each record in this report represents a user visiting your page, independent of any media served.

Create an IP Conversion Pixel: Page Visits Report:

  1. Navigate to the Reporting Tab and open the Custom Reporting dropdown section.
  2. Click ‘New Custom Report’.
  3. Select ‘IP Conversion Pixel: Page Visits’ as the Type.
  4. Fill out the required report details.
  5. Click ‘Save’.
  6. Expand the Custom Reporting dropdown section and click the ‘Download’ button associated with the name of your custom report.
    • If Scheduled Automated Reports were selected, the report will be accessible via your chosen delivery method.

Below are the customizations available when creating the report:

  • Name: Enter a title for your report.
  • Schedule Automated Report: Choose this option to have the report sent to you on regular intervals. See the section for setup details Scheduled Reports
  • Advertiser ID: Select the Advertiser IDs that you would like to include in your report. By default, all Advertisers are included.
  • Pixel ID: Select the Pixel IDs that you would like to include in your report. By default, all Pixels are included.
  • Start Date: Define the start date for the report interval.
  • End Date: Define the end date for the report interval.
  • Type: Choose the type of report. See each section for more details on report types.
    • Custom Report
    • IP Conversion Pixel: Path to Conversion
    • IP Conversion Pixel: Page Visits
    • IP Conversion Pixel: Conversion Rate
    • Log Level Report
    • Reach/Frequency Report.
  • Timezone: Select the timezone that the report will generate, such as Seat Time Zone, User Time Zone, UTC, etc.
  • Dimensions: Categorical values that define how data is grouped and segmented in reports, such as Campaign Name, Advertiser, and Impression Time.

Dimensions:

  • Pixel ID
  • Pixel Name
  • Conversion Time
  • Impression Time
  • IP Address Truncated
  • IP Address Hashed
  • Home or Business
  • Zip Code
  • Region/State Code
  • Advertiser ID
  • Date
  • Custom Variable 1
  • Custom Variable 2
  • Custom Variable 3
  • Custom Variable 4
  • Other Parameters
  • Order ID: Reporting on this field requires this value to be dynamically passed on the IP Pixel using the Order Value or Order ID parameters. Check the Order ID or Order Value boxes when creating the IP Pixel for further guidance.
  • Order Value: Reporting on this field requires this value to be dynamically passed on the IP Pixel using the Order Value or Order ID parameters. Check the Order ID or Order Value boxes when creating the IP Pixel for further guidance.
  • Consumer ID

IP Conversion Pixel: Conversion Rate

Overview

The ‘Conversion Rate Report’ helps track the effectiveness of your ads by analyzing conversion rates day over day. To calculate the conversion rate for each day, divide ‘Conversions’ by ‘Imps’.

The conversion metric in this report matches the UI metrics when the ‘Line’ dimension is included. When this dimension is selected, conversions are not de-duplicated across line items. For example, if a user sees ads from two Lines under the same Campaign and completes one purchase, this will count as a conversion for both Line Items, and the Campaign will show two conversions.

For unique conversions across an advertiser or campaign, you can run a custom ‘IP Conversion Rate’ report without selecting the ‘Line ID’ dimension. This report will show unique conversions on the selected date(s). For unique conversions across a campaign flight, run the ‘IP Path to Conversion Report’ and de-duplicate the hashed IP address across all dates.

Create an IP Conversion Pixel: Conversion Rate Report

  1. Navigate to the Reporting tab and open the Custom Reporting dropdown section.
  2. Click ‘New Custom Report’.
  3. Select ‘IP Conversion Pixel: Conversion Rate’ as the Type.
  4. Fill out the required report details.
  5. Click ‘Save’.
  6. Expand the Custom Reporting dropdown section and click the ‘Download’ button next to the name of your custom report.
    • If Scheduled Automated Reports were selected, the report will be delivered via your chosen delivery method.

Below are the customizations available when creating the report:

  • Name: Enter a title for your report.
  • Schedule Automated Report: Choose this option to have the report sent to you on regular intervals. See the section for setup details Scheduled Reports
  • Advertiser ID: Select the Advertiser IDs that you would like to include in your report. By default, all Advertisers are included.
  • Campaign ID: Select the Campaign IDs that you would like to include in your report. By default, all Campaigns under the selected Advertisers are included.
  • Line ID: Select the Line IDs that you would like to include in your report. By default, all Lines under the selected Advertisers and Campaigns are included.
  • Pixel ID: Select the Pixel IDs that you would like to include in your report. By default, all Pixels are included.
  • Start Date: Define the start date for the report interval.
  • End Date: Define the end date for the report interval.
  • Type: Choose the type of report. See each section for more details on report types.
    • Custom Report
    • IP Conversion Pixel: Path to Conversion
    • IP Conversion Pixel: Page Visits
    • IP Conversion Pixel: Conversion Rate
    • Log Level Report
    • Reach/Frequency Report.
  • Timezone: Select the timezone that the report will generate, such as Seat Time Zone, User Time Zone, UTC, etc.
  • Lookback window: By default, the IP conversion pixels use a 30-day lookback window.
  • Dimensions: Categorical values that define how data is grouped and segmented in reports, such as Line ID and Line Name.

Log Level Reporting

Overview

Log level reporting provides advertisers with detailed bid request data for purchased inventory, with IP addresses and IFAs encrypted for privacy. Reports are delivered daily in UTC for the previous day’s activity. The user time zone offset is included in these reports and can be utilized to adjust the report time zone if needed. To receive log level reports, you must have either an AWS or Google Cloud account and have a scheduled report configured for delivery to s3 or Google Storage. Additionally, certain bid request fields contain numerical values that correspond to specific descriptions. The tables below provide mappings for device type, device connection type, geo type, video placement, video start delay, video protocol, and livestream values. For additional information can be found regarding the fields in the bid requests and bid responses in the Open RTB Specs. For bcat, refer to page 39, section 5.1 for a list of all IAB content categories.

Device Type

ValueDescription
1Mobile/Tablet
2Personal Computer
3Connected TV
4Phone
5Tablet
6Connected Device
7Set Top Box

Device Connection Type

ValueDescription
0Unknown
1Ethernet
2WIFI
3Cellular Network – Unknown Generation
4Cellular Network – 2G
5Cellular Network – 3G
6Cellular Network – 4G

Geo Type

ValueDescription
1GPS/Location Services
2IP Address
3User Provided (e.g. Registration data)

Video Placement

ValueDescription
1In-Stream
2In-Banner
3In-Article
4In-Feed
5Interstitial/Slider/Floating

Video Start Delay

ValueDescription
> 0 Mid-Roll (Value indicates start delay in second)
0Pre-Roll
-1Generic Mid-Roll
-2Generic Post-Roll

Video Protocol

ValueDescription
1VAST 1.0
2VAST 2.0
3VAST 3.0
4VAST 1.0 Wrapper
5VAST 2.0 Wrapper
6VAST 3.0 Wrapper
7VAST 4.0
8VAST 4.0 Wrapper
9DAAST 1.0
10DAAST 1.0 Wrapper

Livestream

ValueDescription
0Non-live Content
1Live Content

Create a Log Level Report:

  1. Navigate to the Reporting tab and open the Custom Reporting dropdown section.
  2. Click ‘New Custom Report’.
  3. Select ‘Log Level’ as the Type.
  4. Fill out the required report details.
  5. Click ‘Save’.
  6. To receive log level reports you must have either an AWS or Google Cloud account and have a scheduled report configured for delivery to s3 or Google Storage.

Below are the fields available to select when creating the report:

  • exchange: The SSP through which the auction or ad request is processed (e.g., Magnite, Index, etc).
  • auction_id: A unique identifier for the auction event, used to track the auction’s lifecycle.
  • imp_id: The impression id with in the context of the bid reques (several requests are sometimes sent at once)
  • imp_tagid: A unique identifier for the specific ad tag used to serve the impression.
  • imp_bidfloor: The minimum bid price set for the impression during the auction.
  • imp_bidfloorcur: The currency of the bid floor for the impression (e.g., USD, EUR).
  • seat_id: A unique identifier for the demand-side platform (DSP) or seat participating in the auction.
  • advertiser_id: A unique identifier for the advertiser in the ad ecosystem.
  • advertiser_code: A code associated with the advertiser for identification within the system.
  • campaign_id: A unique identifier for the specific advertising campaign.
  • campaign_code: A code used to identify and track the campaign.
  • line_id: A unique identifier for the line item within the campaign.
  • line_code: A code associated with the line item, often used for internal line management.
  • creative_id: A unique identifier for the creative or ad asset being served.
  • bid_price_millicents: The price the bidder is willing to pay for the impression, represented in millicents (1/1000 of a cent).
  • win_price_millicents: The price at which the impression was won, represented in millicents.
  • bid_timestamp: The timestamp indicating when the bid was placed in the auction.
  • win_timestamp: The timestamp indicating when the impression was won.
  • imp_timestamp: The timestamp indicating when the impression was served or displayed.
  • source_fd: Entity responsible for the final impression sale decision, where 0 = exchange, 1 = upstream source.
  • source_pchain: A chain or path of the sources involved in the bidding process for an impression.
  • creative_type: The type of creative, such as a display ad, video ad, audio ad, etc.
  • creative_categories: The IAB categories associated with the creative (e.g., “Comedy”, “Lifestyle”).
  • creative_duration: The duration of the creative (e.g., in seconds for an audio or video ad).
  • creative_domain: The domain that represents the brands website.
  • width: The width of the ad, typically for display or video creatives, in pixels.
  • height: The height of the ad, typically for display or video creatives, in pixels.
  • video_placement: placement type as specified in the open rtb 2.5 docs. 1:In-Stream, 2: In-Banner,3: In-Article,4: In-Feed,5: Interstitial/Slider/Floating
  • video_startdelay: Where in the feed the video plays . Specified in the open RTB 2.5 docs in the start delay section.
  • video_protocols: The vast protocol used for the imporessoin. Specified in the “Protocols” section in the open rtb 2.5 docs.
  • device_type: Integer that indicates the  type of device used to view the ad (e.g., mobile, tablet, desktop). Specified in the open RTB 2.5 docs in the section “Device type”
  • device_connectiontype: The type of internet connection used by the device (e.g., Wi-Fi, 4G, 5G). Specified in the open RTB 2.5 docs in the section “Connection type”
  • device_ifa: A unique identifier for the device used for advertising purposes (e.g., Apple’s IDFA or Android’s AAID), hashed for privacy.
  • device_make: The manufacturer or brand of the device (e.g., Apple, Samsung).
  • device_model: The model of the device (e.g., iPhone 13, Galaxy S21).
  • geo_country: The country of the user or device (e.g., US, Canada).
  • geo_region: The region or state where the user or device is located.
  • geo_zip: The postal or ZIP code of the user or device.
  • geo_metro: The metropolitan area the user or device is located in.
  • geo_lat: The latitude of the user’s or device’s location.
  • geo_long: The longitude of the user’s or device’s location.
  • utc_offset: The difference between the local time and UTC time, used for time-based targeting.
  • geo_type: integer indicating how the geographic information was determined. This is specified in the open rtb 2.5 docs under “Location Type”
  • geo_ipservice: An identifier for the service used to determine the geographic location based on the IP address.
  • ip: The IP address of the user or device (sometimes anonymized for privacy).
  • ip_hashed: The hashed version of the IP address for privacy.
  • device_language: The language setting of the device (e.g., “en-US” for English – United States).
  • os: The operating system running on the device (e.g., iOS, Android).
  • os_version: The version of the operating system (e.g., iOS 14.4).
  • hw_version: The hardware version of the device, identifying the physical capabilities (e.g., model revision).
  • auction_type: The type of auction being used (e.g., first-price, second-price auction).
  • bcat: Blocked iab categories as specified by the publisher. The categories can be found in the open rtb 2.5 docs.
  • currency: The currency used in the ad transaction (e.g., USD, EUR).
  • user_agent: The user agent string sent by the browser or app, identifying the device and software.
  • browser: The browser used by the device to interact with the content (e.g., Chrome, Safari).
  • site_domain: The domain name of the website where the ad is being displayed.
  • app_bundle: The unique bundle ID of the mobile app where the ad is served.
  • app_id: The unique identifier for the mobile app.
  • app_domain: The domain of the site representing the app.
  • app_name: The name of the mobile app.
  • app_cat: The IAB category of the mobile app.
  • app_storeurl: The URL link to the app’s store page (e.g., Google Play Store or Apple App Store).
  • content_id: A unique identifier for the specific audio or video content being served.
  • content_livestream: Indicates if the content is part of a live stream (1 = live stream, 0 = not).
  • content_context: Additional context or metadata about the content (e.g., episode, special).
  • content_len: The length of the content (in seconds).
  • content_genre: The genre of the content (e.g., comedy, music, news).
  • content_episode: The specific episode number or identifier if the content is episodic (e.g., podcast episode).
  • content_season: The season number if the content is part of a series.
  • content_title: The title of the content (e.g., the name of the podcast episode, song, or show).
  • content_series: The broader series name or identifier for episodic content.
  • content_url: The URL where the content can be accessed or streamed.
  • content_cat: The category of the content (e.g., “music”, “talk show”, “news”).
  • content_network: The network that distributes the content.
  • content_channel: The specific channel through which the content is served.
  • content_contentrating: The content rating (e.g., PG, R, suitable for children, etc.).
  • content_producer_name: The name of the producer or creator of the content.
  • publisher_id: A unique identifier for the publisher or content provider.
  • publisher_name: The name of the publisher or content provider.
  • publisher_domain: The domain of the publisher’s website or content platform.
  • private_auction: Indicates whether the auction is private (1 = private, 0 = public).
  • deal_id: A unique identifier for the specific deal in a private auction.
  • deal_at: bid type for the deal (first or second price).
  • deal_bidfloor: The bid floor set for the deal in the private auction.
  • deal_bidfloorcur: The currency of the bid floor in the deal (e.g., USD, EUR).
  • data_cost: The cost of the data used for the campaign.
  • revenue: The total revenue generated from the ad.
  • total_cost: The total cost incurred in serving the ad.
  • fees: Fees associated with the ad transaction (e.g., platform or network fees).
  • chrome_conv: Conversion data specific to Chrome browser users (if applicable).
  • conv_pix_id: A unique identifier for the conversion pixel used to track the ad’s performance.
  • site_page: The specific page on the website where the ad was displayed.
  • foot_traffic_fee: Fees associated with generating foot traffic via the ad campaign.
  • data_comm: Commissions associated with data use or sharing in the campaign.
  • art_fee: Fees related to usage of ART custom audiences.
  • contextual_fee: Fees related to contextual targeting.
  • dcm_hosting_fee: Fees associated with hosting the ad via google’s ad server.
  • cc_fee: Credit card fees for processing transactions related to the campaign.
  • chalice_fee: Fees associated with Chalice (a platform or service used for campaign tracking or delivery).
  • campaign_name: The name of the campaign being tracked.
  • line_name: The name of the specific line item within the campaign.
  • creative_name: The name of the specific creative or ad asset used in the campaign.
  • advertiser_name: The name of the advertiser running the campaign.

Download the CTV log level report schema for a full list of available fields.

ctv-log-level-report-schemaDownload

Reach/Frequency Report

Overview

The Reach/Frequency Report provides insights into the number of unique users reached by a campaign. Select the Advertisers, Campaigns, Lines, and Date Range to generate the report, which includes the following metrics:

  • Unique Device IDs (IFAs)
  • Unique IP Addresses
  • Impressions Served

Estimate frequency by dividing total impressions served by either unique device IDs or unique IP addresses.

Create a Reach/Frequency Report:

  1. Navigate to the Reporting Tab and open the Custom Reporting dropdown section.
  2. Click ‘New Custom Report’.
  3. Select ‘Reach/Frequency’ as the Type.
  4. Fill out the required report details.
  5. Click ‘Save’.
  6. Expand the Custom Reporting dropdown section and click the ‘Download’ button associated with the name of your custom report.
    • If Scheduled Automated Reports were selected, the report will be accessible via your chosen delivery method.

Below are the customizations available when creating the report:

  • Name: Enter a title for your report.
  • Schedule Automated Report: Choose this option to have the report sent to you on regular intervals. See the section for setup details Scheduled Reports
  • Advertiser ID: Select the Advertiser IDs that you would like to include in your report. By default, all Advertisers are included.
  • Pixel ID: Select the Pixel IDs that you would like to include in your report. By default, all Pixels are included.
  • Start Date: Define the start date for the report interval.
  • End Date: Define the end date for the report interval.
  • Type: Choose the type of report. See each section for more details on report types.
    • Custom Report
    • IP Conversion Pixel: Path to Conversion
    • IP Conversion Pixel: Page Visits
    • IP Conversion Pixel: Conversion Rate
    • Log Level Report
    • Reach/Frequency Report.
  • Timezone: Select the timezone that the report will generate, such as Seat Time Zone, User Time Zone, UTC, etc.
  • Dimensions: Categorical values that define how data is grouped and segmented in reports, such as Campaign Name, Advertiser ID, and Line ID.

Dimensions:

  • Advertiser ID
  • Advertiser Name
  • Campaign ID
  • Campaign Name
  • Line ID
  • Line Name

© 2025 Pontiac Wiki Sec · All Rights Reserved · Developed by RDK

  • Contact Us
  • Privacy Policy
  • Terms & Conditions
  • Pontiac.media