By default, HeadQ collects two distinct types of analytics datasets: transactional and event data. Transactional data captures critical outcomes like purchases, quote requests, and leads, while event data provides insights into user activity within the store leading up to a transaction. This includes key events such as page views, product interactions, cart additions, and checkouts. Event tracking utilizes cookies for efficient data storage and session management, ensuring a seamless and accurate analysis of user behavior.
Events tracked
| Event | Description |
| view_item | The user views a product |
| add_to_cart | The user adds a product to the cart |
| add_to_quote_cart | The user adds a product to the quote cart |
| view_cart | The user opens the cart |
| begin_checkout | The user starts the checkout process |
| purchase | The user finalizes the checkout process and makes a purchase |
| request_for_quote | The user requests a quote |
| calculate_price | The user calculated the price in the configurator |
| begin_configuration | The user started the configuration but did not calculate the price |
| complete_configuration | The user has completed the configuration and added it to the cart |
| generate_lead | The user has done an action that generates a lead to the store |
| remove_from_cart | The user has removed the item from the cart |
| remove_from_quote_cart | The user has removed the item from the quote cart |
Controlling data tracking
Event data uses cookies to track sessions. By default, it’s disabled, but you can turn it on or off in the store settings under Installation. Changes will take effect in a couple of minutes.
We strongly encourage enabling data tracking to understand better how users interact with your products and configurations.
HeadQ Cookies
The HeadQ JavaScript implementation sets a first-party cookie used to anonymously identify a user and support the core functionality of the service. The cookie does not contain any personal data, nor is it used for tracking users across third-party services.
| Cookie name | Default expiration | Description |
|---|---|---|
__hq_unique_id |
365 days | Used to identify an anonymous individual user. The cookie value is a randomly generated, unique identifier (UUID) that helps improve the user experience and distinguish between different sessions. |
The cookie is stored under the domain of the customer’s website and does not rely on any third-party cookie services for its operation.
Remember to update your Cookie policy descriptions + Privacy Policy.