To analyze the performance of your configuration, power our insights reports and support personalization, we capture key e-commerce events on your platform. These are events such as product views, item clicks, add-to-carts, and purchases.
ImportantMagento extension will support all events out of the box. Any customizations that do not hook into Magento defaults might need extra work. For example, sticky add to cart buttons.
👉 Check Event Tag adoption status to see what is what currently is supported.
To automatically enable Event Tag events, go to Stores > Configuration > Catalog > Tweakwise.
Look for Send analytics events to tweakwise and set the value to Yes.
From version 8.7.0 the setting can be found under the section General:
In earlier versions, the setting can be found in the Merchandising Builder section (in some versions Personal Merchandising subsection):
Important!Validation: the implementation can be tested using Live Analytics, contact your CSM or support to enable this for your instance.
Troubleshooting: If an event is not working but it should be supported, this is probably due to customizations on the platform. For example a template that is overwritten so the original event is not sent.
👉 Check Event Tag adoption status to see what is what currently is supported.
Enabling personalisation and A/B testing
To enable personalisation and A/B testing you have to enable the "Personal Merchandising" option. This makes sure the users profile key is sent along all tweakwise Delivery API requests that returns items. (Search, category, suggestions, recommendations). Before enabling this option make sure varnish cache is fully configured.
Enable "Personal Merchandising" to support personalisation and A/B testing
Full page caching disabledWhen enabling the "Personal Merchandising" option, Full Page Cache will be disabled for relevant pages in order to be able to send personalized request every page. Varnish will make sure that the individual item/product tiles will be cached. This way Tweakwise can serve unique results per pageview, based on the profile key.
NOTE: Obviously this will have some negative impact on your reponse times on the relevant pages. How much this impact is depends on the configuration of those pages and is different per implementation.
Notes
- A profile key is automatically generated for personalization. If no personalization cookie exists, a new profile key is created and stored in a cookie. To ensure registered customers use the same profile key across sessions, you can either reuse an existing profile key cookie or implement custom profile key logic.