👉 Implementing the Transaction tag in the Settings

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 must implement your transaction tag.
This page enables you to easily implement your transaction tag: simply indicate where to find the transaction data. However, you still have the option to implement your transaction tag directly into the source code of your confirmation page.
For more information on the transaction tag, refer to Installing the transaction tag.

This feature is only available for early adopter clients at the moment. If you want to be part of this program, please contact your dedicated CSM or [e-mail].

📋 Prerequisites

To configure the transaction tag according to your environment and perform quality control, you must be able to complete the purchase path to the order confirmation page, in order to access the variables that contain the information associated with the transaction.
It is often possible in a preprod environment, or with the selection of a subsequent payment method (eg: check), or with a payment card dedicated to QA, ... etc.
You have the possibility to delegate this setup to AB Tasty, please contact your CSM with at least, one of these informations:

• Payment method (real or not) and procedure to cancel the order if necessary.
• Copy of the HTML of an order confirmation page (arrival url just after an order) which contains the variables associated with the transaction (article number, reference, price, etc.).

⚙️ Configuration

You can implement your transaction tag using one of the three following methods:

• Datalayer mode: by declaring the variables from your Datalayer containing the transaction related information.
• Selector mode: by declaring the CSS selectors containing the transaction related information.
• Expert mode: by completing the code snippet.

To use the Datalayer mode, you first need to integrate your Data Layer into your AB Tasty account settings. The following Datalayers are supported: Google Tag Manager, TagCommander and Tealium.

Depending on the specified settings, a JavaScript code is created and will be automatically included in the AB Tasty tag. This code is updated each time the configuration is modified.
First, you need to create an affiliation, which coincides with the name you assigned to your transaction tag. The affiliation, referred to as ta, will appear in the list of goals to be configured in the campaign creation flow, to be visible in your campaign report.
For each affiliation, you can specify the URL(s) of your website on which the transaction information is available, such as the confirmation page. If you don’t specify any URLs, all URLs will be targeted.
You can create as many affiliations as you want and edit and delete them. Then, you need to select the method with which you want to implement your transaction tag: 

Datalayer mode

This method enables you to implement your transaction tag based on the variables defined/configured in your Datalayer.
For each mandatory field, you need to enter the name of the key that will be extracted from the corresponding variable. These keys can be found in your Datalayer. 
For example, to fill in the transaction ID, you need to enter the key that matches to the transaction ID configured in your Datalayer. For example, in your Datalayer, if the transaction is available in the "order_id" key with a matching value of "OD564", this means that you need to enter “order_id” in the transaction ID field.

For more information on the Datalayer, refer to Integrating your Data layer into your AB Tasty account. 

Selector mode

This method is useful if the transaction data is available directly on the code of your confirmation page. In this case, you need to fill in each field with the matching CSS selector that can be used in the document.querySelector function.

The item count number (icn) coincides with the total number of items purchased during the transaction. It can be calculated using three different methods: If your key (Datalayer mode) or selector (Selector mode) contains the total number of purchased items, select Default. If your key or selector contains unitary purchased items, select Count. If your key or selector contains the quantity of each purchased item, select Sum.

Expert mode

The Expert mode enables you to implement your transaction tag via a JavaScript code.
By default, there is a code example that you can edit and replace with your own data, available in your source code or Datalayer. You also need to apply the appropriate format to your values (string, float or integer) as described in our developer portal. 

The transaction id (tid), transaction revenue (tr) and item count number (icn) must be declared during transaction tag implementation. The other settings are optional, however we recommend configuring them also in order to enable the application of matching filters in the reports later on.

Preview

The Preview enables you to verify that your affiliation/transaction tag has been correctly configured by showing the latest transactions registered on your website.
The Transaction Tag Generator uses Universal collect data, which is why, after you have implemented your transaction tag, it may take a few hours for the first transactions to be visible in the Preview.
For each transaction, the values matching the keys specified in your transaction tag are displayed:

Need additional information?

Submit your request at [e-mail]

Always happy to help!