Quantcast
Drop gzipped CSV audience files (cookie → segment ID) into a Quantcast-provided S3 bucket. Quantcast ingests files from the first_party/<data_owner_pcode>/ prefix and onboards the audience for Activate targeting.
Prerequisites
- A Quantcast-provided S3 bucket (default:
quantcast-ai-zeotap-inboundinus-west-2). Coordinate with your Quantcast account manager. - AWS access key and secret access key issued by Quantcast via a one-time-secret link (valid for 1 year from issue).
- Your Data Owner PCode (starts with
p-) — Quantcast’s identifier for your account. - Your Source PCode (starts with
p-) — Quantcast’s identifier for the Zeotap data feed. - A Segment ID per audience (alphanumeric/hyphen; auto-generated by Quantcast or provided per onboarded channel segment).
Authentication
Quantcast delivers AWS credentials through their one-time-secret portal (link valid 7 days, credentials valid 1 year).
- Retrieve the access key + secret from the Quantcast one-time-secret link.
- Paste them into Access Key ID and Secret Access Key.
- Rotate credentials before the 1-year expiry to avoid sync failures.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| S3 Bucket Name | Text | Yes | Quantcast inbound bucket. Default: quantcast-ai-zeotap-inbound. |
| S3 Region | Text | Yes | AWS region of the bucket. Default: us-west-2. |
| Data Owner PCode | Text | Yes | Quantcast-assigned customer PCode (prefix p-). |
| Source PCode | Text | Yes | Quantcast-assigned source PCode (prefix p-). |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Segment ID | Text | Yes | Quantcast channel segment ID associated with this audience. |
Supported Operations
Sync Modes
Quantcast is audience-only.
Audience Sync Modes
| Mode | Supported |
|---|---|
| Add | Yes |
| Mirror | Yes (each drop is treated as a full refresh by Quantcast) |
| Remove | No |
| Upsert | No |
Features
- Field Mapping: No
- Schema Introspection: No
How It Works
For each batch, Zeotap writes a gzipped CSV file into the Quantcast bucket under:
first_party/<data_owner_pcode>/<source_pcode>_segments_map_<NNNNN>_<YYYY>_<MM>_<DD>_<hh>_<mm>_<ss>_incr.csv.gzThe file contains no header and three columns per row, separated by commas:
<data_owner_pcode>,<cookie>,<segment_id>Multiple segment IDs (if ever needed) are joined with |. Quantcast treats every drop as a full refresh per the Zeotap integration contract.
Supported cookie fields
Zeotap looks up the cookie value from these row fields (first match wins):
quantcast_cookiequantcast_id,qcidcookie_id,cookietdid,trade_desk_idexternal_id,user_id,uid
Rows without any of these are skipped and reported as failed rows.
Limits
- Recommended segment size: 1k – 10k cookies; per-file maximum: 100 GB.
- No daily file-count limit; Quantcast processes files within 1–3 days of drop.
Troubleshooting
AccessDenied on PutObject
The access key/secret may have expired (they are valid for 1 year) or been rotated on the Quantcast side. Request a fresh one-time-secret link from Quantcast and update the credentials.
File dropped but segment not appearing
Quantcast ingests drops asynchronously. Allow 1–3 days. Verify the key matches the documented format (first_party/<data_owner_pcode>/<source_pcode>_segments_map_...) and that both PCodes are exactly as Quantcast provisioned them.
data_owner_pcode / source_pcode validation failure
Both PCodes must start with p- — paste them exactly as Quantcast provided.
Rows skipped (“no cookie identifier found”)
Your audience query does not project any of the recognised cookie fields. Add at least one of: quantcast_cookie, quantcast_id, cookie_id, external_id, user_id.