Adobe Experience Platform Data Collection

with GDPR coming in place, the call to the Experience Cloud ID service is coming into discussion. Several legal consultants in companies are claiming that the call only may be issued if there is a consent from the visitor to be tracked.The current implementation of the standard extension, will alway...

I can create a Data Element of type javascript variable, or custom code, that references/returns an array.  However, Launch (and DTM) doesn't have any functionality baked in to take advantage of this.  Instead, it ultimately expects a string value returned (and type casts the value to string when pa...

When setting Adobe Analytics variables within an action several levels of the hierarchy are expanded by default. I often find myself removing it entirely just to clean up the workspace. It would be nice if hierarchy was collapsed by default and could be added if needed.

With GDPR coming, the need for consent awareness of rules and actions is becoming more stringent.We have quite a lot of rules which stack up depending on a consent level of the user (e.g.):- strict -> only complete anonymous tracking allowed (eg. analytics beacon)- mid -> some user identification al...

Hi,the idea is basically very simple I want to call a particular rule in the actions section:This can be very helpful for SPAs because I can e.g. define the Page Name or page specific events in the triggered rule but don't need to include all variables I typically have in a Page Load. The second Pag...

Today, the Access controls are not that granular with respect to Mobile services UI and we cannot create custom roles and assigned access to certain features only. either you have to be Admin or not. I have a specific scenario,We want our product managers/Sales/Marketing teams to have access to send...

Launch (and DTM) Data Element Change event type polls the data element every 1000ms (1s).  I would like a field added to specify how frequently to poll.  Add a warning about potential performance considerations, similar to what you already display about timing, but give me the ability to specify thi...

If a rule or data element fails I would like to see more robust error messaging in the build screen, e.g. which rule or data element failed rather than a generic failed message.

At the moment environments are controlled by JavaScript tag that is deployed.  i.e. dev, staging, and production environments have different tags and this determines what code is delivered.However, often we find ourselves wanting to test our development code against the 'live' environment (obviously...

It would be really useful to be able to be able to store a description against each data element and each rule to explain what it is.In Adobe Analytics, the ability to add descriptions to components has become common place so I was a little surprised not to have the ability here.From a workflow/gove...