Skip to main content
Joe_Y_1
Level 2
Jan 24, 2020 3:01 PM UTC
Solved

After migration to Launch, Target property token is no longer automatically detected within Target VEC

After migrating from DTM to Launch, the Target property token is no longer getting automatically detected within the Target VEC.

 

Within Launch, we are using the latest version of the Adobe Target extension.

 

We have a Page Top rule configured to Load Target then Add at_property to All Mboxes then Fire Global Mbox. We would expect with this setup, that the Target property token would be present at the time that the Target VEC tries to detect it. Has anyone else experienced this issue. Is there something wrong with our Launch rule setup?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Gaurav_Singh_02Accepted solution
    Adobe Employee
    Feb 13, 2020 5:10 PM UTC

    Hi Joe , 

     

    could you just try adding a data element for at_property by following the steps provided and then check . I hope this would fix your problem .

    View in thread

    2 replies

    Adobe Employee
    Gaurav_Singh_02Adobe EmployeeAccepted solution
    Adobe Employee
    Feb 13, 2020 5:10 PM UTC

    Hi Joe , 

     

    could you just try adding a data element for at_property by following the steps provided and then check . I hope this would fix your problem .

    Translate
      ganeshbyalebrillio
      Level 3
      Jun 1, 2021 10:11 AM UTC
      How to solve the same issue ..if i am following integrating adobe target through adobe i/o not through launch
      Translate
      Terms & ConditionsAccessibility statement

      Loading footer...