DTM to Launch Property Migrated but some of rules custom code condition not meets | Community
Skip to main content
M
Madhus
Level 2
June 30, 2020
Solved

DTM to Launch Property Migrated but some of rules custom code condition not meets

  • June 30, 2020
  • 5 replies
  • 2049 views

Hi We recently migrated DTM to Launch out of 122 rule arround 100 rules are migrated but some of the rules which had some custom code and data element validation are not firing. those rules are still working in Prod site with DTM but not working in dev environment 

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 Alexis_Cazes_

While it does not answer your questions, we have found during our Adobe Launch migration that the best approach was to do a full audit of the whole tagging content.

Once we audited the implementation we done a full refactor of the tagging content to optimize existing code and remove any content not used anymore.

You will be amazed to find out how much redundant code and poorly written code you have in your web property over time and the migration to Adobe Launch is the perfect opportunity to do some tidying.

5 replies

cserrurier
cserrurier
Level 2
June 30, 2020

Hello,

When switching from DTM to Launch, some functions are no longer supported (in particular the reading of cookies). For rules that no longer work, I advise you to use the "Launch Switch" add-on with the Console to determine if there are errors in your code.
If you have already identified rules that don't work since the migration, you can test the scripts directly in the Console to determine the nature of the problem.

Finally, if the script is not the cause, it may be one of the triggering rules. If this one is based on a dataElement, you may encounter the same kind of problem as mentioned above.

Best regards

    cserrurier
    cserrurier
    Level 2
    June 30, 2020
    @madhus.
    Andrey_Osadchuk
    Andrey_Osadchuk
    Level 10
    July 1, 2020

    Could you share the library URL and a rule name that is not working after the transition?

      Alexis_Cazes_
      Alexis_Cazes_Accepted solution
      Level 10
      July 6, 2020

      While it does not answer your questions, we have found during our Adobe Launch migration that the best approach was to do a full audit of the whole tagging content.

      Once we audited the implementation we done a full refactor of the tagging content to optimize existing code and remove any content not used anymore.

      You will be amazed to find out how much redundant code and poorly written code you have in your web property over time and the migration to Adobe Launch is the perfect opportunity to do some tidying.

        jantzen_b
        Adobe Employee
        jantzen_bAdobe Employee
        Adobe Employee
        September 14, 2020

        Do the rules that do not work contain any references to unsupported objects in the _satellite library?

        https://docs.adobe.com/content/help/en/launch/using/reference/client-side-info/launch-object-reference.html

         

        jantzen_b
        Adobe Employee
        jantzen_bAdobe Employee
        Adobe Employee
        September 24, 2020
        Do any of the answers below answer your initial question? If so, can you select one of them as the correct answer? If none of the answers already provided answer your question, can you provide additional information to better help the community solve your question?
        Terms & ConditionsAccessibility statement

        Loading footer...