What is the reason why Report Builder is not available for Mac?Surely there is still a sufficient number of Mac users who use the Report Builder.

Yep. Still an issue. I've seen so many situations where a simple prefix of a date string or a siteID would provide the uniqueness needed, but alas... 20 characters. I've also seen the situation that Adam mentions where the orderID is just too big for 20 characters. The worst feeling ever is to tell a client that they've been feeding 24 characters into purchaseID for several years, but four of those characters were thrown away...

Agreed. DTM's cookie handling methods are terrible. Currently I include this library in DTM https://github.com/js-cookie/js-cookie And then I do this: _satellite._cookies = Cookies.noConflict(); And then use _satellite._cookies methods to read/write cookies. Doesn't solve for combined cookie functionality, but it's certainly better than DTM's limited methods.

yes please! I'd also love to pull the convoluted logic out of the App Measurement code and put it in a data element

Michael, for #1 check out this tool: http://www.disruptiveadvertising.com/analytics/auditing-a-dtm-adobe-analytics-implementation/

Very much needed!

YES PLEASE

Problem is that the products variable is super specific and so many customizations (events and eVars). Best case is to use the custom code. If you're using a data layer, you should be able to loop through the objects and build the products variable accordingly. This takes the weight off of the developers and allows someone with much more experience to put it all together inside of DTM.

DTM doesn't keep track of usage of the rules. What you can do is have these rules populate a new variable, and you can then look to see how often it's being used in the reporting. On the flip side, these rules may already be populating a unique value in an eVar/prop and/or a specific event, so you can look at the usage there.