What this is
Real-time integrations in Zeotap CDP deliver activation data to a destination platform through the Journeys application. Each integration is configured once as a Destination — with the credentials and mapping the downstream platform requires — and then attached to a workflow through the Send to Destinations node so records flow as users move through the journey. Zeotap CDP supports real-time destinations across email and marketing automation (Adobe Campaign, Cleverpush), mobile engagement (Airship, Batch), and e-commerce (Channable), among others. This page covers what a real-time destination is, what you need before you configure one, the shared configuration pattern every real-time destination follows, and how to verify delivery is live.Prerequisites
Before you configure a real-time destination, ensure you have:
- An active account on the downstream platform with the credentials that integration requires (API key, access token, workspace/company/channel identifiers, or cloud-storage bucket details — the exact set depends on the destination).
- A Journeys workflow, or the ability to create one, in which the destination will be attached to a Send to Destinations node. See Create a Workflow.
- The identifiers and attributes you plan to send already declared on the downstream platform where that platform requires pre-registration. For example, Cleverpush attributes must exist on the channel before Zeotap CDP maps to them.
Configure a real-time destination
Every real-time destination follows the same configuration flow in Zeotap CDP, with per-destination fields for credentials and mapping.- In the Destinations application, start a new destination. Search for the destination by name and enter a name for it in your workspace.
- Enter the credentials the destination requires. The exact fields differ by platform — Airship uses an Access Token and X-UA-Appkey with a region; Batch uses a Live API Key and REST API Key; Cleverpush uses a Private API Key and Channel ID; Channable uses an API Key and Company ID; Adobe Campaign uses either S3 or Azure cloud-storage credentials.
- Choose an action and complete the mapping. Under Choose your Action, pick the action the destination exposes — for example, Send Named User to Airship, Batch Symphony, or Send identifiers and attributes to Cleverpush in Realtime. Under Map the Fields, map Zeotap identifiers and attributes to the destination’s fields, using + Add Mapping Field to add custom ones.
- Save the destination. It becomes available in the Destinations list and can be attached to a Journeys workflow.
- In your Journeys workflow, add a Send to Destinations node, select the destination you created, and complete any per-workflow fields — for example, Batch requires an Audience name on the workflow; Channable requires a Project ID. Save the destination on the workflow. To attach more than one destination to the same node, click Add Destinations.
Verify the destination is delivering
- In Journeys, the destination appears attached inside the Send to Destinations node of your workflow, and the workflow is in Published state on the Workflow listing screen.
- On the downstream platform, records begin appearing where that platform surfaces incoming data — for example, Batch surfaces user traits and events under Settings → Custom data in its dashboard.
Why records are rejected
Real-time destinations reject records when the mapping or credentials do not match what the downstream platform expects. The conditions Zeotap has documented across the supported real-time destinations are:
For Batch specifically, event attribute names must match the following character set or Batch rejects the record:
When to contact support
Contact your Zeotap customer success representative if:- You configured the destination and mapping per the steps above and the downstream platform shows no incoming records after the workflow is published.
- The downstream platform surfaces an error that is not covered by the table above and is not documented on the destination-specific integration page.
FAQ
What is the difference between a real-time integration and a batch integration?
What is the difference between a real-time integration and a batch integration?
A real-time integration delivers records to the destination platform as they flow through a Journeys workflow, using the Send to Destinations node. A batch integration delivers records in scheduled files or API calls. Airship and Cleverpush, among other platforms, offer both a batch and a real-time integration; pick the mode that matches how you want the downstream platform to receive data.
Can I attach more than one destination to a Journeys workflow?
Can I attach more than one destination to a Journeys workflow?
Yes. In the Send to Destinations node, click Add Destinations to attach additional destinations to the same workflow.
Where do I find the full list of destinations Zeotap CDP supports?
Where do I find the full list of destinations Zeotap CDP supports?
See the Integrations Master List for the complete catalog of sources and destinations.
Next steps
- Explore the Integrations Master List → to see every source and destination Zeotap CDP supports.
- Explore Source Integrations (Batch + Real-Time) → to configure the source side of your data flow.
- Explore the Adobe Campaign Real-Time Integration → for a worked end-to-end example of a cloud-storage-backed real-time destination.
- Explore the Airship Real-Time Integration → for a worked end-to-end example of an API-backed real-time destination with identifier priority.
- Explore the Batch Real-Time Integration → for a worked example including the attribute naming rule enforced by Batch.