you mean you had the same numbers in the past and suddenly they diverged? Can you narrow it down to a specific metric/calculated metric and "play" with the segments (add/remove) to narrow down what might cause the difference?

in report builder you should see the same numbers as in the "reports" interface since it has the same "backend". are you sure you have exactly the same settings in the report (filters/metrics/dimensions) as well as user permissions?

did you try to use a "calculated metric" just including your custom event and set decimals to 2?maybe it is just a display problem....other solution: multiply the number by 100 to send to Adobe Analytics. then use a calc. metric and divide by the same number (100) and "show decimals"

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

"Report Builder" is based on the old API 1.4 and similar to "reports data" mentioned above.On the other hand "Analysis Workspace" has a new reporting engine (API 2.0) and a new way of how to fetch, process and calculate data.the link you mentioned will give you most of the differences between the tw...

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

did you found another reason? and why do you create a "metric" with "distinct count" and not a "visit segment"?

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.