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

Avatar

Avatar
Boost 1
Level 1
Madhus
Level 1

Like

1 like

Total Posts

7 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile

Avatar
Boost 1
Level 1
Madhus
Level 1

Like

1 like

Total Posts

7 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile
Madhus
Level 1

30-06-2020

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 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Contributor
MVP
AlexisCazes
MVP

Likes

187 likes

Total Posts

424 posts

Correct reply

198 solutions
Top badges earned
Contributor
Shape 1
Give Back 10
Give Back 5
Give Back 3
View profile

Avatar
Contributor
MVP
AlexisCazes
MVP

Likes

187 likes

Total Posts

424 posts

Correct reply

198 solutions
Top badges earned
Contributor
Shape 1
Give Back 10
Give Back 5
Give Back 3
View profile
AlexisCazes
MVP

06-07-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.

Answers (3)

Answers (3)

Avatar

Avatar
Shape 25
MVP
Andrey_Osadchuk
MVP

Likes

538 likes

Total Posts

973 posts

Correct reply

264 solutions
Top badges earned
Shape 25
Bedrock
Coach
Boost 500
Affirm 250
View profile

Avatar
Shape 25
MVP
Andrey_Osadchuk
MVP

Likes

538 likes

Total Posts

973 posts

Correct reply

264 solutions
Top badges earned
Shape 25
Bedrock
Coach
Boost 500
Affirm 250
View profile
Andrey_Osadchuk
MVP

01-07-2020

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

Avatar

Avatar
Boost 1
Level 1
camilles8371268
Level 1

Like

1 like

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile

Avatar
Boost 1
Level 1
camilles8371268
Level 1

Like

1 like

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile
camilles8371268
Level 1

30-06-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

Avatar

Avatar
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

339 likes

Total Posts

2,338 posts

Correct reply

819 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile

Avatar
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

339 likes

Total Posts

2,338 posts

Correct reply

819 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile
jantzen_belliston-Adobe
Community Manager

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