Enable tracking for URL's passed as targetData | Community
Skip to main content
Level 2
February 6, 2018

Enable tracking for URL's passed as targetData

  • February 6, 2018
  • 1 reply
  • 8303 views

Hello,

When URL's are passed as targetData from the workflow to the content form they are not marked for personalization and no tracking information is added. Is there a way to ensure they are detected and the proper tracking information is appended?

Thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Amit_Kumar
Level 10
February 6, 2018

Hi,

use this documentation for your reference and follow the instruction given there then you will be able to track them.

How to track personalized links in emails

Feel free to reach out to us if you need more information.

Regards,

Amit

dboatAuthor
Level 2
February 6, 2018

Hi Amit,

I did read this documentation and at first it seemed like it would work however I am not understanding the implementation. The URL is passed from the workflow (e.g., targetData.myUrl has a value of 'https://www.mywebsite.com/') and can be unique per recipient however the detection of tracking links happens before the personalization process so these URL's are not appended with the respective tracking information.

I wanted to preprocess this targetData so that the tracking analysis would see these links, however the object isn't available in the @value instructions.

dboatAuthor
Level 2
February 7, 2018

Hi,

You can create a delivery variable i.e myURLVar for this URL, and you can assign your URL value from additional data to this variable in the delivery script.

Use below for url in your delivery and this will work everywhere. you can use your parms like below if you have any.

<a heref="<%@ value object="delivery" xpath="variables/var[@name='myURLVar '']/@stringValue" %>?firstName=<%=recipeint.firstName%>" _label="custom url">my link value </a>

Regards,

Amit


We have a unique-per-recipient URL in the workflow, wouldn't setting it to a value in the delivery would make the URL the same for all recipient's?