The Adobe Experience Cloud Debugger https://chrome.google.com/webstore/detail/adobe-experience-cloud-de/ocdmogmohccmeicdhlhhgepeaijenapj?hl=en now offer "post processing data". that means you get the values after the processing rules and you can directly see if a new rule works.I guess that might so...

I don't know if it is useful or not.example: we started adding a code to each var, eg "v1" for eVar1 and classifications have a letter at the end, eg. "v1a" for the first classification of eVar1.adding the variable name to each variable might solve some clients, other might have just too many inform...

good idea! would save me some time to manually edit the conditional formatting each month...

would it be an option to restrict access to the same user group by permission? eg. add a new permission setting to only allow "user lookup" of own "user groups"? this way we could create a new user group for external agencies and those persons have only access to names/users within that group.

can't believe that we need to make an idea on this! it definitely should not work like that, a restriction for "normal users" is highly needed!thanks for posting the idea...

no, just the header zone of a single project panel with workspace. basically the headet of the panel where you have the panel filters (drop down zone) and the date selector for the panel.especially on larger panel there are a lot of cases where I keep on scrolling up and down just to use the header ...

When creating content within a panel of a workspace project a sooner or later don't see the dropdown zone and the daterange anymore. especially the dropdown zine is very useful for creating new adhoc segments or for selecting a filter (or select a value from a dropdown filter).It would be great if y...

jorisdebeer​instead of using "open in metric builder", select a second metric from the table and choose a function, eg. "divide". this will create a "local metric" not messing up your left rail. then "edit" the metric as usual (delete the second metric) and save.now you have a "local metric" just fo...

good idea!but maybe more useful would be a combination of "classifications" (fetched from RS settings) together with "classification rules" and "last upload date"sort of an overview where you can easily see the whole picture of props/evars which have classifications.

great idea!meanwhile, here's a tip I often use:1) activate a new "prop" (traffic variable)2) setup the new rule you want to test as you would normally setup a rule, except the following changes:a) additional condition to check query string contains a certain parameter, eg "pr-test"b) write a text to...