Adobe DTM Tips & Tricks: Managing your multi-suite tagging implementation in DTM

How can I change the report suite dynamically if my s_code is managed by Adobe?

The recent update in DTM to allow Adobe to manage your analytics s_code has a bunch of good benefits in my opinion. Things like:

  1. You will always be working with the latest version of the Adobe Analytics library (no need to download the latest and greatest).

  2. If you designate your production and staging report suites as part of your Adobe Analytics configuration, DTM will automatically assign the right report suite for the right deployment environment.

But what if your implementation requires the report suite to change dynamically based on URL? Does this mean you automatically will need to switch to a custom s_code deployment? Is there a way to get the best of both worlds? Recently, I’ve been working on a DTM project that requires multi-suite tagging and I wanted to find a way to always give the client the most recent version of s_code and still be able to manage the s.account on the fly.

Using the Customize Page Code allows you to extend the s_code functionality before Adobe Analytics executes

If you choose to let Adobe manage your s_code, using the global “Customize Page Code” section in DTM will allow you to add any additional customized Javascript or plugins. This really means that your code changes can override or change variable settings (like s.account) because the custom code will take precedence over UI settings. So how can you change the s.account values dynamically for a multi-suite tagging implementation with Adobe managed code? Here’s what I did:

Step 1: Set your Library Management Configuration

Confirm that the Library Management configuration of your DTM property is using Adobe managed s_code.

Step 1 - set your library management config

Step 2: Configure the Custom Page Code precedence.

Make sure the precedence setting under the global “Customize Page Code” configuration is set to “After UI Settings” This will allow your code changes to override the use of default staging or production report suite settings.

step 2 config custom page code

Step 3: Add your custom code to dynamically set the report suite.

Open the “Customize Page Code” editor and add code that will set the report suite based on URL conditions. o   The example below will set the s.account based on the current URL. step 3 add custom code

Step 4: Save changes and test in staging.

step 4 save change and test

Using the Custom Page Code configuration is a great way to manage the report suite settings for multi-suite tagging and still get the benefit of an Adobe managed s_code implementation.

Leave a Comment

Your email address will not be published.

Contact Us

Related Posts

Join the Conversation

Check out Kelly Wortham’s Optimization based YouTube channel: Test & Learn Community.

Search Discovery
Education Community

Join Search Discovery’s new education community and keep up with the latest tools, technologies, and trends in analytics.




Scroll to Top


Catch the latest industry trends we’re watching and get new insights from our thought leaders delivered directly to your inbox each month.