Agreed - Classifications and Classification Rule Builder will help here. It's not quite as 'real time' as you're describing, which is why we're all excited for your idea, but it will get the job done.

I just gave this a try and it looks awesome! If you're looking for a more granular view, you can use Week or Day instead of Month. When I used Day, the data was a lot more jumpy, so I ended up using a Moving Avg Calc Metric:Nice Brandon!

Perhaps I'm confused. Isn't that optout page hosted on your website and therefore editable? Or is it being loaded somehow directly from Adobe and therefore unable to be edited? My apologies if I'm missing something here.

Would this https PNG work? https://assets.omniture.com/en/images/skins/default/transformation/002251.global.logo.oms-mark.152x63.png

I really like this idea, here's the best representation of what you're looking for that I was able to come up with today:In essence - leverage Time Ranges to create two columns in the table. Not as slick as yours, but hopefully it's helpful until we can create a visualization more akin to the one yo...

Can't you just specify the YTD dates in data warehouse? I'm confused why that wouldn't be possible.

As you're detecting bots, here's a (somewhat complicated) methodology that I put together with our consulting team to filter bots in a more advanced way:https://theblog.adobe.com/advance-bot-filtering-powers/

Hi there - I'm in complete agreement that bot data needs to be brought into Workspace. However, I'm pretty sure traffic that is identified as bots (via Bot Rules) will already be filtered out of all of your Workspace data, the same way it's excluded from all reports in Reports & Analytics except the...

Thankfully, DTM will work with any data layer you throw at it - even more than one! The best practice is probably to leverage the ContextHub Tool to hook into your JSON objects, then create Data Elements that align with each of the elements in your data layers. Here's the documentation on ContextHub...

Hi Todd,The most important thing for you to consider is overwriting the s object on the site that has two Adobe implementations. You'll want to create an object with a name other than s (sParent, for example) so you can send data to Company A's implementation without interfering with Company B's imp...