Hi Ashleedolan ! Tag-teaming with my partner Peyton on this one :)
You are absolutely correct about the User Update approach. Unfortunately, it's not possible to split users based on the Canvas Entry Property (the Braze community is looking forward to this becoming a feature one day), so the solution would be to log the Entry Property as a Custom Attribute, then you can split the users using the Audience Path afterwards.
We actually have a Youtube video on how to do exactly this: check it out here!
It also sounds like you'll be using some Liquid to create conditional logic based on what your GET request returns from your BE. The Connected Content approach is correct here. Also happy to take a look if you have some more details/examples!
Thanks AllanHeoFNM ! Since the event property is being sent to Amplitude-->Braze as eventValues.community_id and the BE endpoint is referencing {communityId} - will there be a discrepancy in mapping the values if they don't match?
Since I have not added the user update step yet- I did attempt to alter the value with liquid in the webhook itself, but that did not work as I expected it would not.
My guess is that as long as you're referencing using the correct field name when requesting your BE, that should work fine? So if you're requesting from your BE, sounds like you should look for communityId.
Do you mind sharing your Liquid code here?
Disregard - I got it to work 😅
{{event_properties.${eventValues.community_id}}
perfect!! glad to hear it!
