There are two primary approaches to reporting:

• RTB Object Reporting: Retrieve performance metrics alongside Advertisers, Campaigns, Lines, and other RTB objects.
• Custom Reports: Generate a report using selected dimensions, metrics, date ranges, and reporting intervals.

Scheduled reporting can also be used when the same report needs to be generated and delivered on a recurring basis.

RTB Object Reporting

RTB object endpoints can be used to retrieve object information together with performance metrics.

This is useful when an application needs to display or regularly retrieve performance for objects such as:

• Advertisers
• Campaigns
• Lines

Reporting parameters can be added to the applicable RTB endpoint to request metrics.

For example:

GET /rtb/advertisers?interval=1&metrics=true

The metrics=true parameter tells the API to include performance metrics with the returned objects.

The applicable interval determines the reporting period used for those metrics.

This approach is useful for dashboards, account management tools, and integrations that need performance data together with the underlying Pontiac objects.

For more granular reporting or reporting across a specific historical date range, use Custom Reports.

Custom Reports

Custom Reports allow you to define the structure of the report by selecting:

• Date range
• Reporting interval
• Dimensions
• Metrics
• Applicable Advertisers, Campaigns, Lines, or other filters

A Custom Report can be used when the predefined RTB object metrics do not provide the level of detail required.

For example, a report could be configured to return performance broken out by:

• Date
• Advertiser
• Campaign
• Line
• Creative

with metrics such as:

• Impressions
• Clicks
• Spend
• Conversions
• Post-Click Conversions
• Post-View Conversions
• Video or Audio events, where applicable

The complete list of supported dimensions and metrics is available in the API endpoint documentation.

Dimensions

Dimensions determine how report data is grouped.

For example, selecting:

Date
Line
Creative

produces reporting broken out by each unique combination of Date, Line, and Creative.

Adding more dimensions increases the granularity of the report and may significantly increase the number of returned rows.

Common dimensions may include:

• Date
• Hour
• Advertiser
• Campaign
• Line
• Creative
• Exchange
• Deal
• Geography
• Device
• Site or App
• Audience or Segment
• Other inventory and content dimensions

Only include dimensions that are required for the intended analysis.

Metrics

Metrics are the numerical performance values returned in the report.

Common metrics include:

• Impressions
• Clicks
• CTR
• Spend
• Conversions
• Post-Click Conversions
• Post-View Conversions
• Video Starts
• Video Quartiles
• Video Completions
• Audio events
• Other supported performance metrics

Metric availability can depend on the selected dimensions, inventory type, and report type.

Refer to the API endpoint documentation for the current list of available metrics.

Reporting Interval

The reporting interval determines the time granularity of the results.

For example, a report may return:

• Hourly data
• Daily data
• Aggregated data for the requested period

Use hourly reporting when performance needs to be analyzed within individual days.

Use daily reporting when analyzing performance over multiple days or longer Campaign periods.

The reporting interval is separate from the overall date range. For example, a report covering September 1 through September 30 with a daily interval returns performance broken out by each day in that date range.

Date Ranges

When using reports that support a defined date range, specify the applicable start and end dates for the period you want to analyze.

Historical reporting should be requested using the applicable reporting or Custom Report endpoint rather than relying only on a relative reporting interval such as “yesterday.”

This is especially important for integrations that need to backfill data if a scheduled API pull is missed.

For example, if an integration normally retrieves yesterday’s Creative performance each morning but fails to run, a Custom Report can be used to retrieve the missing historical date.

Time Zones

Time zone selection is important when comparing API reporting with data displayed in the Pontiac interface or with reports generated by another system.

Reporting dates and hours should always be interpreted using the timezone applicable to the report.

When reporting is displayed in a selected timezone, hourly data is converted into that timezone before it is presented.

Integrations that store daily or hourly reporting should keep the report timezone consistent across requests to avoid assigning activity to different dates or hours.

This is particularly important when:

• Comparing API results with Pontiac interface reporting
• Combining reports generated in different time zones
• Running scheduled reports
• Aggregating hourly data into daily totals

Some reports are generated asynchronously rather than returned immediately with the initial request.

When a report is submitted, the API may first return information about the report configuration and its current status.

The integration should then use the applicable report endpoint to check the report status and retrieve the completed results.

Do not assume that a successful report submission means the report data is immediately available.

Scheduled Reports can be used when the same reporting configuration needs to run repeatedly.

This can be useful for integrations that need recurring data exports for:

• Daily performance reporting
• Client dashboards
• Internal analytics
• Data warehouse ingestion
• Campaign monitoring

When configuring scheduled reporting, pay particular attention to:

• Reporting interval
• Date range or relative reporting period
• Timezone
• Dimensions
• Metrics
• Delivery schedule

For API integrations that require greater control over when data is retrieved, the application can also run its own scheduled API process rather than relying on a Pontiac Scheduled Report.

Master Seat credentials can be used to retrieve Line-level performance across associated Sub-Seats.

For example:

GET /rtb/metrics/line?sub-seats-only=true

Using sub-seats-only=true with Master Seat credentials returns Line-level metrics for the Master Seat’s associated Sub-Seats.

Because Lines belong to Campaigns within each Sub-Seat, the returned data can be used to report performance by Sub-Seat, Campaign, and Line without switching the authenticated session into each Sub-Seat individually.

This is useful for Master Seat integrations that need to aggregate reporting across multiple Sub-Seats from a single authenticated session.

For example, a Master Seat reporting workflow can:

1. Authenticate using the Master Seat credentials.
2. Request:

/rtb/metrics/line?sub-seats-only=true

3. Use the returned Seat, Campaign, and Line identifiers to separate or aggregate performance by Sub-Seat.

This approach is recommended for cross-Sub-Seat reporting when Line-level metrics provide the required level of detail.

When building a reporting integration:

• Use RTB metrics endpoints when you need performance data for Advertisers, Campaigns, or Lines.
• Use Custom Reports when you need specific dimensions, metrics, date ranges, or greater reporting granularity.
• For Master Seat reporting across Sub-Seats, use /rtb/metrics/line?sub-seats-only=true with the Master Seat credentials when Line-level reporting provides the required data.
• Request only the dimensions and metrics required for the use case to avoid unnecessarily large reports.
• Use a consistent timezone when storing or comparing reporting data.
• Store Pontiac object IDs along with object names so reporting can be reliably associated with the correct Advertisers, Campaigns, Lines, and Creatives.
• For reports that are generated asynchronously, confirm that the report has completed before attempting to retrieve the results.

For the complete list of reporting endpoints, dimensions, metrics, and supported request parameters, refer to the current Pontiac API documentation: https://api.pontiac.media/docs/#/