AB Tasty lets you save the data related to transactions made on your website (e.g. transaction amounts, payment methods, number of items purchased, etc.), along with information related to the purchased items (average cart value, item price, etc.).
To send transaction data to AB Tasty and display it in the reports, you need to add the transaction tag to your purchase confirmation page, after the generic AB Tasty tag.
This data is available in the reports of each campaign in the form of indicators.
Once the transaction tag is implemented on your website, you need to run it through the QA process to make sure that for each purchase, the information is correctly collected by the AB Tasty tag, and that the transaction goal is visible on the goal configuration page.
Verifying that transaction data is collected properly
There are 3 different ways to verify the transaction data collection:
- With the QA Assistant
- With the console’s Network tab
- With the Application/Local Storage tab of the console
The first part of the transaction tag generates a “type=TRANSACTION” query and the second part generates a “type=ITEM” query. Use the Chrome browser console to make sure the transaction tag hit is collected properly. Do this via your browser’s Network tab, in the Local Storage section.
With the QA Assistant
The QA Assistant allows you to QA both tracking and transactions. Transaction data can be found in the dedicated tab:
You can place a fake order on your website and access the confirmation page. If the transaction tag is correctly installed, you should see the transaction data accordingly. If nothing is sent in the QA Assistant, it means that data is not collected and that the transaction tag has not been implemented correctly. If that’s the case, refer to How to implement the transaction tag? or to the Transaction tag FAQ.
With the console’s Network tab
Depending on the settings configured when implementing the transaction tag, these will also be listed with the transaction hit.
To make sure the transaction tag is sending hits correctly, apply the following steps:
- Go to your website.
- Open your Chrome browser console.
- Go to the Network tab.
- On the web page, add products to your cart and confirm your purchase.
- In the console, select the ariane.abtasty.com transaction hit.
Click the Headers tab and make sure the “TRANSACTION” and “ITEM” settings are there.
The transaction name (ta) appears just as you configured it when implementing the transaction tag. The AB Tasty tag automatically fills in the generic settings such as vid, vp, ul, sn, sen, sd, etc. in order to qualify the hit.
With the application/Local Storage tab of the console
You must also make sure the “transaction” and “item” type data has been collected and is present in your browser’s local storage.
To do this,
- Go to the Application tab of the console.
- In the left-hand column, unfold the Local Storage entry.
- Select the ABTastyData key:
All “transactions” and “items” type information is displayed.
Goal configuration page
Once the transaction hit has been collected and the usual processing time is up (between 45 minutes and 4 hours), you can add the transaction goal to your campaigns (for more on this, refer to New reporting - Configuring goals).
To do this,
- Create a new campaign in QA mode.
- Go to the Goals step of your campaign.
- Click the Transaction goal.
- Select your transaction goal to add it as a main or secondary goal.
The goal name matches the value assigned to the ta setting during transaction tag implementation.