engineer-extension-integrations

Braze Connected Content pulls survey responses by making deep-link calls to partner platforms, returning user attributes and event metadata for personalization. You must validate Connected Content responses and ensure user identity is threaded correctly to avoid misattributed profiles.

Mapping partner webhook callbacks to Braze custom events requires directing payloads to the Braze /users/track endpoint. You must ensure the user's external_id or email is included and map completion events to custom events while storing returned metadata as custom attributes.

Third-party SDK callback events fail to trigger Braze campaigns due to SDK initialization race conditions or missing user identity. Confirm the SDK initialization order and validate that external_id or email is included in the callback payload before it reaches Braze.

You can pass rewards and gamification data to Braze user profiles via webhook /users/track flows. Validate attribute names and event properties during configuration to ensure the partner data syncs reliably and triggers downstream campaigns correctly.

An external_id or email is required to sync learning platform completion events into Braze reliably. Including user identity ensures the mapped custom events and custom attributes attach to the correct Braze profile.

Troubleshoot lost events from landing page integrations by checking for external_id or email threading, SDK initialization race conditions, and attribute name mismatches. Validate the webhook or Connected Content response handling to prevent data sync failures.