Firstly, you need to know how to measure your pages' value. Is it page views? Time spent? Bounce rate? Something else? To chunk up your pages into meaningful portions, you can consider using Classifications on the Page dimension to do that. https://experienceleague.adobe.com/docs/analytics/component...

I'm the developer of this extension. Thanks for bringing this to my attention. I have submitted a new version of my extension that fixes this. I've also replied to your private message about this.

@hs_vk , @hs_vk wrote: To send data to (or to use without any mapping) the Cart Additions, Cart Removals, Product Views (OOTB/standard AA metrics) - do we need to use the Commerce details field group i.e. productListItems and its respective fields like commerce.productListAdds.value? Think of it th...

I believe you're using AEM as your content management system, and AEM's Core Components is configuring ACDL for you. So what you're experiencing is a problem with how AEM implements adobeDataLayer, rather than how ACDL itself works. Adobe has provided documentation on how to use ACDL with this setup...

I don't think your problem is related to the one in the original post. I suspect that there's a bug in the _satellite.dlClonerLoaded code. Since you or your developers had written that, then your team would be in the best position to debug this. Try running _satellite.dlClonerLoaded directly in your...

Those desktop ones could be "edge cases", i.e. few and far between, assuming that the percentage of all desktop orders is very small. I'd still focus on mobile, if that is the vast majority.

Based on what you've shown, it looks like this affects users who browse your website on a mobile device only. Perhaps something has been programmed wrongly in the mobile version of the website such that the payment method isn't being set properly in the data layer. That could certainly happen. I've ...

Looks like the plug-in did away with your old format since its version 4.0 update in August 2016. To get back your desired value, you'll need to use some custom code to convert the plug-in's returned values to what you want. Something like this:   // use this inside your AA extension's custom code's...

Seems that the error is occurring because a "ga" is missing in the web page. Without knowing what that "ga" is exactly nor what is going on in your web page, it's hard to troubleshoot. Can you please provide more information of what is going on when you encounter this error?