--- title: "Sync Amplitude cohorts to Braze" canonical_url: https://ampl.webclat.com/guides/sync-amplitude-cohorts-to-braze description: "How to send a behavioral cohort built in Amplitude to Braze as a live audience for messaging - the destination setup, sync mechanics, and how to confirm members actually landed." source: Webclat | Amplitude Solutions (official Amplitude partner, independent consultancy) --- # Sync Amplitude cohorts to Braze **In short:** Amplitude's Braze cohort sync sends the membership list of any behavioral cohort you build in Amplitude to Braze as a synced segment, so a lifecycle team can message people based on real product behavior instead of a static import. The sync runs on an interval you configure, so a cohort defined once ("activated but hasn't hit core action in 14 days") keeps updating in Braze without anyone re-exporting a CSV. ## What it is A cohort in Amplitude is a saved group of users or devices defined by behavioral and property criteria - did an action, in a time window, with optional frequency and property filters. Cohort sync to Braze is a destination integration that takes that cohort's current membership and pushes it into Braze as an audience Braze can target with a Canvas or campaign. The sync is one-directional (Amplitude to Braze) and periodic: Amplitude re-evaluates the cohort's membership on its own schedule and reconciles the Braze-side audience to match, adding newly-qualifying users and removing users who no longer meet the definition. It is not a one-time export - that is the entire value over a manual CSV handoff. ## When you need it - A lifecycle or CRM team wants to message users based on behavior Amplitude already tracks - a feature adopted, a milestone hit, a drop-off pattern - without engineering building a second pipe from the product database into Braze. - The trigger condition is genuinely behavioral (a sequence, a frequency, a time-since-last-action) rather than a simple user property Braze's own event stream could already capture - that's the case cohort sync earns its place over a direct Braze SDK event. - You need the audience to stay current automatically. A marketing team exporting Amplitude cohort CSVs by hand on a schedule is exactly the workflow this integration exists to replace. ## Implementation, done properly 1. In Amplitude, build and save the behavioral cohort first, on its own, and check its membership count looks sane before wiring up any destination - debugging a cohort definition through a second system's UI is much harder than debugging it in Amplitude's own cohort builder. 2. In Amplitude's data destinations settings, add Braze as a destination and authenticate it with a Braze REST API key scoped for user data / subscription group access (the exact scope name and plan-tier gating for cohort sync varies by Amplitude plan - verify against current Amplitude docs before assuming it's available on your tier). 3. Attach the destination to the specific cohort(s) you want synced, and set the sync cadence. Pick a cadence that matches how time-sensitive the message is - a same-day onboarding nudge needs a tighter interval than a monthly win-back list. 4. Confirm the user identifier Amplitude is matching on (email, external user ID, or a Braze alias) actually exists as a stable, populated field on both sides before the first sync - a mismatched identifier is the single most common reason a cohort sync shows Amplitude-side success with zero Braze-side membership growth. 5. Build the Braze Canvas or campaign against the synced segment as you would any other Braze audience, and stage it behind a small test group before the full send. ## How to verify it worked 1. In Amplitude's destination/sync log for the cohort, confirm the most recent sync run completed successfully and check the reported member count against what the cohort shows natively in Amplitude's cohort builder. 2. In Braze, open the synced segment and confirm its size is in the same range as Amplitude's reported count - a large, persistent gap almost always traces back to the identifier-matching step, not the sync mechanism itself. 3. Add yourself (or a test account) to the cohort's defining behavior, wait one full sync interval, and confirm you appear in the Braze segment - this is the only way to confirm the sync is live rather than a one-time snapshot from setup day. 4. Spot-check a user who should have dropped out of the cohort (because they stopped qualifying) and confirm they're removed from the Braze segment on the next sync, not just added-but-never-removed - a sync that only adds and never prunes will quietly over-target over time. ## FAQ ### Does this replace sending events to Braze directly from our app? No - direct event streaming (or a dedicated events destination) is how Braze learns about individual actions in near-real time; cohort sync is for targeting a defined, evaluated GROUP based on a behavioral pattern Amplitude has already computed. Most mature setups use both: events for triggered, in-the-moment messages, cohort sync for segment-based campaigns. ### What happens to a Braze user who Amplitude can't match to an identifier? They simply don't appear in the synced segment - Amplitude can't push a cohort member into Braze without a matching identity key on both sides. This is why identity resolution (getting anonymous and identified users merged correctly in Amplitude) has to be solid before cohort sync is worth setting up at all. Related: [Building behavioral cohorts in Amplitude](https://ampl.webclat.com/guides/building-behavioral-cohorts-in-amplitude), [Reconciling Amplitude identities](https://ampl.webclat.com/qa/reconcile-amplitude-branch-segment-identities), [Use case: cohorts your lifecycle emails can use](https://ampl.webclat.com/use-cases/cohorts-your-lifecycle-emails-can-use)