Update a user’s preference via a link - not working

  • 11 November 2022
  • 3 replies


Hi, I am trying to use the following variable via a button in an email:

{% preference_link 'customer_type' 'gen_cust' %}

As described here:

When I send a test email and click the button, I am directed to my “update preferences” page, however, the custom property specified is not updated with the specified value 

Both ‘customer_type’ and ‘gen_cust’ are both properties that exist on my manage preference page. What am I doing wrong?


If i use the variable {% update_property_link 'customer_type' 'gen_cust' '' %} in the button URL instead, then the property value on the profile is updated, however, I need the customer to end up on their update preferences page rather than my home page.

What am I doing wrong with the {% preference_link 'customer_type' 'gen_cust' %} variable?

Is there a way to use the {% update_property_link 'customer_type' 'gen_cust' '' %} variable but end up on the customers update preferences page rather than''?




Best answer by Dov 15 November 2022, 15:43

View original

3 replies

Userlevel 7
Badge +61

Hi @hsconline,

Thanks for confirming this with us.

I checked in internally and I noticed you’re in touch with one of our support team members on this issue. I recommend continuing your correspondence with them and they’ll be able to provide you with next steps.

Thanks for being a community member.


Thanks Dov, yes, both my list-specific manage preferences page and my general manage preferences page have the property name and values needed.

Userlevel 7
Badge +61

Hi @hsconline,

Thanks for sharing this with us.

Keep in mind there are two types of manage preferences pages - a list-specific page (for each discrete list) and a general manage preferences page. Can you confirm that you have updated both types of pages to include the property name and value you’re describing? For example, if you’ve added yourself to a list for testing purposes and the list-specific preference page does not contain the property + value set for the custom property, that would prevent this from working.

I hope that’s helpful.