A space to discuss online store customization, theme development, and Liquid templating.
We offer a cart drawer, and some merchants have reached out stating that their "Added to cart" stat plummeted once they enabled the cart drawer.
To be clear, this is while viewing the Online store conversion rate metric of the Analytics dashboard.
Interestingly, their other metrics remained the same, so I don't believe Adblocker is playing a role here. There is a clear line between when they enabled the cart drawer and when the analytics change.
Can someone @ Shopify help me to understand why a side cart might interfere with the analytics here?
Some specific questions:
I'm just trying to better understand so I can determine whether it's happening with every merchant who uses our product, or if certain merchants have specific conditions that might come into play.
Thanks very much. Let me know if you need more information.
Hi Camsb,
Are you able to identify any differences in terms of themes being used that might be affecting these metrics? Some themes handle carts differently which could impact this behaviour.
Liam | Developer Advocate @ Shopify
- Was my reply helpful? Click Like to let me know!
- Was your question answered? Mark it as an Accepted Solution
- To learn more visit Shopify.dev or the Shopify Web Design and Development Blog
Hi Liam,
I've not been able to identify anything that stands out.
Some additional context:
It would be helpful to know exactly how the metrics are collected (ie. which API calls / scripts) so I could pinpoint potential interference between our inline cart code and the theme code.
I'm seeing some info on validating analytics for a Hydrogen app:
Validate that analytics are working
Anchor link to section titled "Validate that analytics are working"To check that analytics data is being sent to Shopify analytics as expected, inspect your Hydrogen app's requests in your browser's developer tools network tab, and filter for the monorail-edge.shopifysvc.com endpoint.
Requests to this endpoint return an HTTP response status code of 200 OK or 207 Multi-Status.
- A 200 status code means the data upload succeeded as expected.
- A 207 status code means there are errors in the request payload. Any related error messages are returned as part of the response. When running your app in development mode, error messages output to the browser console.
I'll continue looking into this -- it appears that maybe these merchants are sending fewer requests to the monorail-edge endpoint 🤔