Adobe Experience Platform

Within a direct call rule, you can specify Adobe Analytics to be disabled, pop as s.t(), or as s.tl().  Currently there is no way to specify this automatically.  This forces us to do a lot of duplication of direct call rules: one for s.t and one for s.tl.   Can you please update this to allow you to dymamically specify which AA call type to use?  e.g. extra argument(s) passed to _satellite.track(), or fields in the DC rule that we can put a %data element% reference in. 

It would be great to have a more comprehensive search abilities in the DTM. For Example:- able to return any rules (event/page/direct call) that use eVar56 and event32 in Adobe Analytics- find any rule with eVarXX with the value 'product'- find any rule that uses the Data Element "%thePageName%"

It will be really nice if you can add new property admin privilege which you can create new user.

DTM went down today for an unknown reason.  Normally when systems go offline, the first place I check is http://status.adobe.com/. DTM is not listed on this status board.  Can you please add it.

The event-based rule for "Element in viewport" is an awesome feature. The problem is that it only runs once per HTML page view. As sites migrate to SPA the need for a setting to capture each time an element appears in the viewport is becoming more necessary. Perhaps an option to set a maximum number of times the rule can fire per HTML page view, between 1 and infinite. An option to limit the rule from firing more than once per unique HTML element would also be a slick addition. As in, if you have 3 internal campaign promotions on a page that all use the same CSS Selector, the rule would fire three times on the page as each unique element appears on page. But no "repeats" of the same unique element.

Users (non-admins) in DTM cannot see the embed script that is associated with each property. Brands with dozens of DTM properties often provide User-only access to agencies and consultancies. But there's no way to confirm that a particular property matches up with the embed code on a particular site. Users should be able to see (not edit) what the embed code is on all DTM properties.

Currently in DTM, only Admin users have the ability to copy an existing rule. All roles have the ability to create a rule, but only Admins can copy. Why is that? This capability would be extremely useful to all roles, and not just Admins. Please open up the copy feature to users in all roles.

Right now you cannot use a data element to set the report suite ID.  It would be great to be able to set the report suite ID conditionally via a data element so you do not have to write the logic in the s_code, and so you can really control what the report suite ID should be set to in any condition.  By writing it in the s_code, it will work for the base page view, but it will not work for any event based rules or direct call rules that send data to Adobe Analytics.

DTM knows all states of the loading page. A build in feature for measuring the page load time would be a simplification and better then using any javascript custom code.

Hi, I'd like to suggest 3 features for DTM. 1. A feature that would allow for downloading specific report suite settings for events, evars, props etc. It would be a lot easier to do the mappings for our rules using names coming from our report suites rather then evar1, event10 etc. Note that a pretty similar feature already exists for AEM - SiteCatalyst integration. Inside mapping framework a user is able to give his SiteCat credentials and then the page is populated with variables from specific report suite. 2. It would be nice to have the ability to use the interface for numeric events (similarly as we have the ability to serialize them, maybe a small checkbox to indicate the numeric event and an input field for it's value?). 3. A functionality that would allow us to choose how data elements will be stored. In our recent project we had issues with cookie usage. Basically a lot of data for a third party tool was stored in a cookie and adding more cookies caused problems with exploding

Hi, I have noticed that the Direct call has a "bug" as variables which are set on rules which trigger s.tl() persist and get tied up with my direct call rule (i.e. to fire a s.t()). I have been battling trying to find an effective solution to try keep only the variables which are set on the template. The above can be very challenging especially for end users who dont have any developer background.  It would be great to have DTM be more strict in terms of taking the variables which have been set within the tempalte and the editor (i.e. under the analytics tab). If this cannot be done, another option can be to offer the functionality to 'clear variables' when setting up any kind of rules. ThanksJerome

It would be great to have a callback feature in DTM for Adobe Analytics.  The callback would fire after data was sent to Adobe Analytics, such as when the s.t() or s.tl() functions are called.  The callback would likely reference the "s" object, so that s.clearVars() can be called.  This will allow every hit that is sent to Adobe Analytics to start with a clean slate instead of having to use what was on the previous hit.  This is especially important for single page applications. It would be great to have a global callback available, with the option to set one for each rule.  These would fire after the next instance of sending data, and would not continue to queue up for subsequent hits.

DTM CSS Selector tool (the bullseye) in event based rules should be available to use when authnetication (login to a site) is required.  Currently, it's only available for use on unauthenticated pages.

Hi - Like Tealium has a global analytics library that you can choose to replicate for all profiles, can we have something similar in DTM. Most companies have multiple sites and the same Data Layer across all. This feature would be very helpful to them. Making changes to the global library will be visible on all that refrence it. (a simple publish is needed)

Would be great if we could have DTM recognize events pushed (as outlined in the W3C Digital Data Layer spec;  https://www.w3.org/2013/12/ceddl-201312.pdf) to the relevant Data Layer/Universal Data Object  If we could build Event Rules off of events pushed to the data layer there would no longer be a need for _satellite.track("event") code embedded in a page. This would keep DTM and the data layer totally indendant of the UI content and one less thing to worry about breaking when changes to a pge are made for content or functional reasons. When I have a page I want to track multiple events on that are not CSS related today it requires adding multiple _satellite.track()'s to the page.  I also think this would make configuring DTM for Single Page Apps easier as all you need to do is have development push a "Page View" event into the data layer instead of firing a _satellite.track("pageview") every time. Development is laready pushing all kinds of data for each page into the data layer thi

Special characters are not allowed in cookies per RFC 2109, 2965, and 6265. However, when storing a Data Element value for a Session in DTM, the value is not URL-encoded in the session storage cookie that DTM creates. This lack of URL encoding of whitespaces and special characters many of my Data Element values contain caused multiple services on one of my sites to fail when trying to parse those non-compliant cookies. Please update DTM libraries to automatically encode and decode values stored in cookies.

It would be extremely useful to have a DTM api for basic operations like: get, post, put of rules (event, direct, pageload) and data elements. Editing different properties is quite a pain atm.

DTM should allow inheritance of properties: eg we embed one property on one specific site.This property inherits from 3 containers:1) a global web analytics property - managed by a central WA department2) a global marketing property - managed by a centralmarketing department3) a local marketing property - managed by a country marketing department This way every library property stays quite clean and not all logic has to be merged into one propertyAdditionally not all functionality needs to be adjusted in multiple properties if a change is needed.

I often find myself using processing rules to fix occasions of where DTM Rules fails, or to make a change faster than I can edit/create rules in DTM. In that light, a connection between the two, event if it's just a library in DTM that I can use to look up Processing Rules.

Is there a way to increment events by more than 1 in DTM?  We like to track lead numbers AND assign them a revenue value in a separate currency event, but it doesn't appear that this is something we can easily do through DTM.  The only solution I've found is to use the Custom Page Code editor...but then I need to fire ALL events there. If this isn't possible, I'd like to submit this as a feature request.  I'm guessing a lot of others would appreciate this functionality. Thanks!

I would like to export the conditions and resulting scripts in DTM. That would help me audit faster, find rules affected by CSS changes, and implement ObservePoint more easily. 

The online documentation and training material needs major improvement. Most of the training videos are outdated and the documentation is lacking key information - see attached screen shot taken from Enterprise TV for "new user orientation" - how many years outdated is this??  There have been occasions when I request missing documentation information via Client Care and the response is to pay for consultancy services which doesn't seem acceptable. The  training content and documentation available with Google is night and day versus Adobe. On a positive note, I thought the video training for DTM was very good - so more of that please.

We do have customer request where we will have to administer loads of 3rd party tags. As we already track the page (with one property for all their sites) we want to avoid that people administering those 3rd party tags get access to this property, as they are not allowed to do changes to the property with Analytics in it.As of now you just can set access rights on a property level, not per tool or tag.A second property would solve the issue, but as you cannot determine the name of the DTM JS object ('_satellite') this does not work, as the second property overwrites the first one.Thus my feature request is, to allow renaming the DTM object (as you can do with the Analytics 's' object) to be able to use two properties at the same time. Thanks a lot!BestregardsFritz

One of the biggest concerns IT departments have in regards to DTM is the option to include custom JavaScript. This is a very valid concern as one line of bad code could potentially break the entire page, or inadvertantly interfere with important functions. Right now anybody with User access can include custom code with any rule, and as soon as that rule is saved it immediately goes "live" on the staging site. To minimize this it would be great if only designated users had access to the Custom Code options, where non-approved people would be limited to only the regular UI options. This could be either a new Role, or maybe a checkbox of available options for a Group. I kind of like the available options one as this would make it easier to have other "options" like this in the future.

Hello, when using the Transaction ID-field in the Adobe Analytics tool-section, the transaction ID is not set in the s.tl()-call of the corresponding rule. I have to include "transactionID" to the s.linkTrackVars variable manually in custom code section. This is very confusing and not documented.Therefore I suggest to include the transactionID in the s.linkTrackVars variable by default, if it is set in the Transaction ID-field. Best regards,Frank