Skip to main content

What this is

A Braze Currents source carries data from Braze into Zeotap CDP. Braze Currents is Braze’s own continuous export of your engagement events; pointing it at Zeotap CDP means the activity Braze records is unified with the customer data you already hold, rather than staying inside Braze. Using Braze Currents as a data source in Zeotap CDP, you map your customer data to Zeotap’s endpoint through batched JSON payloads. To send data the other way, out of Zeotap CDP to Braze, see Braze for activating an audience into Braze, and Braze Integration for real-time orchestration from Journeys. Braze Currents sits in the Customer Engagement Channels source category, alongside the other engagement platforms listed under Customer Engagement Channels. With engagement events flowing in, you can build targeted customer segments, personalise content recommendations and optimise advertising strategies against behaviour that originated in Braze.

Supported identifiers and events

The source integrations catalogue lists Braze Currents under Customer Engagement Channels, carrying Customer Data (CE) only. Identifiers. Every Braze Currents table you sync to the source must carry at least one identifier — for example an email address, a cellphone number, a cookie or an ADID. Events. The source covers two families of Braze events: Braze source — attributes supported has the complete list. You choose which of these Braze sends when you configure the export on the Braze side. There is no limit on the number of columns ingested into Zeotap CDP — you can map them to the Zeotap catalogue or add custom fields.

Prerequisites

  • A Braze account with access to Partner Integrations → Data Export, where the Currents export is created.
  • Access to the Sources application under Integrate in Zeotap CDP.
  • A country on every record. Records must be tied to a country for a data collection to be created. The supported standard objects contain country columns, so fill the country column with valid values — otherwise the country has to be hard coded. Use alpha ISO 3 country codes.
  • Data in the right region. Make sure the data you ingest belongs to the correct region for the table it comes from, so that data privacy and compliance requirements are met. The source form asks you to select a Region when you create the source.
Speak to your customer success manager if you want a Braze Currents source created for your tenant.

Set up the Braze Currents source

Setting the integration up is two steps. First create the source in Zeotap CDP — on successful creation it generates an API URL and a write_key on the source’s IMPLEMENTATION DETAILS tab. The API URL establishes the connection between Braze Currents and Zeotap CDP, and the write_key is what lets Braze ingest data into that source. See Create a Braze Currents source. Then create a Custom Currents Export in Braze pointed at that API URL. See Implement a Braze Currents source.

Verify the source is receiving data

Find the source on the source listing page. A newly created source stays at status Created until it receives anything; once data starts flowing it moves to Integrated, and you can inspect the incoming records on the source’s PREVIEW DATA tab — Components of the Preview Data tab explains what each field means. The source reaches Mapped once at least one data collection exists on top of it, built against the common taxonomy; see Map the catalogue.

Troubleshoot the Braze Currents source

The source is still at Created and no records have arrived. Braze only starts sending once you click Launch Current. Check that the Endpoint and Bearer Token in the Braze export match the API URL and write_key shown on the source’s IMPLEMENTATION DETAILS tab. Country and city are missing from the ingested records. The country and city columns are blacklisted for ingestion, because the country and city are derived automatically from the user’s IP address. Blacklisted fields for data ingestion has the complete list. Some records failed to ingest. An alert icon appears beside the source on the listing page if any erroneous record was ingested in the last 90 days, and it stays there until the errors are fixed. Hover over the TOTAL RECORDS INGESTED count to see the ingested-versus-failed split and the ingestion efficiency. Components of the source listing page explains the columns and the source report. Data stopped arriving after the source was paused. Pausing data collection invalidates the write key on the source page, which stops data collection. Resume data collection from the ACTIONS menu on the source listing page.

Next steps

Last modified on November 17, 2026