To add personalization to urls in a email or SMS, you must use double curly brace formatted tags e.g {{ recipient.custom.url }} as opposed to standard JavaScript tags described in this article. Using the tags such as {%= recipient.custom.url %} will generate a unique tracking link and potentially cause errors at send time.

Example:

If the subscriber has a custom field called url in their profile with a value of www.taguchi.com.au, the page exists - e.g. The active page is loading and not returning a 404 not found message, the url personalization they should use is:

http://{{ recipient.custom.url }}

OR

https://{{ recipient.custom.url }}

Any address in subscribers custom field should not contain the scheme of the url. For example:

 `www.taguchi.com.au`

Example of address with the scheme (Do not use!):

`http://www.taguchi.com.au`

Personalized link in a call to action button

In order to include personalized URLs in a call to action button:

1. First, if you haven't already, create the custom field via Settings > Custom Fields. For this example we'll use the field url.
2. Ensure the url in your data does not contain 'https://' or 'http://' e.g. 'www.taguchi.com.au'
3. Upload/pass your data into Taguchi, mapping the relevant column to your custom field.
4. In the content of your email, input the personalisation as provided in above example, into the link field of the button. Take note if the complete url needs to load over 'http' or 'https', as this will need to be considered in the personalisation of the button. For example: https://{{ recipient.custom.url }}
5. Save changes and begin proofing your email.

Troubleshooting personalized url issues

1. The button isn't clickable in a proof or the live send Make sure the personalisation used in the button link starts with 'https://' or 'http://' i.e. https://{{ recipient.custom.url }}. This ensures the template recognises that the personalisation is a link and the button is therefore clickable.

2. The button directs to an error page or the link doesn't load but the personlisation in the button link looks correct, i.e. https://{{ recipient.custom.url }} This could be one of two things:

   1. The value in the custom field on a subscriber's profile contains 'https://' or 'http://' at the start and therefore, it's trying to load the unique url with an additional 'https://' e.g. 'https://https://www.taguchi.com.au'. To resolve the issue, you will need to re-upload/re-pass your data with 'https://' removed from the link. The value in the subscriber's profile should just be www.taguchi.com.au.
   2. If point 1 is not the issue, the domain in the personalized url may need whitelisting in Taguchi. To whitelist the domain, create a new text block in the related email activity and input the domain e.g. https://www.taguchi.com.au of the personalized link as a text link in some copy, save and send a proof. You can remove the additional content once you've tested and the link loads correctly.

Please contact taguchi support if you are still experiencing issues with implementing personalized urls. This feature also needs to be enabled in your template. Please contact taguchi support if you are unsure if its available in your template.