Hello,
I wanted to ask around to see if anyone migrated from DTM to 'Launch' yet? If so, was it an easy migration? Is it really as easy as a turning a switch 'on' and everything moves to Launch? I would like to know the challenges faced through this? I did some research on the actual steps to migration but didn't find much. However, I found more steps on 'How good launch is compared to DTM'. I want to know that also but first would really like to be enlightened on the steps to migration. Can anyone help me?
Thank you,
Neha
Solved! Go to Solution.
Adobe made a big effort so that migration might be as smooth as you would expect it. but don't be surprised, if there are some issues in your implementation, all depends how you use DTM and what you want in Launch.
However, Launch offers a bunch of new opportunities you never had in DTM (or you would need to use a lot of custom code). but writing all the cases or differences in here would take far too long.
Based on our experience (we have already migrated the first few properties) I would strongly recommend to "verify" your current implementation. You can take the chance to not only migrate, but "rethink" the current implementation. If doing so, the effort might be much more - but worth in the long turn (depending where you start at).
there are a lot of very useful articles I can recommend, just use google to look for:
- https://medium.com/launch-by-adobe/migrating-from-dtm-to-launch-57548251a86d
- https://www.searchdiscovery.com/solutions/partners/adobe/adobe-launch/dtm-launch-assessment/
- DTM-to-Launch Migration Series #1: Options and Considerations - 33 Sticks
- https://webanalyticsfordevelopers.com/tag/launch/
- https://jimalytics.com/tag-management/adobe-dtm-vs-launch/
Adobe made a big effort so that migration might be as smooth as you would expect it. but don't be surprised, if there are some issues in your implementation, all depends how you use DTM and what you want in Launch.
However, Launch offers a bunch of new opportunities you never had in DTM (or you would need to use a lot of custom code). but writing all the cases or differences in here would take far too long.
Based on our experience (we have already migrated the first few properties) I would strongly recommend to "verify" your current implementation. You can take the chance to not only migrate, but "rethink" the current implementation. If doing so, the effort might be much more - but worth in the long turn (depending where you start at).
there are a lot of very useful articles I can recommend, just use google to look for:
- https://medium.com/launch-by-adobe/migrating-from-dtm-to-launch-57548251a86d
- https://www.searchdiscovery.com/solutions/partners/adobe/adobe-launch/dtm-launch-assessment/
- DTM-to-Launch Migration Series #1: Options and Considerations - 33 Sticks
- https://webanalyticsfordevelopers.com/tag/launch/
- https://jimalytics.com/tag-management/adobe-dtm-vs-launch/
Thank you for the detailed response. These articles are very helpful. I have another question- If I have no experience with DTM but I am interested in learning Launch, is that possible or I need some DTM background?
Thank you again,
Neha
Views
Replies
Total Likes
no, you don't need to know DTM (maybe it is even better to start with the new tool). there are some great youtube videos about launch.
just start, try and error will give you a good learning
Views
Replies
Total Likes
Perfect, thank you. I will check it out.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies