Real-time
Two-way sync
Changes in Braze or Reltio instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Database
Braze to Reltio integration — real-time, two-way sync
Keep Braze and Reltio in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Braze and Reltio
Mirror Braze's data into Reltio so your own code can read and write it like any other table, with changes flowing both ways in seconds.
Engineers integrate with tools like Braze through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in Reltio.
Stacksync mirrors Purchases, Segments, Campaigns, Canvases from Braze into Data Change Requests (DCR), Reference Data (RDM), Entities, Relations in Reltio and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Braze, so the tool and the database never disagree.
Common use cases
- 01 Keep subscription and consent states consistent between Braze subscription groups and the CRM or CDP of record.
- 02 Export campaign and Canvas engagement data into a warehouse for cross-channel reporting.
- 03 Sync Relations (affiliations, hierarchies, households) between Reltio and a CRM or graph so account and affiliation structures stay aligned.
- 04 Feed Interactions (transactions, visits, events) into Reltio to enrich entity profiles, then read them back for 360-degree reporting.
Common sync patterns
One integration pattern for the whole stack
Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
Read Braze with a query
Records from Braze are ordinary rows in Reltio; join them, index them, and use them in application logic without touching the vendor API.
Automate Braze from your codebase
Write to the synced tables in Reltio and Stacksync propagates the change into Braze, replacing custom integration code.
What you can sync between Braze and Reltio
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Braze objects | Reltio objects | How this pairing syncs | |
|---|---|---|---|
| Users The central profile object, identified by external ID, Braze ID, or user aliases; the main sync target. | Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. | Users is specific to Braze and Interactions to Reltio — each maps to any object or custom field on the other side. | |
| Custom Attributes Profile fields written from CRMs, warehouses, and product databases to drive personalization. | Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. | Custom Attributes is specific to Braze and Matches (Potential Matches) to Reltio — each maps to any object or custom field on the other side. | |
| Custom Events Behavioral events pushed into Braze to trigger campaigns and Canvases. | Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. | Custom Events is specific to Braze and Activity Log to Reltio — each maps to any object or custom field on the other side. | |
| Purchases Transaction records logged against profiles for revenue-based targeting. | Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. | Purchases is specific to Braze and Data Change Requests (DCR) to Reltio — each maps to any object or custom field on the other side. | |
| Segments Audience definitions read for membership export and campaign targeting. | Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. | Segments is specific to Braze and Reference Data (RDM) to Reltio — each maps to any object or custom field on the other side. | |
| Campaigns Message sends whose metadata and analytics are read for reporting. | Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. | Campaigns is specific to Braze and Entities to Reltio — each maps to any object or custom field on the other side. |
How changes propagate between Braze and Reltio
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Braze Reltio Interval-based propagation
DetectionStacksync polls Braze for changes on an incremental schedule, reading only records changed since the previous pass. Braze Currents streams engagement events outward.
DeliveryEach detected change is written to Reltio through its API, with automatic retries and rate-limit backoff.
Reltio Braze Interval-based propagation
DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.
DeliveryEach detected change is written to Braze through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Braze: Endpoints have per-endpoint rate limits documented by Braze; batch endpoints accept multiple users per request.
- Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with Braze ⇄ Reltio
Connect Braze and Reltio for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Braze–Reltio connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Braze or Reltio data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Braze or Reltio record.
Observability
Monitoring
Track your Braze ⇄ Reltio sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Braze and Reltio.
How the Braze and Reltio connectors work
Braze
- Integration surface
- REST API
- Authentication
- REST API keys scoped to specific endpoints, issued per workspace
- Change detection
- Braze Currents streams engagement events outward; profile reads otherwise rely on export endpoints and polling
- Capabilities
- read · write
- Rate limits
- Endpoints have per-endpoint rate limits documented by Braze; batch endpoints accept multiple users per request
Reltio
- Integration surface
- Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
- Authentication
- OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
- Change detection
- Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
- Capabilities
- read · write
- Rate limits
- Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
How it works
How to connect Braze to Reltio — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Braze and Reltio with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Braze
connected
Reltio
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Braze and Reltio objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Braze ⇄ ReltioCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Braze ReltioCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Braze and Reltio integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Braze and Reltio: authenticate both systems, choose the objects to sync (such as Braze's Users and Custom Attributes), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Braze and Reltio records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Braze and Reltio connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Braze–Reltio integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Braze and Reltio. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Braze: Braze Currents streams engagement events outward; profile reads otherwise rely on export endpoints and polling. On Reltio: Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Braze side: Purchases, Segments, Campaigns, Canvases, plus custom fields where Braze exposes them. On the Reltio side: Data Change Requests (DCR), Reference Data (RDM), Entities, Relations. Stacksync auto-detects both schemas and converts types between the two systems.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 424 integrations available for Braze and Reltio.
Popular · 6 of 424
-
Braze ⇄ SAP Hana - Braze ⇄ Jdbc
-
Braze ⇄ Render Postgres -
Braze ⇄ PostgreSQL - Reltio ⇄ ServiceNow
-
Reltio ⇄ Slack
No integrations match .
