Non-User-Specific Custom Events?

Hey there abenton! You find a solution?  I'm thinking 2 options... both of which are backend/data engineering heavy:
1) Use your code to make an API call that sends ONLY to your segment - maybe resource intense
2) Cloud Data ingestion - Delay prone

1 - We have several messages that are "triggered from the code". Our engineering team builds in logic that will make the API call triggering a message from our backend.  We make these calls real time for certain transaction messages, or based on different algo. type criteria (e.g. 14 days after last event, to this audience). I would think with engineering, you could set it up like this. - IF event occurs - make API call... -

2 - Use CDI (Cloud Data ingestion) to create/update a custom attribute which is the trigger for the message - you set entry criteria as ACTION - When custom attribute is any new value - CDI_attribute. We use a CDI sync from Snowflake that creates/updates an engagement attributes which let's us know which users are active.
CAUTION - I don't know if this will work realtime. We only update at 9am. If you need an immediate trigger - this probably won't be so precise. all depends on your infrastructure.

3) I am looking into how you might use a Webhook to trigger the subsequent canvas/send - but doesn't seem promising. I think at a minimum you'd need to create a user that represents your custom event and then have some sort of forloop that cycles through each userID in the segment (triggering the canvas for each)... I may follow up... this is probably not gonna work.

Happy to clarify! sorry for the lengthy response 😅
-Joseph

I agree with all the other things mentioned, but if you really want to do this in Braze yourself, you could:

Trigger an event/attribute update to a 'fake' user - on that exists in Braze, but doesn't correspond to an actual user.

That will cause, for that user, a webhook campaign or a canvas with a webhook step in it...

... that triggers a campaign/canvas for the actual audience via the Braze API.

I'm not convinced this is the right way of solving your actual problem, but it could be made to work and would work reasonably well.

I'd be really interested in working on this with you if you'd like to reach out.

Hi abenton

I just want to clarify I am reading this correctly. Essentially, you want any user to be able to trigger a certain event on a page but when the event occurs it messages an entire segment, not just that user.

i.e. I go on your page and click a product and as a result, it sends a push to all the users in a certain segment, not just me.

Hi abenton , hope all is well! FYI, this is the exact use case for API-Triggered Campaigns where the message is sent based on logic/trigger that occurs from your backend, not based on the user's actions. You'll need some Engineering resources no matter what, although we can always try to take some effort off of their plates by building the API-triggered Campaigns/Canvases, maybe creating a webhook to capture the data, etc.