The example you mentioned is a bit more complex than that though.. "visit" is an arbitrary concept that must be applied to the data.  They would essentially be replicating what they already do so that you can get reports.  This is exactly what the reports or api already give you.  IOW this is alread...

Okay so here's the problem, Summary: Allow for DTM to load a tool but not output the "trigger" code. Many sites are setup to output content and libraries and other resources in a progressive manner.  For example, when you use angular.js framework.  The issue with this vs. DTM is that a lot of things...

When I create a new report suite and do it by duplicating an existing report suite, the custom menus and classifications are not automatically duplicated.  I would like for this to be automatically done.  Copying the customized menu structure after the fact isn't *that* hard to do, but copying the c...

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 t...

Legacy Adobe Analytics (<=H26) has variables for dynamically populating s_account: dynamicAccountSelectiondynamicAccountListdynamicAccountMatch For some reason this was removed from the new AppMeasurement library.  These are incredibly useful variables used by many people.   Currently DTM encourages...

there are sortby buttons in the column headers that you can sort the report suite listings by.  

Currently in order to gain access to Processing Rules, you must become certified.  The logic of this is that data can be changed so Adobe wants to ensure you know what you are doing. However, I find that this is a pointless hoop to jump through, given thata) I've taken the test and am certified.  Mo...

The API does provide information for the classification settings.  Of course it's not "user friendly". But it is more or less "programmer friendly."  That's why you should have a programmer make it "user friendly" since "user friendly" is objective and therefore left up to you to decide what format ...

Currently through the API you can get information about: - props- events- eVars- list vars But you can't get any information about hierarchy vars (e.g. hier1). I understand that you should not be able to change (SaveXXX) the settings, since this is something enabled by ClientCare, but you could at l...

Perhaps I misunderstand your request, but you can already sub-classify things.  Granted, it's a little limited, but perhaps it will suit you?  When you go to create classifications, you can do like Variable> a>> aa>> ab>b And the template will look like this: Key   a   a^aa   a^ab   b This doesn't r...