Braze

Rekomi's Braze integration runs a 2-call sequence:

1. POST /users/track upserts the user profile with an email-identified attributes object (email, first_name, last_name, rekomi_tags). Rekomi deliberately does not send an external_id: an external_id Braze doesn't know creates a brand-new profile, so identifying by email is what updates your existing profiles instead of minting duplicates.
2. POST /v2/subscription/status/set enrolls the user in the chosen subscription group with subscription_state: "subscribed".

Connecting

1. Braze > Settings > API Keys. Create a REST API key with the users.track and subscription.status.set permissions (used for syncing), plus email.hard_bounces (used only by Rekomi's connection test).
2. Find your cluster's REST endpoint URL in Braze (e.g. https://rest.iad-01.braze.com).
3. In Rekomi, Integrations > Braze, paste both, click Connect.
4. Braze has no list enumeration, so the integration page shows a manual Audience/Group ID input instead of a list picker; paste your Subscription Group ID there.

Tags

Braze has no first-class tag primitive. Rekomi sends tags as a rekomi_tags array attribute, segment in Braze with rekomi_tags includes "X".

Referred customers and leads (optional)

Turn on Sync referred customers and leads on the integration page and every sale or lead Rekomi attributes to an affiliate is written to Braze as well, matched on email so existing contacts are updated, not duplicated. Each one carries:

• custom attributes rekomi_referral_link, rekomi_campaign, rekomi_referring_affiliate, rekomi_referring_affiliate_code, rekomi_last_event, rekomi_last_sale_amount on the user profile
• rekomi_tags array gains Rekomi customer or Rekomi lead (added, never replaced)
• Affiliates synced by the section above also get Rekomi referral link, Rekomi campaign and Rekomi affiliate status in the same fields, so you can merge a partner's link into your emails.

Refunded, denied and fraud-quarantined conversions are never pushed, and imported historical conversions are skipped. It is off by default.

Provider notes

• Bearer auth with REST API key.
• Per-cluster endpoint with strict SSRF allowlist: rest.{iad|us|au|id|jp|kr}-NN.braze.com and rest.fra-NN.braze.eu (Indonesia, Japan, and Korea clusters included).
• Connection test probes GET /email/hard_bounces?limit=1 (hence the extra key permission; Braze has no read endpoint scoped to the write permissions sync uses).
• /users/track is async server-side but reliably durable; Rekomi treats 2xx as success and logs any non-fatal errors entries the 2xx body carries.
• 429 honors Retry-After.
• Disconnect deletes the integration row.

---

See the braze integration overview on the marketing site for use-cases, persona fit, and unique automation patterns.