Recommendation For Implementing New Adobe Analytics to Existing

[sharonkim12]

Would like recommendation on implementing Adobe Analytics on a site that has an existing Adobe Analytics currently implemented. The implementation is basic with a few eVars, sProps, etc. Some of the site is going through a redesign, with new sections being added. And therefore, would like to implement Adobe Analytics with new configuration. Not sure who implemented and configured current DTM, but will need to implement a more robust version.

• Is it possible to add another DTM container on the site and have the old one running at the same time? I've seen many sites with both DTM and GTM so figured this is possible? Once we are comfortable with the new DTM and data in Adobe Analytics, shut down the old one?
• Or the above is not recommended. Thus, create a new one, then once new DTM is ready, shut down old and use new?
• Or... ?

Thank you.

[Stewart_Schilling · Accepted solution]

Sadly, It is not possible to run more than one instance of DTM on the same site at the same time.

You can use Charles Proxy to replace the existing DTM embed (locally) with a new one while you are doing development. To do this you'd use a Body Response Rewrite rule.

If I were in your shoes, I'd be using Adobe Launch instead of DTM for the replacement.  I'd also take the opportunity to implement a data layer (if you don't already have one).

[Alexis_Cazes_]

I agree on the fact that you should think of using a data layer. Some good articles from Jan Exner

https://webanalyticsfordevelopers.com/2017/06/20/using-a-ceddl-data-layer-with-dtm/

https://webanalyticsfordevelopers.com/2016/01/19/data-layer-yet-another-reason/

https://webanalyticsfordevelopers.com/2015/05/19/data-layer-on-the-fly/

https://webanalyticsfordevelopers.com/2014/11/04/data-elements-vs-data-layer/

https://webanalyticsfordevelopers.com/2013/11/12/data-layer-tips/

In terms of DTM you can always deploy 2 analytics tools in parallel and it should work. Please be aware that if you set both tools to send to same report suite id then you will duplicate data. So one tool should be configured to prod and the other one to stage and switch once you happy with new implementation

I also agree that you should look at Launch which is lighter and faster than DTM and there are much more features and integrations than with DTM.

https://medium.com/launch-by-adobe/migrating-from-dtm-to-launch-57548251a86d

Blog Posts we recommend!

[sharonkim12]

Yes...I thought about the 2 analytics tools (separate report suite). But not sure about the current data layer if there is much of one, if that makes sense. Is it possible to continue collecting current data while "jiggering" the data layer to one that meets our needs? Haven't worked much with the technical side of all this so apologies if I am not making sense in asking my questions.

As for Launch, I am to implement the site in the same process as another colleague who is implementing on a new redesigned site that will be launched. Wasn't sure if we are to use Launch or DTM but we will be going with DTM since that is what is being used right now and would be faster to go with this. We will convert to Launch at a later time.