Adobe Experience Platform

Would it be possible to add the Web Property name where the event occurred in the "Audit Events" area?

UX improvement (for fast clicking users):If you add a change in the Library Contents, then forget to delete or fill it and try to save the library, the upcoming error sign is kind of small. The error sign is just near the unfilled change ("Select a Change below"), but the blue bar below the head "Library Contents" ("This library contains...") ist much more visible. Thus you won't directly understand wich error appeared or why you can't save.

Hi,     Would like to suggest to enhance the Adobe DTM Publish History to be able to change the time display from “UTC” to “GMT +0800” (i.e. Singapore), because it is very confusing to look at UTC time.     Thanks.Regards,Yaw Dak

Within DTM, when viewing the rule lists, the name column is truncated. When we have a description and unique rule name longer than the available view - it would be great to be able to expand that column width to take advantage of larger screens.

Hello, Currently while working on mobile apps that uses adobe analytics SDK,we have noticed that Adobe acquisition links doesnt allow other external parameters to be added to the adobe acquisition links. All external parameters added are getting truncated from the play store/app store url created by Adobe . Here is an example below https://c00.adobe.com/v3/fea46a1d1546a5cade6a4355b0711fe88382c487c5e3654c716ad962e66b54a2/start?a_g_id=com.symantec.mobilesecurity&a_i_id=520284590&a_dd=g&ctxa.referrer.campaign.name=AbeTestCampaign&ctxa.referrer.campaign.trackingcode=camptrackingcodeabe&ctxa.referrer.campaign.source=sourceabe &ctxa.referrer.campaign.medium=mediumabe&ctxa.referrer.campaign.content=contentabe&ctxa.referrer.campaign.term=termabe&utm_source111=gasource utm_source111 is a test extenal URL parameter  added, which gets truncated from the app store URL below https://play.google.com/store/apps/details?id=com.symantec.mobil

It would be helpful to be able to custimize the calendar in mobile services.  Our fiscal calendar starts on a Monday, but Mobile Services calendar starts on a Sunday.  It adds an extra complication when trying to compare Mobile Service data with any other Adobe tool.  

Hi, I was wondering if DTM could include an option where a user could choose to ask DTM to minimize any html and / or javascrit which is being added thus allowing a boost in performance. This could be a great option to enable only to affect the production environment.

I would like to see the %data_element% syntax expanded to be able to reference properties of returned objects.  For example, currently in DTM you can do %data_element% syntax in various fields.  And for certain built-in data elements, you can e.g. %this.id% (reference to a clicked link's id attribute in an event based rule). But I would like this to also be doable for arbitrary objects returned from data elements. For example if I have the following on a page:  var dataLayer = { page: 'some page' } If I create a data element named "dataLayer" of type js object type and point to dataLayer, it will return an object.   Or alternatively if I create a data element of type custom script and it has  return {page:'some page'} Now if I use %dataLayer% in a field, it will return something along the lines of [object object] or else a stringified version of the object.   But if I try to do %dataLayer.page% then it will output that literal string because there is no data element of that name.   So

Currently, when you want to use the Media Module in Adobe DTM, the only way is to switch the AppMeasurement Core Code to "Custom" and paste the Media Module before the existing code. By doing so, you loose the option to one-click-upgrade via dropdown, and the ability to see if your property is using the Most Recent AppMeasurement code version or not. I suggest to add a checkbox that is called "Add Media Module Core Code" to avoid the disadvantages and lets you work close to Adobe's best practice (see screenshot attached).

Currently, when a new page is loaded, DTM walks through all Page Load Rules and checks if any condition is met. Things get difficult if you have an AJAX reload on the page. What I at the moment do is reconstruct all I have set up as Page Load Rules and put this in the Event Based (or Direct Call) Rule that triggers on the AJAX reload. Whenever something changes, I have to change this on both rules. It would be great if there was a way to remove this redundancy and get something like _satellite.trackPage(); which you could put in an Event Based / Direct Call Rule and does nothing but let DTM walk through every Page Load Rule and fire s.t(); after - just as it would after a real page load.

Adobe Mobile Services allows the configuration of marketing links. These links can be tracked. However, the only reporting metric that is available to track the clicks is 'number of clicks in last 30 days'. This does not allow us to properly track these clicks.  It would be better if we can report the number of clicks by day, week, month, etc. 

Hi, I am making use of the DTM library download which was intially a pain as you could not specify a specific url as it assumes based on the location i.e. //. DTM now automatically bring the domain host which is great but i have noticed an issue especially when using different staging environments which requrie a certain port number. It would great if DTM can add the port number if available or just allow you to make use of a data element. In my current situation i always need to override that piece of code so i can work on all my staging. Thanks

When I am looking to go in and delete or add categories to a bunch of rules at once, it's a pain to have to roll through pagination. It would be great to be able to select the number of rules to be displayed. 

It would be a huge time saver and no brainer to have a vendor tag template system to help simplify publishing of tracking codes and eliminate errors.  Everyone else inf the tag management space seems to have a huge tag template system that lets You Instantly Launch 3rd Party Code Snippets in seconds. Google Tag Manager Tealium Ensighten 

I have Global Variables set up at the Adobe Analytics tool level. I would like to be able to have a checkbox in the Event-Based rules that allow me to send that information in the servercall for the event-based rules that leverage the s.tl() function. This is useful so that I would only need to update in one place (the Global Variable settings) when we need to add a variable instead of needing to go into the affected event-based rules as well. 

Hi My organisation has a large digital presence with multiple DTM property's (60+) and it is time consuming going through all the DTM property's to see if I have rules waiting to be published. It would be great if publishers/admins would receive a notification when a rule is waiting to be published, or if a notification workflow was added. I requested this back in May, but haven't heard anything more around this? http://help-forums.adobe.com/content/adobeforums/en/marketing-cloud-forum/activation.topic.forum__fgx6-hi_i_have_alarge__b2cf-hi_parat_can._s_1_tosp.html/forum__fgx6-hi_i_have_alarge.html#forum__fgx6-hi_i_have_alarge__b2cf-hi_parat_can CheersCallum

Many will be using the tag man for 3rd party marketing tags. This is not very flexible today and can easily become crowded when using many tags and conditions. Suggestion: Make it a 2 step process: 1) Add tag name/category eg Doubleclick that will appear on the same level as Adobe Analytics In the overview add a tag.Make it possible to name a tag and then add the custom script It should be possible to add several indenpendent tags under one cataegory "Doubleclick" eg "Doubleclick Retarteging" and a custom script"Doubleclick Order page" and a custom script 2) Go to RulesIn a dropdown it shall be possible to select the newly ceated tag in a dropdown after the GA/Adobe. eg. select Doubleclick > "Doubleclick Order page" and then make a rule for that

Let's say I have the following: some text I make an event based rule, Event Type "click", with an Element Tag or Selector "#foo".   I want to get the text from the button "some text" and pop e.g. eVar1 with that text.  Right now, in order to do this, I have to create a custom condition where I do something like this:  _satellite.setVar('buttonText',this.innerText); return true;  And now I can use %buttonText% in my eVar1 field.  This is *okay*, except I do not like this from a maintenance perspective.  I have an on-the-fly data element created within the rule, and the only way anybody will ever know about it is if they go to the rule and look.   What I ask for is the ability to create the data element from the Rules > Data Elements page, just like any other Data Element.  I think it should be fairly easy for you to at a minimum internally pass a reference to "this" to the custom script function for use.  But really, you can expand on Data Element functionality in general by adding "

It would be nice if you could delete data elements after seeing a warning that they are being used in the custom code!

Need ability to restrict permissions within the Mobile UI to Admin-only. Business users currently can modify settings in "manage variables" for any app. This causes several problems, generally resulting in degraded data both in the mobile UI and within Report Suites on the Analytics side (this is the main concern). Currently, all functionality within the Mobile UI is available to all users - they can even delete apps (though unlikely to occur). At the least, we need lock down usage of the entire Mobile UI for Admin use only. This ability could live within either Analytics or the Mobile UI. We are in the process of converting all apps to using Adobe SDK 4.x (from both a TMS solution and from Adobe SDK 3.x). Therefore, we are entirely dependent on context variables, which are fully exposed to any of our 100+ end-users within the Mobile UI. This is a core need.

On top of being able to deactivate rules, I would like a way to archive them as well (I think Target has something similar).   This would make it so that the rules that you may not need any longer don't show up as you scroll through your list of page/event rules (some of our properties have 5+ pages of rules). However, we'd like to keep a copy to refer back to in case we ever needed to.

As a 3rd party consultant I have seen this scenario in DTM far too often now that I think something in the DTM interface should change so that users don't accidentally use the "serialize from value" field when they are not intending to set up event serialization. Many of my clients think it's a way to change how events increment (that's the most common misuse). I've also come across clients who clearly don't understand that events are incremental and actually populate the "serialize from value" field with the same string they are trying to populate their eVars and sProps with, resulting in no data getting collected at all. I'd recommend a little info or question mark icon that users could hover over, right next to the "Serialize from value" text, with an onHover modal that pops up to explain exactly what this field is for.

When entering values for eVars etc in to the DTM, there are a limited number of dynamic values that can be entered. EG:%this.innerHTML%%this.getAttribute()% Could be useful to have a "Custom Script" option as in the "Data Element" section is a function that returns a string, and has access to the "this" element the event has been triggered on

Guys, Currently it's not possible add a comment after changing something within our code or Page Rules. We have the possibility to add a "Note" but the Note is not linked to that specific version. In order to mantain and understand our code we need to know what changed on a specific version. The possibility to add comments while creating a new version of our tags it's really important. Please, do something about that since it is really difficult to remember what have changed between versions.

DTM has the ability to write cookies using the _satellite.setCookie function.  However, there are a few problems with how they currently function, and it requires some work arounds to get it to work properly for some websites.  Here are the items that need to be changed:Cookie names can be written with a space in the name, or other invalid or undesired values.  This is especially possible when a data element is set to persist for a visit or visitor.  The cookie names should be encoded so this will no longer occur.  There are some servers that will throw errors on any request where this occurs, so it is best to avoid this.Cookie values are not encoded.  This can cause a few different problems.  First, if the cookie contains a semicolon, it'll break how the cookie is stored and the cookie will not have the correct settings.  Next, some servers can throw errors if cookies contain non-encoded values, especially for any multibyte or special characters.The cookies are ALWAYS set on the subdo