Another limitation with "Compare Time Periods": if I do "Compare Time Periods>This week last year to this time range":It nicely goes back in time to the right week:But if I update the date range on the panel, the comparison does not update:...Making it very hard to create a dynamic, update-able repo...

Kind of? The current "analytics on analytics" (if you're referring to the usage logs) only includes Reports and Analytics- not Ad Hoc, not Workspace, not API/DW requests. It also takes a bit of tweaking to get into a useable format, if you want to see how many folks viewed the campaign report, for i...

To show some examples:Currently, if I right click on a column (in certain circumstances), I get a "Compare Time Periods" report. I have a few clients that use this feature A LOT. When you do, you end with something like this, where a column appears to the left with a date range over it (which I can ...

This seems to be a duplicate of Calendar Events in Analysis Workspace

I currently love and use the "Compare Time Periods" option frequently, but it only works in certain situations (for instance, it isn't an option if I have "days" as a dimension in the report), and I can't drag in Time Periods I've already created. I frequently want that sort of "compare" functionali...

This sounds very similar to the already-existing "Enable EU compliance for Adobe Analytics" option in the Analytics tool/extension?

Yep, I know Segments and Virtual Report Suites are a workaround for this. But those have a few potential problems too: You have to have been capturing IP into a custom variable. Unless folks have been doing that already in their RS, it has the same retroactivity problem- it would only work for data ...

In most cases, folks create new Bot Rules specifically because they've uncovered a bot that has been messing with their data... unfortunately, by the time you've identified the problem and created the rule, it's too late: the bot has already done damage.The workarounds are pretty drastic- applying a...

It would be awesome if, when I have multiple metrics/columns in a freeform table, I could add some sort of visual divider between columns. It would serve no purpose other than to make it easier to view. So this:Could become this:

Good idea, and I love your example! Though in Workspace, allocation can also be based on your metrics (for instance, an eVar with Linear doesn't show as linear in workspace unless you have a metric you've set to be linear- see Followup Post: Allocation in Analysis Workspace | Digital Data Tactics