Hi all,
Looking for input from other EU customers — especially those operating under strict ePrivacy interpretations — on how you architect Content Cards and In-App Messages when Braze is classified as Marketing in your CMP.
Our setup
- Braze Web SDK loaded via GTM, initialized only after Usercentrics consent
- Braze classified as "Marketing" in the CMP because the SDK tracks and personalizes via External ID
- Our vertical has a strong need for service/transactional in-app communication (booking confirmations, price alerts, status updates) alongside our marketing campaigns
The conflict
Product wants Content Cards on the homescreen and transactional In-App Messages to "always show" — including for users who haven't given marketing consent. But:
disableSDK() takes all network requests offline, so no cards can be fetched while disablednoCookies: true doesn't help — SDK still writes to localStorage, still sends device-identified requests, so legal site still requires consent- Braze's own docs confirm: delaying initialization until consent means Banners and Content Cards won't display until then
- A "cookie split" (Functional vs Marketing within one SDK instance) doesn't work I guess— the SDK is one instance with one behavior
Questions
- For transactional/service messages: are you building these outside Braze, or have you found a way to keep them in Braze with a separate legal basis?
- Any experience with server-side rendering Braze Content via the Catalog/Content Blocks API to bypass the SDK entirely? Worth it, or did you end up just using a CMS?
