After migration to Launch, Target property token is no longer automatically detected within Target VEC | Community
Skip to main content
J
Joe_Y_1
Level 2
January 24, 2020
Solved

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

  • January 24, 2020
  • 1 reply
  • 3757 views

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.
    Best answer by Gaurav_Singh_02

    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 .

    1 reply

    G
    Adobe Employee
    Gaurav_Singh_02Adobe EmployeeAccepted solution
    Adobe Employee
    February 13, 2020

    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 .

      G
      ganeshbyalebrillio
      Level 3
      June 1, 2021
      How to solve the same issue ..if i am following integrating adobe target through adobe i/o not through launch
      Terms & ConditionsAccessibility statement

      Loading footer...