Pontiac Docs Pontiac Docs

Custom Reporting

Custom Reporting

  • Standard Custom Reports
  • IP Conversion Pixel: Path to Conversion
  • IP Conversion Pixel: Page Visits
  • IP Conversion Pixel: Conversion Rate
  • Reach/Frequency Report
  • Log Level Reporting
  1. Home
  2. Reporting & Attribution
  3. Custom Reporting

Standard Custom Reports

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. Select the advertisers, campaigns or line items, dimensions, metrics & date range to generate a custom report. All custom reports created will be in UTC time zone.

Custom reports are limited to 500,000 rows. If your report exceeds the maximum number of returnable records, there will be a yellow caution symbol next to the name of the report with an error stating that the data is incomplete. The report will still run and will return the first 500,000 rows, but the data will not be complete for the selected dates & parameters. If you need to receive additional data, you can reach out through the Help Center, separate the report into multiple reports, or limit the dimensions selected to decrease the number of rows.

Custom Reports will remain downloadable in the platform for 30 days. Expired reports must be ‘Rerun’ at a later date, however and it is possible that certain data points will no longer be available. 

IP Conversion Pixel: Path to Conversion

The ‘Path to Conversion’ report provides data on the IP conversions registered as well as on the impressions served through Pontiac campaigns to those users that converted. This report can be utilized to see the entire pathway to conversion from each impression the user viewed to the action they completed on your website.

The column ‘imp_time’ will indicate when the impression was served through Pontiac to a user that visited or converted on the site where the pixel is placed. The total number of ‘imp_times’ indicates the number of impressions that were served to users that then converted, this will correspond to the ‘Attributed Imps’ field in the IP Conversion Pixel metrics under the Advertiser.

The ‘conv_time’ column will indicate the time the action or conversion took place on the site. The total number of unique ‘conv_times’ is the total number of unique conversions or visits that were driven by your campaign. This will correspond to the ‘Total Convs’ field in the IP Conversion Pixel metrics under the Advertiser.

IP conversion pixels have a standard lookback of 30 days in the metrics that are displayed under the Advertiser. This means that the user must complete the desired action within 30 days of seeing the ad for it to count as a conversion. If you would like to pull reporting with a custom lookback window, this can be done in this report. Select from ‘5’, ‘7’, ’15’ or ’30’ from the ‘Lookback window’ dropdown .

Report Dimensions:

  • Pontiac pixel Id
  • Conversion time
  • Imp Time
  • IP Address
  • Zip Code
  • Site Domain
  • Exchange
  • Region/State
  • Auction id
  • User id
  • Advertiser
  • Line
  • Device Type
  • Date
  • Creative Id
  • Order ID*
  • Order Value*
  • Deal Name
  • Publisher Name
  • Content Network
  • Content Channel
  • Content Series
  • Content Title
  • Content Genre

*work with your web developer to dynamically pass these values on IP pixel

IP Conversion Pixel: Page Visits

The ‘Page visits’ report will only provide data on ALL page visits or loads for this pixel. ‘Visit Time’ indicates the time of the page visit. This is not a Conversion event attributed to your campaign, it is total page visits independent of media served.

IP Conversion Pixel: Conversion Rate

Analyze conversion rate day over day to track the effectiveness of your ads with the ‘Conversion Rate Report’. To calculate conversion rate for each day, divide ‘Conversions’ by ‘Imps’.

NOTE: The conversion metric in this report will match the metrics in the UI when the ‘Line’ dimension is included. When this dimension is included, conversions are NOT de-duplicated across line items. For example, if a user sees an ad from 2 lines under a campaign and then completes one purchase, this will be counted as a conversion attributed to both Line Items. This will also appear as 2 conversions on the Campaign in the interface as the associated line metrics are aggregated.

If you would like to see unique conversions under an advertiser or campaign, you can run a custom ‘IP Conversion Rate’ report without selecting the ‘Line ID’ dimension. These are uniques on the selected date/s. For uniques across a campaign flight, run an ‘IP Path to Conversion Report’ and de-duplicate the hashed IP address across all dates.

Reach/Frequency Report

The Reach/Frequency report is designed to provide data on the number of unique users that were reached by a campaign. Select the Advertiser/s, Campaign/s, Line Item/s, and date range, then run the report to view the following metrics:
Unique Device IDs (IFAs)
Unique IP Addresses
Impressions served

Frequency can be estimated by dividing total impressions served by either device id or IP.

Log Level Reporting

Log level reporting provides advertisers with every piece of necessary information available in the bid requests for inventory that they have purchased. For privacy reasons, IP addresses and IFAs are encrypted in log level reports. Log level reports are delivered daily for the previous day’s activity. To receive log level reports you must have either an AWS account and have a scheduled report configured for delivery to S3, or set up delivery via FTP. Download the CTV log level report schema to see every field that is passed:

ctv-log-level-report-schemaDownload

Various fields in the bid request contain a numerical value that can be mapped to a description. The tables below provide the mappings for device type, geo type, video protocol and livestream values. Additional information can be found regarding the fields required or utilized in the bid requests & bid responses in the Open RTB specs.

Device Type

Video Protocol

Geo Type

Livestream

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

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