Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

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

Madhus
Level 2
Level 2

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 

1 Accepted Solution
AlexisCazes
Correct answer by
Community Advisor
Community Advisor

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.

View solution in original post

7 Replies
camilles8371268
Level 1
Level 1

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

Madhus
Level 2
Level 2
Hi @camilles8371268 Thanks for solution but custom code in which some certian code was written are working perfect still in DTM (as production site still having DTM code) but its not working in Launch also some of extra variables are firing which are not part of rule
Andrey_Osadchuk
Community Advisor
Community Advisor

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

AlexisCazes
Correct answer by
Community Advisor
Community Advisor

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.

View solution in original post

jantzen_belliston-Adobe
Community Manager
Community Manager

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-referen...

 

jantzen_belliston-Adobe
Community Manager
Community Manager
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?