Source connector

Braze connector

Braze integration for databases, warehouses and BI tools

Cross-channel customer engagement platform. Datrise captures Braze entities such as users, campaigns, canvases, message events, segments and custom attributes, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Braze REST API + Currents authenticates with API key, incremental runs key on last_edit.time[gt], and Braze caps calls at Default 250,000 requests/hour per workspace shared across ~40 endpoints, with endpoint-specific overrides such as `/users/track` bursting to 3,000 requests/3 seconds, `/users/delete`/`/users/alias/new`/`/users/identify`/`/users/merge` sharing 20,000/minute, and `/events/list`/`/purchases/product_list` sharing 1,000/hour.

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `braze_users`) with a schema derived from the Braze API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Braze pipeline page, and join the waitlist to get the Braze connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Braze data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
users	braze_users	Upsert by primary key, incremental on updated-at
campaigns	braze_campaigns	Upsert by primary key, incremental on updated-at
canvases	braze_canvases	Upsert by primary key, incremental on updated-at
message events	braze_message_events	Append-only, incremental by timestamp
segments	braze_segments	Upsert by primary key, incremental on updated-at
custom attributes	braze_custom_attributes	Upsert by primary key, incremental on updated-at

Braze API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Braze REST API + Currents
Authentication	API key — Requests carry a workspace-scoped REST API key as a Bearer token (`Authorization: Bearer YOUR_REST_API_KEY`), with per-key endpoint permissions and optional IP allowlisting.
Pagination	page — Most export/list endpoints use an integer `page` parameter starting at 0, with a fixed page size per endpoint (e.g. 100 for `/campaigns/list`); some endpoints instead expose a cursor field documented per-endpoint.
Rate limit	Default 250,000 requests/hour per workspace shared across ~40 endpoints, with endpoint-specific overrides such as `/users/track` bursting to 3,000 requests/3 seconds, `/users/delete`/`/users/alias/new`/`/users/identify`/`/users/merge` sharing 20,000/minute, and `/events/list`/`/purchases/product_list` sharing 1,000/hour.
Incremental cursor	last_edit.time[gt] — Endpoints like `/campaigns/list` accept a `last_edit.time[gt]` filter for entity metadata, but user/event-level incremental extraction is normally done through Currents rather than polling.
Webhooks	No
Bulk export	Yes — Currents (streaming export of engagement events as Avro files to S3/Azure Blob/etc.)
Deletes detectable	No

Official API reference

What bites when replicating Braze

`/users/export/ids` was cut from 2,500 requests/minute to 250 requests/minute for any workspace onboarded after August 22, 2024, so the same connector code can hit throttling on new accounts that worked fine on older ones.
Currents delivers events with at-least-once semantics and can write duplicates when its internal queue reprocesses a batch, so consumers must deduplicate on the event's `id` field rather than assume one write per event.
Currents flushes to storage on whichever comes first: roughly every 5 minutes or after 15,000 events accumulate, which means near-real-time but not strictly ordered delivery across files.
There is no Braze webhook or deletes feed for user/event data; Currents only streams forward-going engagement events, so detecting deleted user profiles requires a full re-export and diff against the prior snapshot.

Compare this against every other documented API

Popular destinations for Braze

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Braze connector FAQ

What Braze data does the connector extract?: 6 objects: users, campaigns, canvases, message events, segments and custom attributes. Each lands in its own table with types preserved; history-style objects (1: message events) load as append-only streams.
Is the Braze integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Braze data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Braze → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Braze pipeline with guided onboarding

Join the waitlist to get priority access for Braze integrations with guided setup, schema-aware mapping, and production-grade incremental sync.