The event-based rule for "Element in viewport" is an awesome feature. The problem is that it only runs once per HTML page view. As sites migrate to SPA the need for a setting to capture each time an element appears in the viewport is becoming more necessary. Perhaps an option to set a maximum number...

Users (non-admins) in DTM cannot see the embed script that is associated with each property. Brands with dozens of DTM properties often provide User-only access to agencies and consultancies. But there's no way to confirm that a particular property matches up with the embed code on a particular site...

I love how you can easily filter the Dimensions menu in Analysis Workspace by variable names for props and eVars. For example, type "eVar1" into your Dimensions or Report menu (Reports & Analytics or Analysis Workspace) and you'll see a list of eVar reports that have "eVar1" in them (eVar1, eVar10-e...

Has anyone else seen pretty significant delays and content flicker on mboxes that are injected on a page using DTM versus mboxes that are hard-coded on the page? I have a client with literal seconds differences between mbox loads and have definitely seen some flicker (gah!). Would love to know if an...

Today, DTM deploys mboxes around elements on the page using the mboxUpdate function. This works very well - it erases the opportunity for content flicker:- DTM hides the element with code in the - DTM calls mboxUpdate- mboxUpdate waits until window.onload to update the content  Unfortunately, some c...

Let's face it - bots are getting smarter. Bot Filtering needs to get smarter too. Bots are getting better at changing user-agents, IP addresses, domains and more in between visits. Bots are now even adding delays between page views to look more like a normal visitor. And don't forget, they're runnin...