Metrics based on transactions
Last updated
Was this helpful?
Last updated
Was this helpful?
A metric is based on an event and helps to analyze the number of collected events (or their mean/average) and compare it to a baseline, generally the total number of unique visitors or the total number of sessions. For more information about definitions, please refer to the following .
In this article, you'll find detailed information about all AB Tasty transactional metrics:
You need to set up the transaction tag on your website, it collects transactions from your checkout page. For more information, please refer to this
It’s triggered each time a visitor performs a transaction on the website and is normally sent from your checkout/validation page.
AB Tasty receives the event transaction but also all the information added in the transaction tag:
transactionRevenue
affiliations
paymentMethods
currencies
shippingMethods
customVariableNames
productCategories
All this information is useful to calculate metrics and also to filter your report on specific purchases.
This data is displayed two times and with a different definition and calculation in the reports:
Total transactions: total number of transactions/single purchases performed during the campaign for each variation
Unique transactions: total number of different buyers (unique visitors who have performed one transaction at least)
In this example, as the unique transaction and the total transactions column are not equal, we conclude that some unique visitors have purchased more than one time during the campaign duration, in both original and variation groups.
AB Tasty variable : transactions
metric view: Overview or
metric view: Transaction detailed data
The transaction rate is always automatically calculated at the visitor level:
AB Tasty variable: transactionUserConversionRate
In a test campaign, this metric compares two transaction rates (at a visitor level or a session level) and helps to identify the best performer between two variations (the variation is compared to the baseline, which is the original version).
The average order value calculated on all the recorded purchases in the variation.
20 different transactions recorded, for a total amount of $10,000.
Average order value = $10,000/ 20 = $500
In a testing campaign, this metric compares two average order values and helps to identify the best performer between two variations (the variation is compared to the baseline, which is the original version).
Average order value variation - average order value baseline
Average order value original = $154.20
Average order value variation = $153.90
Average order value growth = $154.20 - $153.90 = $+0.30
Average product quantity is calculated on all the recorded purchases in the variation.
Total number of items purchased in all transactions / number of transactions
Total number of transactions = 153
Number of purchased items = 298
Average product quantity = 298 / 153 = 1.94
Average price of a purchased item per variation
Total revenue: $10,000
Number of purchased items: 298
Average product price = $10,000 / 298 = $33.55
This is the revenue generated by each variation (turnover = sum of all transaction values).
Please consider the variable you use to capture the amount of a purchase when you’ve installed your transaction tag, this amount doesn’t have to contain the delivery fees or taxes.
This is the difference between the revenue of a variation compared to the revenue of the baseline (original)
Revenue variation - revenue original
For an A/B Test with only one variation:
In the , select metric view: Raw data
In the , select:
In the , select: metric view: Transaction detailed data
The growth metrics are always displayed on all variations except on the one which is used as the baseline. See this to learn how to change the baseline in a report.
In the , select: metric view: Overview
In the , select: Average order value detailed data
In the , select: metric view: Average order value detailed data
In the , select: metric view: Average order value detailed data
In the , select: metric view: Revenue detailed data
In the , select: metric view: Revenue detailed data
In the , select: metric view: Revenue detailed data
This is the fictive amount that could have been earned if 100% of the traffic of the campaign had been assigned to the variation (assuming the same behavior in terms of transaction rate and average order value).