QA Mode & QA Assistant

Definitions

The QA (Quality Assurance) process enables you to choose the method(s) used to perform the QA of your campaign, which is a mandatory step before the launch.

QA mode is a specific phase which aims to make your campaign visible to you only, permitting you to visualize the configured changes and perform the QA. Your targeted visitors won’t be able to see the campaign until you take it out of QA mode and formally launch the campaign. It's available in the campaign flow, step "QA & Overview".
QA Assistant is a functionality which helps to QA your campaign during your navigation on your website during the QA, and to identify and understand why some modifications are not visible as planned

To QA your campaign means to check that all changes, targeting, and tracking have been implemented correctly before making the campaign live for your visitors (the audience targeted by your campaign).

QA mode

The QA mode enables you to choose the method(s) used to perform the QA of your campaign.
The aim of the QA mode is to make your campaign visible to you only, in order to visualize the configured changes and perform the QA. Your targeted visitors won’t be able to see the campaign yet.

To access the QA mode, go to the step QA & Overview of the campaign flow.

You can target your campaign by URL parameter, by IP and/or by Cookie:

Targeting by URL Parameter
Targeting by IP is the easiest and fastest way to QA your campaign. It enables you to QA your campaign on all devices and browsers at the same time.
Targeting by cookie may be useful if you work in a big company with a shared IP address.

Using this method is safer because when you QA your campaign by IP, your colleagues may be able to see your campaign on their own devices. The cookie method is local, meaning you have to manually add the cookie in your browser (the Cookie Editor extension can be useful) or in your Chrome console. You will be the only one to see the campaign. However, with this method, you will need to repeat the operation for each browser you want to QA.

When you enable at least one parameter, the QA mode turns On. Once you have configured the QA mode, we recommend performing the QA of your campaign using the QA Assistant.

For more info on configuring the IP and/or Cookie parameters, refer to How to use the QA mode.

In any case, once on QA mode, you can QA your campaign 2 different ways:

QA Assistant

The QA Assistant is an application (based on an iframe) that allows you to QA your campaign without having to open your browser console. It displays the campaigns that are live on the active page, those that are active on the website (other than the page you are viewing) as well as information related to the events configured in the campaign.

Please refer to the following articles to learn how to use the QA Assistant:

on desktop
on mobile

Good to know 💡

The QA Assistant is compatible with the following browsers: Chrome, Firefox, and Safari
The QA sessions (when the QA Assistant is opened or when the test is in QA mode) are not counted in the report once the test is launched in production without QA mode

The QA Assistant displays three tabs, allowing you to view and control various information on your website/page:

The Campaigns tab
The Events tab
The Transaction tab

Campaign tab

The Campaigns tab is displayed by default and is divided into two different sections:

Live campaigns on this page: the top section displays all campaigns that are live on the active page (the campaigns you are assigned to)

From there, you can visualize the variations of your campaigns from the Variation/ experience Dropdown:

Live campaigns on this website: the bottom section displays all campaigns that are currently live on your website, regardless of whether you are assigned to them

Each line, which relates to a specific campaign, displays the campaign type, the campaign name, the campaign ID, and the targeting configuration acceptance status: accepted, rejected, pending, etc.

Page URLs (Where): corresponds to the specific URLs where the campaign is supposed to trigger
Trigger (How): corresponds to the specific triggering conditions to trigger the campaign (number of session viewed pages etc.)
Segment (Who): corresponds to the specific segmentation conditions to trigger the campaign (device, emotionsAI segment etc.)
Display frequency: corresponds to the accepted visit frequency to trigger the campaign
QA mode: whether QA mode is enabled on the campaign or not
Status: general status of the campaign on the session, the global result of the previous criteria

On the right of each line, you can see the overall campaign status:

Status	Explanation
Accepted	The user matches all of the targeting criteria.
Rejected	If one of the targeting criteria is rejected (page, audience, or trigger), the user will be rejected from the whole campaign. You can see the targeting details by clicking on the campaign row from the QA Assistant.
QA rejected	The campaign is currently in QA and the user does not match at least one of the QA conditions.
Traffic rejected	Less than 100% of the traffic is allocated to the campaign and the user is not exposed to it. This status means that the user is being part of “untracked traffic” (visitors who see the original version of your website but whose actions won’t be collected at all). The information is stored in the AB Tasty cookie, so to avoid it, you must either clear your cookies or navigate to a new incognito window (and close all previous incognito windows).
Pending	The campaign is configured in AJAX mode and the tag always checks the targeting.
1-visitor 1-test	The one visitor one test option is activated on your account and the user has already been exposed to another campaign.
Missing data	Some information is missing to validate the targeting. This can happen for geolocation or userAgent data, for example. You can see the targeting details by clicking on the campaign row from the QA Assistant.
Exposed to another experience	The user is rejected from this experience because they have already been exposed to another experience of the same personalization campaign.
Timeout loading variation data	For deferred campaigns, variation data has taken more than 3 seconds to load so tag stop and don't execute the campaign. More details are here.

Events tab

The Events tab enables you to perform QA in real-time and to verify that actions and custom trackings have been correctly implemented on your campaign.
The following tracking types can be verified with the QA Assistant:

Page tracking is not compatible with the QA Assistant - your page goals won’t appear in the Events tab but will be displayed in the reporting interface.

Heads up ⚡️

To perform the QA, you must be on a page included in the targeting of your campaign or on a page where tracking has been configured.

To do so, click the element of the page where action tracking has been configured. The action name will automatically appear in the Events section, with the following information:

Event name
Event type (action or custom tracking)
Campaign name and ID where the event will be recorded
Variation name and ID where the event will be recorded
Time at which the event was triggered

When clicking on the event name, you can see the corresponding element highlighted on the web page.

Transaction tab

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 to the QA Assistant, it means that data is not collected and that the transaction tag has not been implemented correctly. If that is the case, refer to How to implement the transaction tag? or to the Transaction tag FAQ.