Skip to main content

​
Introduction

Quantcast is a programmatic advertising platform that combines audience measurement with display, video, and audio ad delivery. The connector exposes campaign performance — impressions, clicks, viewability, completion rates, reach, frequency, and spend — through Quantcast’s GraphQL Developer API. Reporting follows a four-level campaign hierarchy: ad account, campaign, ad set, and ad or creative. Reflecting Quantcast’s roots as a measurement platform, audience and measurement signals such as device and household reach, completion rates, and viewability are first-class metrics alongside spend and clicks. As a marketing connector, metrics, breakdowns, and currencies are standardized so widgets can aggregate across other ad-platform and analytics sources without additional configuration. To connect this data source, see How to connect Quantcast to Adriel.

​
Data refresh strategy

​
Architecture data

Architecture covers ad account, campaign, ad set, and ad metadata. It refreshes twice daily, at 4:00 PM UTC and 5:00 AM UTC. Ad-to-campaign IDs are back-filled during the fetch, and VAST video creatives are resolved during the same pass.

​
Reports data

Reports include daily performance for ad account, campaign, ad set, and ad. Real-time. Report data is queried live from the GraphQL API when a dashboard loads, so visits reflect current data. Scheduled jobs also keep recent ranges warm:
  • 5:00 PM UTC — syncs the last 9 days across ad account, campaign, ad set, and ad.
  • 11:40 PM UTC and 6:40 AM UTC — sync the last 3 days across the same levels.
  • 7:30 AM UTC on the 1st and 15th of each month — syncs the last 30 days across the same levels.
The metric catalogue is fetched per ad account and cached for one hour, so metrics newly published on the Quantcast side become available without a redeploy once the cache expires.

​
Architecture levels

Ad account → Campaign → Ad set → Ad / Creative

​
Date range limits

​
Metrics

How to read the columns Data type uses this vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean. API Key in code style like impressions is the literal Quantcast API field name. Italic text describes how a value is produced when it does not map cleanly to a single API field, including metrics discovered dynamically per account.
The connector models 41 standard fields, discovered per ad account from the availableBreakdownsAndMetrics GraphQL query and cached for one hour. Some fields populate only when the underlying campaign carries the matching ad format (audio, video, conversion pixels, or brand-lift surveys).

​
Delivery and clicks

​
Viewability

​
Spend and fees

​
Reach and frequency

​
Results and revenue

​
Video completion

​
Audio completion

​
Breakdowns

​
Standard hierarchy

​
Creative attributes

​
Time grouping

Quantcast returns daily records; Adriel groups them into these views for reporting. Each grouping has its own maximum date range (see Date range limits).

​
Limitations

  • Format-dependent metrics — video, audio, brand-lift survey, and conversion-pixel metrics populate only when the campaign runs the matching ad format. Campaigns without that format leave those columns empty.
  • Reach is not additive — device and household reach are deduplicated only within the query’s date range, so longer windows produce higher reach numbers. Reach cannot be summed across separate ranges.
  • Two revenue keys merge — Quantcast returns both revenue and pixelRevenue; both map to the standardized Revenue field, so reports that mix conversion sources sum into the same column.
  • Serial, rate-limited fetching — report jobs run one at a time per data source (concurrency 1) to respect Quantcast’s rate limits. Rate-limit errors surface with a retry-friendly message rather than failing the dashboard.
  • Per-account metric availability — the metric catalogue is discovered per ad account and cached for one hour, so a newly published Quantcast metric can take up to an hour to appear.

​
API references

​
See also