My IT team is really concerned about the need for synchrous loading of DTM. They'd prefer to load it asynchrously so that if the call fails, the page will load anyhow. Barring that, they want it to load last. If loaded asynchrously, my event based rules fire but my page load rules don't and my data elements don't work.Has anyone dealt with similar concerns or do you have suggestions for ways to implement that won't result in us relying on the call working perfectly?

All of my event based rules are firing beautifully, so I know the code is on the pages correctly, but none of my page load rules are firing at all. We have a prop that captures all URLs upon page load that was in place prior to adding DTM to the site. I set up a rule for an eVar to just copy that prop. It doesn't fire at all, which is odd, because I asked for assistance from Adobe when setting that rule up. It should fire on every page.As background, we've had SC code on our site for five years,...

We're in finance. Everything is naturally going to drop off significantly on the weekends because markets aren't open. However, the anomaly detection sees this as an anomaly even thought it's completely expected. Being able to exclude weekends would greatly increase the usefulness of this product.

I work in finance. Our site activity drops very sharply on weekends as people can't take action since markets are closed. This means that I get anomalies every weekend for certain events and measurements. Being able to exclude weekends would help me find true anomalies.

We'd like to know and compare average activity throughout the day for two different ways of reaching our site. Currently, the chart for Hour of Day shows the busiest 15 minute increment in order of activity. It would be nice if instead, it showed a chart going from 0:00 to 23:45 and showed average activity during those 15 minutes periods in order. That would be an accurate picture of activity on your site throughout the day and wouldn't require an export to Excel and charting.

IE10 can be used in Metro or Desktop mode, and the user string also differentiates between touch and non-touch. It would be great to know how many of our users are on each of these modes, as we can make decisions about site design in the future.