Braze SDK: Logged Out/In States & Push States
Hey Bonfire! How did your devs configure the Braze SDK behaviour for Logged Out users in cross-device states? There are some concerns at play here and looking to make a call that is future-proof but also not overly complex on handling edge cases. Context: - EU app - Cross-device app and (potentially edge-case) multi-user per device - Team leaning towards not manually updating Push Subscription status to Unsubscribed when users opt-out due to complexity in handling all edge cases and also not wanting to Unsubscribe someone from multiple devices when they only opted-out in one Outstanding question is when a user logs out whether it's best to: 1. Stop the SDK from running altogether to ensure the user is not being tracked by accident while logged out (thinking GDPR/Privacy compliance here); 2. De-register the push token, and re-register later upon new login; 3. Create an anonymous user (which will have the previous push tokens) and later merge the profiles upon new login --> I'm not sure this is possible since the external_id will already be assigned so it's not really anonymous. In short, what is the best practice to ensure that if Logged Out: - No Push Notifications are sent to the device - We can easily recognise and recover the push preference after a re-Login? ... while keeping the config. as simple as possible Thanks!How to tell a recipient's bounce status in an export?
I am using the Braze export API to pull down recently added users, and want to check if any of them are marked as hard bounce, or have already accumulated any soft bounces (and if so, in what time period). Similarly, I'd like to be able to tell if a user has marked as spam. Is there an attribute capturing this information that I'm overlooking? Or is the best/only solution to create segments for those attributes and make multiple requests. Thanks!
Tracking Users' Post Click
Hi Braze Community, I am scratching my head a bit trying to understand how the Braze SDK does not have an out-of-box feature that automatically associates a session with a specific user post email/sms campaign click. From what I am reading, even after having clicked through a campaign, if a user comes in a private browser or is not cookied Braze will not recognize them until they log in or put their email somewhere onsite. This is hugely challenging for us, and I assume others as we want all email/sms traffic post-click automatically identified to help fuel abandonment flows. The only solution that we have found is surfacing the external id in every campaign URL and calling changeuser once they hit the site referencing their external id in the URL to tie their session to the correct profile. Is this truly the only option or am I misinterpreting this workflow? How have others dealt with this issue?
iOS Braze SDK and Content Card Data Questions
Hello there! Quite a newbie here in Braze Bonfire. Hopefully someone knows something about the question I have: We have an iOS mobile app created using Swift and we are in the process of implementing content cards via Braze SDK. What we noticed is Braze SDK didn't have the content card data on our first call to Braze SDK even when I already called the cancellable stated in this documentation. Only when we do further calls to requestRefresh() it is only then we are able to get content card data. Has anyone experienced this before and is there a way to do it in such a way that when you do a first call to SDK and a first call to requestRefresh() will have the content card data ready for fetching? Thanks!Need to export Opted In date. Any ideas?
Hi all We are linking our Braze instance to some internal tooling and it is a non-negotiable requirement that we share the opted in date for each user we pass, so they know how old the opt in is. I can see the date exists inside Braze but it does not look like the API passes this date. Has anyone had a similar problem or know of a workaround? Thanks!Braze User ID in /campaigns/trigger/send API Response
Hey folks 👋 — I’m working on an integration using the /campaigns/trigger/send endpoint and wanted to share something I ran into. Here’s a sample payload I’m sending: { "campaign_id": "d44eaedf-bd07-4a95-881f-3c1662796a96", "recipients": [ { "external_user_id": "{{HASHED_EMAIL_ADDRESS}}", "prioritization": ["unidentified"], "send_to_existing_only": false, "attributes": { "email": "{{EMAIL_ADDRESS}}" } } ] } And here’s the response I’m getting back: { "dispatch_id": "687e7579a602835baed3e4868af9c06e", "message": "success" } Love that it’s working, but… It would be incredibly helpful if the response also included the Braze User ID (braze_id) that the message was sent to. In use cases where we’re sending to partially identified users or passing in attributes dynamically, it’d be really valuable to get confirmation of the user object Braze resolved to. This would help with: Debugging user identity issues Verifying merge behavior when using prioritization Logging and downstream analytics Ensuring consistency across systems (especially when using Braze as source-of-truth for user resolution) Could Braze consider optionally including the braze_id in the response when the user resolution is successful? Curious if anyone else has tackled this — or has a good workaround? Would love to hear your thoughts. Thanks! J
Braze Webhook notifications do not work
Hi, I have several webhook alerts: Scheduled Campaign Finished Sending Scheduled Campaign Sent/Not Sent It stopped working a few days ago. I also have Webhook Errors email notification, but I got nothing. Strangely, apart from the webhook, the email alerts for `Scheduled Campaign Finished Sending` and `Scheduled Campaign Sent/Not Sent` are working. Please let me know if there's a problem. Thank you.
