Connector Improvement: [Braze] User Data - Push Notification Object
PlannedHey,
The user table does not currently include all relevant attributes—specifically, push_notification_enabled.
However, when querying the Braze API via the /users/export/ endpoint, we receive a user object that includes a push_tokens sub-object. This attribute is important for our tracking and related metrics and insights.
Could u please let us know if its possible to add this flag to the user table and when can we expecting this to be done ?
"push_tokens":[{"app":str,"platform":str,"token":str,"device_id": str,"notifications_enabled": bool}],
-
Official comment
Hi Obadah,
Luke from the Product team here. Thanks for submitting this request!
I appreciate you taking the time to outline how we can retrieve this data. How would you prefer this to be represented in our connector's schema? Typically, we break an array of objects like this into a child table with a reference to the parent table (USER) to make it easier to query.I've added this request to our team's backlog. I can't provide an accurate timeline right now because we will prioritize this relative to other feature requests based on customer demand. Additional upvotes on this feature from other Fivetran customers will help increase the priority of this specific request.
Cheers,
Luke -
Hi Lucas,
Thanks for getting back to me, and apologies for the delayed response — I was on vacation 🌴
Yes, having a separate table that includes a
user_idreference would be ideal.Would it be possible to prioritize this request? We're currently blocked and unable to proceed with our reporting until this is in place.
Thank you for understanding!Best regards,
Obadah
Please sign in to leave a comment.
Comments
2 comments