Add better dynamic s_account support to DTM

joshd7227840

MVP

09-04-2014

Legacy Adobe Analytics (<=H26) has variables for dynamically populating s_account:

 

dynamicAccountSelection

dynamicAccountList

dynamicAccountMatch

 

For some reason this was removed from the new AppMeasurement library.  These are incredibly useful variables used by many people.  

 

Currently DTM encourages you to use the AppMeasurement library and I have a feeling when Adobe eventually fully integrates the core lib into DTM, they are only going to use AppMeasurement instead allowing option for Legacy.  In either case, currently DTM only allows you to specify a live vs. staging s_account value, and the only way that gets populated is if you include the specific script URL for the environment, or use the _satellite methods for changing the environment.  This is not at all the same principle as the dynamicXXX vars. 

 

What I would like to see integrated into DTM is the same functionality that dynamicXXX vars offer.  There are of course ways to override things with custom code, but I would like to have it integrated as part of the DTM tool, since the major selling point of a tag manager is to minimize custom coding. 

1 Comment (1 New)
1 Comment

joshd7227840

MVP

09-04-2014

My suggestion was originally for Adobe Analytics, but this same principle should be applied to your other integrated tags (e.g. Google Analytics).  For example,  When I create a Google Analytics tag, I can specify a stage and live account id (what pops _setAccount) but the same restrictions are on this as I explained in my original post.  

 

I would like to see better support for dynamically populating this value and other "config" values.  Basically, the "rules" forms have great support for dynamically populating a given variable, but  everythign in the "config" section for a tag seems geared more towards if you have a single site. If you could update the "config" forms to be more like the "rules" forms where you can dynamically populate the value based on rules, that would be awesome. 

 

This is useful for implementations across multiple sites that need to have data routed to different report suites/accounts/profiles/etc..