Goal Property Unique Count
Overview
A Goal Property Unique Count metric answers the question: how many different values of this property did each user reach?
You pick a goal and one of its properties, for example product_id on a product_view goal. For each user, ABsmartly counts how many distinct values of that property appear in their goal events. Viewing the same product once or ten times counts the same: one product.
This makes it a good fit for questions about breadth rather than volume, such as "did this change make people look at more different products?"
How it's calculated
Say you track a product_view goal with a product_id property, and create a metric on that property.
context.track("product_view", { product_id: "P1" });
Three users are exposed to the experiment:
| User | product_view events after exposure | Distinct products | Value |
|---|---|---|---|
| Ana | P1, P1, P2, P3 | P1, P2, P3 | 3 |
| Ben | P1 (5 times) | P1 | 1 |
| Cara | none | none | 0 |
In the experiment results, this group would show a Value of 4 (3 + 1 + 0) and a Mean of 4 / 3 = 1.3333 distinct products per participant.
Values are distinct per user, not across the whole experiment. Ana and Ben both viewed P1, so it counts once for each of them. The group viewed only three different products, but the Value is 4.
Compare that with a Goal Count on the same goal, which counts every event: Ana 4, Ben 5 and Cara 0, so a Value of 9 and a Mean of 3.0000. Ben's repeat views make him look like the more active user, while the unique count shows that Ana looked at more products.
Creating the metric
When creating a metric, choose Goal Property Unique Count as the metric type, then:
- Select the Goal you want to measure, for example
product_view. - In Property, type the event property whose distinct values you want to count, for example
product_id. This field is required. - Optionally set an Outliers limit method, add Metric property filters, or Add time filters, as with other goal-based metrics.
Under Goal relations, you can Add cancellation. Unlike Goal Property, this type can't use Add refund or Add replacement.
How values are compared
- Values are case-sensitive, so
"abc123"and"ABC123"count as two different values. - The number
123and the string"123"count as the same value. - Events where the property is missing or
nulladd nothing to the count.
Reading the results
In the metric results table, Value is the sum of every participant's distinct count in the variant, and Mean is that total divided by the number of participants. The impact is calculated on the Mean, as with other continuous metrics such as Goal Count.
Because each user's values are counted separately, Value is not the number of different values seen in the variant. If every user viewed the same single product, the Value would equal the number of users who viewed it.
More examples
Products viewed: goalproduct_view, propertyproduct_id. How many different products users looked at.Categories purchased from: goalpurchase, propertycategory_id. How many different categories users bought from.Articles read: goalarticle_read, propertyarticle_id. How many different articles users opened.Products per purchaser: a Ratio metric with aGoal Property Unique Countofpurchaseonproduct_idas the numerator and aGoal Unique Countofpurchaseas the denominator. How many different products buyers bought, on average.
Good to know
- Great for discovery and variety experiments: recommendations, search, catalogue navigation or content feeds.
- If you cancel goal events, a value stops counting only when every event with that value has been cancelled.
- Outlier limits apply to each participant's distinct count. For example,
Fixedlimits of 0 and 50 count a user who viewed 200 different products as 50.