Configure a Streaming Activation Destination
Connect a CDP to an external marketing or advertising platform so that audience membership changes are delivered in real time or on a scheduled basis.
Activation destination configuration creates a live data channel from the CDP's audience engine to an external system — an advertising platform, a cloud storage bucket, an email service provider, or a custom webhook. The core output is a verified, credentialed connection paired with a segment-to-destination mapping that governs which audiences flow where and on what schedule. Practitioners must decide credential management (OAuth, API key, access-key/secret), field mapping (which profile attributes accompany the membership signal), deduplication strategy, and export cadence (real-time streaming for advertising vs. scheduled batches for email).
Different destination types have materially different latency and payload characteristics. Advertising destinations (Google DV360, Meta, LinkedIn) typically use cookie- or device-ID-based membership signals and require platform-level allow-listing arrangements with the ad network. Cloud-storage destinations (S3, SFTP, Azure Blob) use file-based exports and serve email marketing platforms that ingest flat audience lists on a schedule. The choice between these patterns affects both the real-time responsiveness of campaigns and the infrastructure complexity of the integration.
Parallel viability note: Activation destinations are a core feature of every major CDP and reverse-ETL tool. Hightouch, Census, and Polytomic all provide visual destination connectors to the same advertising and cloud-storage endpoints, operating directly against a data warehouse rather than a profile store. The AEP Destinations Catalog includes 100+ pre-built connectors maintained by Adobe and partners, and also exposes a Destinations SDK for custom endpoint development. For composable-stack teams, reverse-ETL tools provide comparable breadth, but latency for advertising destinations depends on the underlying sync frequency, which is typically minutes rather than seconds.
Side-by-side implementations
In AEP Real-time CDP, destinations are configured via the Destinations Catalog in the UI. For advertising destinations such as Google Display & Video 360, the practitioner authenticates with an Advertiser ID and Account Type, selects one or more segments to activate, and defines a segment schedule. For batch file destinations such as Amazon S3, the practitioner provides bucket credentials, configures an incremental-file export schedule (e.g., hourly every 3 hours), maps profile fields including a deduplication key (e.g., ECID), and finishes the wizard. Once configured, the platform streams membership signals to advertising destinations in near-real-time and exports CSV/Parquet files to cloud storage destinations on the configured cadence. For warehouse destinations, AEP's Snowflake Batch destination writes audience membership data directly to Snowflake tables on a configurable schedule. **June 2026 migration required**: AEP changed the Snowflake Batch destination table structure in March 2026. New connections export one row per audience membership per profile using a column-per-attribute format (columns: `TS`, `MERGE_POLICY_ID`, `AUDIENCE_ID`, `AUDIENCE_NAME`, `AUDIENCE_ORIGIN`, `AUDIENCE_STATUS`). The legacy format — one `ups_<audience-id>` column per audience — is deprecated at end of June 2026. During the transition period, both formats coexist within the same connection; new tables are prefixed `V2_`. Customers using the legacy format must migrate before June 2026 end-of-month. Additional constraints for this destination type: exported data has a 7-day TTL; Azure Private Link connections are not supported.
Capability: Reverse-ETL (CDW-to-Destination Sync)
Parallel implementation not yet available.
In Hightouch, a Destination is configured by selecting the target platform (e.g., Google DV360, Amazon Ads, Meta Ads) from the Destinations catalog and authenticating with the platform's API credentials. A Sync links a Hightouch Model (a SQL query against Snowflake or any connected data warehouse) to the Destination, mapping warehouse columns to destination-specific field names. For advertising destinations, Hightouch Match Booster handles identity resolution and PII-safe delivery: match keys are hashed via SHA256 or MD5 before transmission, supporting email, phone, MAIDs (mobile advertising IDs), postal address, and IP as match key types. Match Booster additionally supports household-level matching and CTV ID translation for cross-device advertising campaigns. For S3/Azure/GCS batch exports, Hightouch's File destinations write CSV or JSON exports on a configurable schedule, replacing AEP's Destinations catalog with a warehouse-centric activation layer.
Capability: Reverse-ETL (CDW-to-Destination Sync)
Task-level sources
- technical-training/module6/index.md
- technical-training/module6/ex2.md
- technical-training/module6/ex4.md
How is this implementation?
Sign-in-gated. Tomorrow morning's curriculum-ingestor consumes your feedback: "Inaccurate" queues the task for re-review, "needs update" queues it for a refresh, and "one vendor panel is wrong" re-drafts just that panel.