RTB House
Drop gzipped tab-separated audience files (cookie ID → segment ID) into the RTB House-provided S3 bucket under <tagging_hash>/<client_name>/.
Prerequisites
- A configured S3 bucket with RTB House (production:
rtbhouse-zeotap; testing:rtbhouse-zeotap-testing). - AWS access key + secret issued by RTB House with
PutObject,GetObject, andListBucketpermission. - Your tagging_hash (contact your RTB House POC).
- Your client_name as embedded in the object path/filename (e.g.
Douglas). - Cookie-syncing enabled between Zeotap and RTB House (RTB House does not accept Mobile Advertising IDs in this push).
Authentication
AWS IAM access keys (AWS keys RTB House issues for their inbound bucket).
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| S3 Bucket | Text | Yes | RTB House inbound bucket. Default: rtbhouse-zeotap. |
| S3 Region | Text | Yes | AWS region of the bucket. Default: eu-west-1. |
| Client Name | Text | Yes | Customer identifier embedded in object path + filename. |
| Tagging Hash | Text | Yes | RTB House-assigned tagging_hash. |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Segment ID | Text | Yes | RTB House segment ID associated with this audience. Multiple IDs can be comma-separated and are written as-is. |
Supported Operations
Sync Modes
RTB House is audience-only.
Audience Sync Modes
| Mode | Supported |
|---|---|
| Add | Yes |
| Remove | Yes |
| Mirror | Yes |
| Upsert | No (not distinct from Add for S3 drops) |
Features
- Field Mapping: No
- Schema Introspection: No
How It Works
Each batch produces up to two gzipped tab-separated files:
s3://<bucket>/<tagging_hash>/<client_name>/zeotap_<client_name>_add_<YYYYMMDD-HHMMSSsss>.csv.gz
s3://<bucket>/<tagging_hash>/<client_name>/zeotap_<client_name>_remove_<YYYYMMDD-HHMMSSsss>.csv.gzFile body: no header, tab-separated, one row per user:
<userID>\t<segID1>,<segID2>,...Sync mode behaviour:
- Add: every row → add file.
- Remove: every row → remove file.
- Mirror: rows flagged
removedby DiffOps → remove file; others → add file.
Supported cookie fields
Zeotap extracts the cookie from (first match wins):
rtb_house_cookie,rtbhouse_cookie,rtb_cookiecookie_id,cookietdid,trade_desk_idexternal_id,user_id,uid
Rows without any of these are skipped and reported as failed.
Mobile Advertising IDs
RTB House explicitly excludes MAIDs from this integration. Do not map GAID/IDFA fields — they will not be accepted.
Limits
- Maximum file size: 5 GB per file.
- Retention: RTB House processes drops asynchronously; allow up to 24 hours for audiences to become available.
Related — CAPI Flow
RTB House also supports a real-time CAPI (Conversions API) push for Journeys event streaming. The CAPI flow uses a separate endpoint (https://omni.creativecdn.com/partner/omni/postbacks) and requires a pkey credential. It is not implemented by this destination; it is surfaced through the Journeys CAPI module.
Troubleshooting
PutObject returned AccessDenied
The IAM keys RTB House provided may have been rotated or scoped away from your bucket prefix. Contact RTB House to reissue credentials.
Rows skipped (“no cookie identifier found”)
Your audience query does not include a cookie-shaped identifier. Map rtb_house_cookie (preferred) or any of the accepted fields above.
Audience not appearing in RTB House
Allow up to 24 hours for asynchronous ingestion. Verify the object path begins with <tagging_hash>/<client_name>/ and that tagging_hash matches what RTB House provisioned.