The reporting displays the results of goals chosen during the Goal step of the campaign configuration process.

By default, no filters are applied, but you can filter the results to obtain more specific data based on various criteria.

Accessing filters

To access the new reporting filters, apply the following steps:

Go to the dashboard and click :
The new reporting opens.
Click Filters in the top right-hand section of the screen:
the filter panel is displayed.

List of filters

You can select one or more filters among the following:

Device
Browser
Customer loyalty
Date
Action tracking
Custom tracking
Page
Landing page
Geolocalization
Transaction
Item
Ecommerce variable
Visitor attributes

Device

Filter results based on user device (desktop, mobile, tablet).
You may notice some discrepancies between the filtered and non-filtered data on your reporting. This is due to the fact that filtered data is updated instantly whereas non-filtered data is updated every 48 hours.
For example, let’s say your campaign targets mobile visitors only. If you filter your report data to see mobile visitors, you may observe more unique visitors in the filtered view than in the non-filtered view.

⭐ Good to know

The sum of visitors on mobile + tablet + desktop may not be equal to 100% of the traffic because some visitors use other devices such as smart TVs, game consoles, car GPS and so on (not accounted out here).

Browser

Filter based on the user’s browser (Chrome, Chrome mobile, Firefox, Internet Explorer, Safari).

Customer loyalty

Filter results based on:

The New visitors: visitors who are visiting the website for the first time.
New visitors = number of new visitors / total of unique visitors

The Returning visitors: visitors who have already visited the website before.
Returning visitors = number of returning visitors / total of unique visitors

You may notice that the total of new and returning visitors is not equal to 100%. It may be due to the fact that some visitors see a campaign both as new and returning visitors.

For example, let’s say you launched an A/B test on your homepage. If a visitor visits your website for the first time and sees the campaign, he will be counted as a new visitor. If the same visitor goes back on your homepage the next day (new session), he will be considered a returning visitor because he will already have a cookie. In this case, the visitor will be counted as a unique visitor but will be counted as a new visitor as well as a returning visitor.

Date

Filter results based on a date or specific time period.
Select include or exclude from the first drop-down list.
To select a period, click the start date and the end date.

Update rules

There are the rules regarding data update: the older the campaign is, the lower the refresh frequency is.
Also, you might face a reporting whose results have not been updated for a few days. This explains why, if you open a reporting on a given day (represented by a green dot in the date picker), the days before might be unavailable in the date picker of the date filter.
In the top left card of the reporting, you can see when the results have been updated for the last time and when the next update will occur.

For old campaigns, the results of the current day will never be available in the date picker, even if data has just been refreshed.

Action tracking

Only display the results of users who carried out the selected action tracking(s).

Select include or exclude from the first drop-down list.
Select an Action tracking from the second drop-down list.

⚡	The action trackings displayed in the list are those previously defined in the editor. If no action trackings were configured, the filter isn’t displayed.

Custom tracking

Only display the results of users who carried out the selected custom tracking(s).

Select include or exclude from the first drop-down list.
Enter the name of your custom tracking.
[Optional] Enter text for your custom tracking.
[Optional] Enter a value for your custom tracking.
[Optional] Add a value.

⚡	You can select custom trackings configured previously in the campaign code or the AB Tasty Global Code.

Landing page

Filter the results based on the page the user entered the website on.

Select include or exclude from the first drop-down list.
Select an option which enables you to specify the page URL.
Enter the page URL.

Geolocalization

Filter the results according to a specific geographical area.

Select include or exclude from the first drop-down list.
Select a Country.
[Optional]Select a Region.
[Optional]Select a City.

Transaction

Filter the results based on transaction variables.

Select a category.
For the Transaction amount category, select an option from the first drop-down list, then enter a value in the Value field.
For the Coupon category, select Applied to display the results of users who used a coupon or Not applied to display the results of users who did not use a coupon.
For the Buyer category, select Buyers to display only the data of users who made a transaction during their session and Non-buyers to display the data of users who did not make a transaction during their session.
If you have implemented several transaction tags, select the name of the desired transaction from the drop-down list.
For the Currency, Delivery method and Payment method categories, select the desired option from the drop-down list.
[Optional] Add a value.

Item

Filter the results based on variables related to the transaction items.

Select a category.
Select an option from the first drop-down list, then enter a value in the Value field.
[Optional] Add a value.

Ecommerce variable

Filter the results based on the ecommerce variables configured previously in your source code.

Select include or exclude from the first drop-down list.
In the Key field, enter the name you have given your ecommerce variable.

The ecommerce variable filter enables temporary backwards compatibility with older ecommerce variables.

Visitor attributes

Filter the results based on the Visitor attributes.

In the Key field, select a key. The keys appearing in the drop-down list are those you configured in your source code or in the Visitor attribute section (Settings).

In the Value field, select the value you want to match with the key you selected above.

⚡	This filter works if you have implemented the Segment hit on your website or if you have defined one or several Visitor attributes from the Visitor attributes section in the Settings. This filter is only available for Tag v3.

Implementation

Applying a filter

To apply a filter, apply the following steps:

Click the filter you want to add:
The filter is displayed at the top of the filter panel.
Select one or more other filters as needed.
Click Apply at the top of the filter panel.

👍	You can add as many filters as you like.

The number of selected filters appears in blue to the right of each category and at the top of the filter panel.

Deleting a filter

To delete a filter, click the cross to the right of said filter on the filter panel. To keep the other filters currently applied, click Apply again.

To delete all your filters, click Reset in the top right-hand section of the filter panel.

Results displayed

When you apply one or more filters to the reporting results, these may take several seconds to load.

The conversion rate, improvement rate, gain probability (Gain probability tab), confidence interval and the median value (Confidence interval tab) are updated, taking the applied filters into account.

The number of unique visitors is also updated. It displays the number of unique visitors who match the applied filters, as well as the percentage these visitors represent compared to the total number of visitors.

When you apply one or more filters to the reporting results, the filtered view note appears in the top right-hand section of the unique visitor card.

New reporting - Glossary

New reporting - Gain probability

New reporting - Bayesian test

New reporting - Personalizations

New reporting - Test campaigns

New reporting - Configuring goals

New reporting: transactional indicators and ecommerce data

Installing the transaction tag