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:
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
Hey JordanW​
I think the two things to consider here are that the payload you send will only trigger the users you add to it, and they need to match the filters on the canvas. You can know pretty quickly who it went to if the response says "message": "success" because it will only be users that exactly match the payload and the canvas. I actually think if one of them doesn't the whole trigger fails... can't 100% confirm that.
The other side of this is that if you are triggering a large number of users, maybe in the thousands or millions, I personally wouldn't want the entire list of Braze IDs coming back in the response and blowing up my console. 🤯😄
