Integrations / Advertising
Quantcast
Server-side conversion delivery to the Quantcast Measure Conversion API. Sends a bare JSON array of conversion objects to pixel.quantserve.com/conversion, matched via the Quantcast browser token (__qca) or IP + User-Agent, with SHA-256 hashed email and a raw external_id. Carries event name, hierarchical labels, revenue (billing currency), order id, and product category.
Datafly Signal delivers first-party events to Quantcast server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Quantcast expects.
Why route Quantcast through Datafly Signal
Conversions survive ad blockers and tracking prevention
A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari's ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions Quantcast optimises against are not filtered by the browser.
Email hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Quantcast receives match keys rather than raw personal data.
Client IP and user agent are preserved
Server-to-server delivery normally loses both, which weakens matching. Signal forwards the genuine visitor values as request headers so Quantcast attributes the event to the right session.
One consent decision governs every destination
Quantcast is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
generate_leadpagepurchaserefundsign_upview_itemVertical presets
Default. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Quantcast documentation.
Frequently asked questions
Does Datafly Signal integrate with Quantcast?
Yes. Datafly Signal delivers first-party events to Quantcast server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Quantcast expects. The integration is included in every deployment at no additional cost.
How is server-side Quantcast tracking different from the Quantcast tag?
The Quantcast tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Quantcast from your server, so delivery does not depend on browser conditions.
What personal data is sent to Quantcast?
Email are normalised and SHA-256 hashed inside your own deployment before delivery, so Quantcast receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Quantcast?
The blueprint ships with mappings for generate_lead, page, purchase, refund, sign_up, view_item. Any event in your schema can be mapped to Quantcast through pipeline configuration without a code change.
Do I need to keep the Quantcast tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so Quantcast deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Quantcast server-side?
See how Datafly Signal delivers first-party events to Quantcast from infrastructure you control, with hashed identity and consent enforcement built in.