You can see key insights from your product finder directly within Aiden at an aggregate level (for all clients).
However, it is also possible to link your Aiden product finders to your Google Analytics account and even to your CRM/CDP to gather insights about all customers as well as at the level of a unique customer.
💡Good to know: This feature is an impact booster that may not be included in your Aiden plan. Contact us to validate or upgrade!
We recommend setting this up if you want to use the data from your product finder for e.g. marketingautomation purposes. You can then see which answers a particular customer has given and which products have been recommended to this customer. You can also create a segment of your customers who have used the product finder and compare them with other customers on your website, e.g. to find out the effect of the product finder on conversion rates or return rates.
In this guide, we explain how it works.
The basics
When a customer uses your product finder, it sends product finder JavaScript events to the web page in which you have included the product finder. You can record these events and then use them for further analysis.
In the overview below you can see how it works!
Event types
The product finder sends 4 different event types. View the event type to see what parameters are sent:
1. Question answered → Sent when a customer has answered a question.
Parameter name | Parameter value |
type | answered-event |
advisorId | The app unique ID used internally in the Aiden CMS |
advisorName | The app name |
data.question | The question label |
data.answers[] | List of given answer(s) |
2. Product advised → Sent when a customer reaches the advice page.
Parameter name | Parameter value |
type | advised-event |
advisorId | The app unique ID used internally in the Aiden CMS |
advisorName | The app name |
data.products[] | List of products |
data.products[].id | The unique Aiden product ID |
data.products[].name | The product title |
data.products[].link | The product link URL |
3. Product clicked → Sent when a customer clicks on a product on the recommendation page.
Parameter name | Parameter value |
type | product-clicked-event |
advisorId | The app unique ID used internally in the Aiden CMS |
advisorName | The app name |
productName | The product title |
productId | The product unique ID from the catalogue |
productLink | The product URL from the catalogue |
4. Start over → Sent when a customer clicks the 'Start over' button.
Parameter name | Parameter value |
type | start-over-event |
advisorId | The app unique ID used internally in the Aiden CMS |
advisorName | The app name |
Implementation
You will need a developer to set this up directly on your website. Below is an example of the type of script they need to create to pick up the Aiden events.
<script>
window.addEventListener("message", function (event) {
if (event.data.advisorName && event.data.advisorName !== "") {
handleAidenEvents(event.data)
}
})
function handleAidenEvents(event) {
switch (event.type) {
case "advised-event":
event.data.products.forEach(function (product) {
// Do something for each advised product
console.log("product advised: " + product.name)
})
break
case "start-over-event":
// Do something when user clicks "start over" button
console.log(event.advisorName + " started over")
break
case "answered-event":
// Do something when user answers a question
console.log(event.data.question + " answered")
event.data.answers.forEach(function (answer) {
// Do something for each given answer
console.log("answer given: " + answer)
})
break
case "product-clicked-event":
// Do something when user clicks "start over" button
console.log("product clicked: " + event.data.productName)
break
}
}
</script>
💡 Good to know: Need help? Feel free to contact our team directly at: [email protected].