There’s the required data that you collect on every interaction, but there’s also metadata you should collect depending on the Module.
Here are some examples of the metadata:
- Row/List Index: If the module contains some kind of list or rows, you should collect which row the user clicked on. It tells you exactly where the interaction happened on the page. It may show a pattern to how users click on your products.
- Product information: Any Interaction connected to the product should include product information. Information such as product name, price, product availability, etc.
- Customer information: Customer data that changes the site, or is of interest to the analyst should be tagged. Maybe your site changes if it’s a minor, or if the customer is buying from a certain country, etc.
- Business-specific: Your business may have parameters that are specific to it. Look into how you can connect it to your modules, or the customer session.
Component Analytics thrives when tagging is automated. See if you can automate the information above too.
– Samy
Component Analytics daily
Every weekday, I publish about Component Analytics and analytics collection strategies.
