Quantcast

Datafly Signal delivers conversion events to Quantcast Measure server-to-server using the Conversion API. This augments the Quantcast Live Tag with reliable server-side conversions that are not affected by ad blockers or browser tracking prevention, and lets you report conversions that happen after a delay or off the website.

Prerequisites

Before configuring Quantcast in Signal, you need a Quantcast Measure account and your account P-Code.

Step 1: Find your P-Code (Account ID)

Your P-Code is the account identifier Quantcast uses to attribute events to your account. It is the same value as the qacct parameter in your Quantcast Live Tag (it looks like p-XXXXXXXXXXXXX).

1. Sign in to your Quantcast Measure account.
2. Open your account settings, or inspect your existing Live Tag on your site.
3. Copy the qacct / P-Code value.

Step 2: Keep the Live Tag running (recommended)

The Conversion API is designed to augment the Live Tag, not replace it. The Live Tag captures the Quantcast browser token, which gives the highest match accuracy when you send server-side conversions. Keep the Live Tag deployed so Signal can link conversions back to web activity.

Configure in Signal

Configuration Fields

Management UI Setup

1. Go to Integrations > Add Integration > Quantcast.
2. Choose the Default preset (page views plus core conversions).
3. Enter your p_code.
4. Select consent categories (typically advertising or marketing).
5. Click Save.

API Endpoint

POST https://pixel.quantserve.com/conversion?a={p_code}

There is no API key. Requests are scoped to your account by the a query parameter (your P-Code). The request body is a JSON array of conversion objects, sent with Content-Type: application/json.

Identity Signals

Quantcast matches each server-side conversion to a user using the signals below. The more you provide, the better the match.

How to send user data

Call datafly.identify() when a user logs in, registers, or submits a form:

datafly.identify("user-123", {
  email: "jane.doe@example.com"
});

Signal normalises and hashes the email before sending it to Quantcast as user.email.

Consent

The Quantcast Conversion API has no per-event consent field. Signal enforces consent upstream: when a visitor has not granted marketing consent, the event is dropped by the pipeline and never reaches Quantcast. Set the integration’s consent categories (typically advertising) so this gating applies.

Event Mapping

Default preset

Conversion details map as follows: properties.revenue → revenue (a plain numeric value in your account’s billing currency — there is no currency field on this API), properties.order_id → orderid, and properties.category → product_category. The page URL and referrer are sent on every event as url and referer, and the event time is sent as a Unix epoch timestamp in time.

To customise, edit the integration’s Field Mappings in the Management UI.

Example: Purchase event

Datafly.js call:

datafly.track("Order Completed", {
  order_id: "ORD-001",
  revenue: 129.99,
  category: "apparel"
});

Quantcast Conversion API payload sent by Signal:

[
  {
    "name": "Order Completed",
    "time": 1717689600,
    "url": "https://example.com/checkout/confirmation",
    "referer": "https://example.com/checkout/payment",
    "orderid": "ORD-001",
    "revenue": 129.99,
    "product_category": "apparel",
    "user": {
      "token": "abc123…",
      "external_id": "a1b2c3d4e5f6",
      "email": "5e88…<sha256>…",
      "client_ip": "203.0.113.50",
      "client_user_agent": "Mozilla/5.0 …"
    }
  }
]

Testing

1. Trigger a conversion event on your website (e.g. complete a test order).
2. In Signal’s event debugger, confirm the event is delivered to Quantcast and the response is HTTP 200.
3. Confirm the outgoing payload is a JSON array, that user.email is a SHA-256 hash (never raw), and that revenue carries no currency symbol.
4. In your Quantcast Measure account, confirm the conversion appears against your P-Code (allow time for processing).

Troubleshooting