Embedded NPS Survey Via Email

Hi Bonfire!

Lately, I've been hearing a lot of customer requests on how to embed an NPS survey in an email and have the user's responses get logged as a custom attributes. I believe this use case should be doable with Link Aliasing.

I wanted to post here to see if anyone has already tried it and found any pros and cons with this set up. Also, would the custom-attribute-logging campaign be 10 different webhook campaigns, one for each score?

Thank you!

Best,

Allan

Find more posts tagged with

Accepted answers

DRamirez

Hi Allan!
We have an email NPS survey that works exactly like that! So there is a campaign where we have a range of buttons from 0 to 10. We then have an action based canvas based on link alias clicks. In that canvas we let people go through several audience paths (with the filter “clicked specific alias in this campaign”), since braze can only do up to 8 paths during each audience step. So we start with 3 options (promotors, detractors & passives), and then they go through 10 different audience paths for each score type. Each one of them ends with a user update step (it used to be a webhook before the user update feature) where they get a custom attribute linked to their profile.

Pros?

You will see all the results in one canvas
you can make quick calculations for each month by just filtering the date in the canvas

Cons?

It is quite a hassle to set up. As the email has a mobile and desktop view, this means it also has different buttons (2 aliases for each score type) that you have to track each time, so that is a lot of work in the delivery step and all the audience paths
It only looks at the first time somebody clicks in that specific mail, so it could be that somebody made another choice, that will not get registered anymore.

All comments

DRamirez

Pros?

You will see all the results in one canvas
you can make quick calculations for each month by just filtering the date in the canvas

Cons?

It is quite a hassle to set up. As the email has a mobile and desktop view, this means it also has different buttons (2 aliases for each score type) that you have to track each time, so that is a lot of work in the delivery step and all the audience paths
It only looks at the first time somebody clicks in that specific mail, so it could be that somebody made another choice, that will not get registered anymore.

AllanHeoFNM

@DRamirez This is absolutely the perfect answer to what I was looking for. Thank you SO SO SO MUCH for this detailed answer!!

Best,

Allan

amanK

Hey Allan!

Great question -- we've explored this exact setup.

Link Aliasing works well for this use case. The typical approach is to create 11 aliased links in your email (one per score, 0-10), each pointing to a landing page or redirect URL that carries the score as a query parameter (e.g., ?score=7&user_id={{${user_id}}}). When a user clicks their score, Braze logs the click against that alias, and you can use a webhook or Connected Content call triggered by that click to write back to a custom attribute.

On your question about whether you need 10 separate webhook campaigns -- technically yes, if you're triggering webhooks off individual link alias clicks, you'd set up one Action-Based campaign per score value (or use a single campaign with audience filters checking which alias was clicked). Some teams simplify this by routing all 11 links to a single endpoint (your own server or a tool like Elvan) that accepts the score as a parameter and handles the attribute write in one place -- that cuts the campaign count significantly.

A few things worth keeping in mind:

Make sure your link alias names are consistent and clearly labeled (e.g., "nps_score_7") so reporting stays clean.
If you want the follow-up open-text question ("what's the main reason for your score?"), you'll need to handle that on the landing page side, not purely within Braze.
Test click deduplication -- if a user clicks multiple scores (accidental double-click), you'll want logic to only log the first.

Happy to share more on how we've structured the webhook side if that's useful.

Best,
[Your name]