Disclaimer: long post & lots of questions, so feel free to respond partially.
Hi all,
I lead CRM at an EU-based consumer app. We recently launched a consent banner in our apps. Our legal team’s position is that the Braze SDK must sit behind analytics/marketing consent. The reasoning is that the SDK collects session and device data and we use Braze for behavioural targeting, so the transactional use doesn’t make it strictly necessary.
Around 65% of users accept. For the rest, the SDK never initialises (we’re using delayed initialization). That creates a few problems I’d love to hear how others have solved:
1. Transactional push for non-consenters. Without the SDK, Braze never gets a push token, so we can’t send service pushes like friend activity or account notifications (our app has a pretty strong social side, so sending pushes about friend's activity is considered transactional). Our current plan is:
- the app fetches the token natively
- our backend registers it via
/users/track with push_tokens - the pushes stay as API-triggered campaigns in Braze
Q: Is anyone running token import as an ongoing production flow rather than a one-off migration? Any gotchas, especially with rendering Braze payloads on Android without the SDK, or with deep links and open tracking? Or did you move transactional push out of Braze entirely?
2. Separating marketing from transactional. Push subscription state covers all push. Q: How do you make sure non-consenters only ever get service messages (assuming they're also opted-in to push)? A custom consent attribute, a global exclusion segment, a separate workspace, or something else?
3. Targeting and segmentation for non-consenters. Q: Are you feeding Braze with server-side attributes and events (e.g. via your CDP or the REST API) for users who declined, and has your legal team accepted that? Does cookie consent affect your email segmentation at all, or only SDK-driven channels?
4. In-app messages and Content Cards. Q: If you use them, have you accepted they’re consenter-only? Or have you built native, backend-driven alternatives for must-see messages?
5. Analytics and reporting. Q: How are you handling the reporting gap, for example warehouse-based KPIs, server-side events to your analytics tool, or treating consenters as a sample?
Even a quick “here’s what we did and what legal accepted” would be really helpful. Happy to share back what we land on.
Thanks!