You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update: It seems the behavior is for user_alias to take priority over external_id. If this is intended, it should be more clear in the docs. Currently it says the brazeAliasName is "optional" which sounds like an additional nice-to-have field and not a replacement of the original.
Closing this because we are reverting to not setting user_alias.
Describe the bug
The iOS SDK docs supports sending user_alias fields to Braze:
https://www.revenuecat.com/docs/integrations/third-party-integrations/braze
However, if we set this value, the external_id gets dropped from the payload when sending to Braze and then Braze does not recognize the event.
The following event sends to Braze from RevenueCat, but Braze fails to recognize it on their end:
The following event is successfully recognized by Braze, but doesn't have a user_alias set:
Per Braze docs, the example looks like we should be sending both values, external_id always and user_alias if it is available.
https://www.braze.com/docs/api/objects_filters/user_alias_object/#example
Are you able to update this or is the recommendation to not use user_alias?
The text was updated successfully, but these errors were encountered: