Enable tracking for URL's passed as targetData | Adobe Higher Education
Skip to main content
D
dboat
Level 2
February 6, 2018

Enable tracking for URL's passed as targetData

  • February 6, 2018
  • 1 답변
  • 8314 조회

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.

이 주제는 답변이 닫혔습니다.

1 답변

Amit_Kumar
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

    D
    dboat작성자
    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.

    Amit_Kumar
    Amit_Kumar
    Level 10
    February 7, 2018

    Thanks Amit I appreciate the time you're taking. I tried as you suggested and created a view that simply returns <%= targetData.url %> with an @include instruction in the content form, however the tracking information was not automatically appended.

    You mentioned the mirror page view, this view handles the appending of the tracking information, were you suggestion my new view should do the same?

    Thanks.


    Hi,

    I just did a quick test, and it is working fine for me

    Hope this helps!

    Amit

    약관 및 조건Accessibility statement

    Loading footer...