IntegrationsAdvertisingQuantcast

Quantcast

Datafly Signal sends conversions to Quantcast server-to-server through the Conversion API, which augments the Quantcast Live Tag with events that happen outside the browser.

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 what Quantcast receives is not filtered by the browser.
  • 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.
  • No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.

Prerequisites

Enable the Conversion API

Ask Quantcast support to enable the Conversion API on your account. Until it is enabled the API answers “Conversions API is not enabled for this account”.

Choose how Quantcast identifies the visitor

Either send your own identifier in Live Tag as external_id (Signal sends the signed-in user ID, else the Signal visitor ID, so Live Tag must send the same value), or collect a Quantcast browser token in the browser and store it in an ID provider named quantcast_token.

Find your P-Code

Your account ID starts with p- and is the qacct value in Live Tag.

Configure in Signal

Configuration Fields

FieldRequiredDescription
p_codeYesYour Quantcast account identifier (P-Code), the same value as the qacct parameter in the Quantcast Live Tag. Sent as the ‘a’ query parameter on every Conversion API request. Find it in your Quantcast Measure account settings or in your existing Live Tag.

Management UI Setup

  1. Go to Integrations > Add Integration > Quantcast.
  2. Choose a preset: Default (default), Retail (ecommerce), Lead Generation (lead_gen), Insurance (insurance).
  3. Fill in the fields above and click Save.

Request format

A JSON array of conversion objects. There is no API key: the account is the a query parameter. Revenue is in the account’s billing currency; there is no currency field.

POST https://pixel.quantserve.com/conversion?a={p_code}
[
 {
  "event": {
   "order_id": "ORD-1001",
   "product_category": "Jackets,Accessories",
   "revenue": 259.99
  },
  "name": "Order Completed",
  "referer": "https://www.example.com/",
  "time": 1758500000,
  "url": "https://shop.example.co.uk/checkout/done",
  "user": {
   "client_ip": "203.0.113.9",
   "client_user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7)",
   "external_id": "crm-user-9",
   "token": "Q0--svLtoken"
  }
 }
]

Event Mapping

Signal eventVendor eventPresets
pagePage ViewDefault
view_itemProduct ViewedDefault, Retail
generate_leadLeadDefault, Lead Generation, Insurance
sign_upSign UpDefault, Lead Generation
purchaseOrder CompletedDefault, Retail
add_to_cartAdd To CartRetail
begin_checkoutCheckout StartedRetail
get_quoteQuote StartedInsurance
quote_completedQuote CompletedInsurance
purchasePolicy PurchasedInsurance

Signal forwards event properties the preset does not map unless the integration’s strict output contract is on. Turn on strict_output_contract for this integration so only the documented fields are sent.

Identity

user.external_id (the signed-in user ID, else the Signal visitor ID) is always sent, plus user.token when the browser token is collected, and the visitor’s IP and user agent. Quantcast does not accept email or any other personal data, so none is sent.

Consent

Quantcast is an advertising destination and requires marketing consent by default.

Troubleshooting

ProblemSolution
”Conversions API is not enabled for this account”Ask Quantcast support to enable it.
Conversions not attributedLive Tag must send the same external_id as Signal, or collect a browser token.

Blueprint

The Quantcast blueprint version is 0.6.0. It was last reviewed against the vendor’s documentation on 2026-09-22.

See also

AdformRokt