Curious about the impact of your product finders on e.g. sales and conversion? Then activate your Impact Dashboard in Aiden:
The Impact Dashboard in Aiden
The Impact Dashboard works by forwarding customer purchases to Aiden. To do this, you place the Impact Script - a small piece of JavaScript - on the order confirmation page.
This is how you activate the Impact Dashboard:
Log in to your Aiden account
Go to one of your apps
Go to Analytics
On the Impact tab, click Set up and follow the steps!
Unless you are technically proficient yourself you will probably need a developer to do this. All instructions can be found below.
💡Good to know: The Impact Script forwards all orders from the website, which Aiden then checks whether the order can be linked to a choice user. This is because in the Aiden backend we can see if a product was recommended in a particular session.
Just to be sure, check if you are allowed to share this order data according to your terms and conditions.
💡Product Variants: By setting product variants in your catalog, Aiden can show better insights in the Impact Dashboard. Learn how to set up product variants in this tutorial.
1. Insert the Aiden base script
Most likely this script is already in your webshop (otherwise your product finders would not work properly), but just to be sure: follow step 1 here and especially check if the Aiden script is present on your order confirmation page.
2. Integrate with the Impact script
First choose how you want to integrate the Impact script. You can either install it directly on you website, or integrate it through Google Tag Manager (GTM).
⚠️ Note: Preferably do not place the scripts via Google Tag Manager! Sending the purchase information is then blocked by adblockers. This results in significant under-reporting of metrics in Aiden.
That said, we know that integration via GTM is often the fastest option, so you'll find that explanation later in this tutorial as well.
2.1. Direct integration
To forward the purchase information, you can use this example script as a starting point and place it on the order confirmation page. Make sure that the values in orderId, currency, and products are dynamically populated per order with the requested purchase information.
After placing the script go to step 3.
View example script
View example script
<script type="text/javascript">
window._aiden = window._aiden || []
window._aiden.push({
event: "Purchase",
// debug: Optioneel.
// Kan gebruikt worden om te kijken of events correct verstuurd worden.
// Als een event incorrect is wordt dit in de console gelogt.
// Weghalen voor productie gebruik, anders worden er geen events verwerkt!
debug: false,
// apiKey: begint met 'AID-' en vind je onder "Analyze" bij een keuzehulp in Aiden.
apiKey: "YOUR API KEY",
// orderID: bestelnummer
orderId: "Order Identifier",
// currency:
// ISO-4217 valuta code waarin betaald is.
// https://nl.wikipedia.org/wiki/ISO_4217
currency: "EUR",
// Inhoud van de bestelling
products: [
{
// aidenProductId:
// Unieke identifier die in Aiden ingesteld staat.
// Als producten via een product feed zijn gekoppeld is het
// aidenProductId hetzelfde als de waarde in het <id> element
// in de XML feed.
aidenProductId: "12345678",
quantity: 4,
price: 99.99, // prijs per stuk
},
],
})
</script>
⚠️ Note: The IDs Aiden receives via a CSV or Google Shopping Feed are used to recognize purchased products and link them to product finder sessions. So make sure the correct IDs are sent along. Should a developer do this for you, tell them what type of ID to send along.
2.1. Integrate with Google Tag Manager
Integrating with Google Tag Manager is possible, however, it does increase the chances of under-reporting by adblockers. It also adds additional complexity to the integration. The steps below outline what you need to do to set up Impact analytics with Google Tag Manager. The exact steps depend on how Google Tag Manager is set up on your webshop and which other Triggers or Variables are already set up.
2.1.1. Create a Tag
Create a Tag of type Custom HTML. Paste the example-script below into it. As a Trigger, you can select a "Page View" that triggers only on the order confirmation page.
View example script
View example script
<script type="text/javascript">
window._aiden = window._aiden || []
window._aiden.push({
event: "Purchase",
// apiKey: starts with 'AID-', you can find this at the "Analyze" section in Aiden.
apiKey: "YOUR API KEY", // Replace with your API-key
orderId: "{{Purchase - order ID}}", // Replace with GTM-variable containing the transaction/order ID.
// currency:
// ISO-4217 currency code
// https://nl.wikipedia.org/wiki/ISO_4217
currency: "EUR",
// Content of the order
// Important: make sure the price field in the products variable contains the price per item, not the price * quantity
// This script fills the aidenProductId parameter with id or item_id value
products: ({{Purchase - order products}} || []).map(function (e) {
if(!e.hasOwnProperty('aidenProductId')) {
e['aidenProductId'] = e["id"] || e["item_id"];
}
return e;
})
})
</script>
2.1.2. Replace the default values
There are a number of example values in the script that need to be replaced.
💡 GTM Triggers and variables: There are probably already some purchase tags in your GTM container. These send purchase information to for example your CRM or an ad or analytics platform. You can use these tags to see which variables and triggers are used.
API-key
First you need to fill in the API-key where it says "YOUR API KEY". You can find the API-key in Aiden by clicking on your name > settings > API keys. Make sure the API key is between quotation marks, just like "YOUR API KEY" is.
{{Purchase - order ID}}
Replace this variable with the variable that contains the order/transaction ID. You can find the right variable by searching the variables list for "order id", "orderid", "transactionid" or "transaction id". Or by looking at other purchase-tags.
{{Purchase - order products}}
Replace this variable by the variable that contains the purchased products. Every product should contain at least an id or item_id, the quantity and price (per item).
The product-ID needs to be the same as the product-ID in the catalogue in Aiden. This is important because otherwise we cannot match the ordered product to the advised products.
Searching the list of variables for the terms purchase and products van help you find the right variable. You can also look at other purchase-tags for help.
⚠️ Note: Please make sure the price of every product is the price per product and not the price per product times the quantity. Settings this up the wrong way will result in bad data.
Didn't find the right variable?
If the variables do not exist, they need to be created. You can read how this is done here.
3. Checklist
Check the following questions, and make sure you can answer all of them with a definite "YES".
Do the id's in the aidenProductId-field match the ones in the Aiden catalogue?
Does the price-field contain the price per piece? In Aiden the amount will be multiplied by the quantity, if price is not the price per piece the impact analytics will not be correct.
Does the orderId-field contain a unique value for each order?
Is the embed-script loaded on the page from where the event is send?
Is the event sent from the same domain where the app is embedded? So not on a subdomain.
Did you remove the impact script from the test or staging environment?
4. Wait for the first purchase to be shipped
When a user makes a purchase, data will be sent to Aiden. Then under "Analytics" in Aiden you can verify the integration. If everything comes in correctly, then the integration is successful and Impact analytics are now available to all product finders!