Definition
The QA Assistant is an application (based on an iframe) that enables 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. For more information about QA mode and QA Assistant, please refer to the following article.
You can also use the QA Assistant on mobile devices, for more information, refer to How to use the QA Assistant on mobile devices.
⭐ Good to know
- The QA Assistant is compatible with the following browsers: Chrome, Firefox, 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 the QA mode.
How to use QA Assistant on desktop
Step 1: Launch the QA Assistant on Desktop
Before launching QA mode, make sure to add QA mode on your campaign.
- From the QA step, activate the QA Mode by enabling QA parameters
-
Click Open QA Assistant
-
Choose the option "Open QA Assistant on desktop"
- The URL set up in the Main information step opens along with the QA Assistant on the default browser of the device.
The QA Assistant can be enabled on any website where the AB Tasty tag is implemented. The URL set up in the Main Information step opens in a new tab. The QA Assistant opens in a panel at the bottom of your page.
|
Heads up ⚡️ The pop-ups blocked modal may display on your browser and prevent the QA Assistant from opening. To enable the page, select the option always allow pop-ups and redirects from abtasty.com and validate. |
⭐ Good to know
You can open the QA Assistant direcvtly from your website:
- Go to your website
- From the keyboard, type Ctrl+Q+A: the QA Assistant opens in a panel at the bottom of your page.
The QA Assistant displays three tabs, allowing you to view and control various information on your website/page:
⭐ Good to know
To minimize the QA Assistant, click the AB Tasty logo in the top left corner. The QA Assistant will still be visible as a logo in the bottom left corner. To close the QA assistant, click the cross that appears upon hovering over the AB Tasty logo.
Step 2: Check modification display
The Campaigns tab helps you to check that:
-
The targeting is correctly applied: you are assigned to the campaign while meeting the targeting conditions.
- The modifications are correctly displayed: verify that there’s no regression on your website when displaying the campaign.
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. |
Targeting details
By clicking on the campaign row, you can see the details of the targeting configuration (page URLs, Segment, and Trigger) in a table with the exact values you configured in AB Tasty. On the right side of the table, you can see the current status for each targeting criteria and, if you are rejected, understand why you are not exposed to the campaign.
From there, you can go to the Targeting step of your campaign to edit the targeting set.
If you are looking for a specific campaign, you can enter the campaign ID, campaign name, or campaign type in the search bar.
Step 3: QA Assistant - Check event tracking
Make sure you are assigned to the right campaign: from the Campaigns tab, you will find all campaigns you are assigned to, illustrated with the “Accepted” status.
QA the click action from the Events tabs:
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:
- Campaign Action tracking (XAT) and Account Action trackings (AAT)
- Custom tracking
- Transaction tracking
- Element visible tracking
- Dwell time tracking
- Scroll rate tracking
- Iframe click tracking
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.
If you are looking for a specific event, enter the event ID, event name, or event type in the search bar.
Step 4: Check transactions
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.
How to QA a redirect campaign
Once you're exposed to a redirected URL of a redirect test, you won't be able to switch back to the original variation from the variation dropdown list.
On the original variation, make sure you've checked all click tracking actions before switching to the test variation.
Share link option
By clicking Share link, you have the possibility to share the QA Assistant link with a colleague to enable him to perform the QA of the campaign on the device of his choice (desktop, tablet, mobile).
The IP address of the device used by your colleague to QA the campaign must be included in the QA parameters.
The link can be used once and is available for a limited time of 8 hours.
Use cases
The QA Assistant can be useful for various reasons:
- To QA your campaign. That is to say verify that the modifications, targeting and trackings have been implemented correctly.
- To know what campaigns are currently running on your website or on a specific page. You can see all the running campaigns at a glance and check the targeting configuration.
- To understand why you don’t see a specific test on your website/page. When checking the targeting configuration, you can quickly see why you don’t match the targeting, and return to the targeting section of your campaign to modify it.
Let’s say you want to verify that the set-up, graphic modifications, targeting and trackings of your campaign have been implemented correctly.
When using the QA Assistant, you don’t have to apply 100% of the traffic to the variation you want to QA. You just need to enable the QA mode from the QA step of your campaign, launch your campaign and then use the keyboard shortcut to trigger the QA Assistant on a targeted page.
From the QA Assistant, you can now verify that you are included in the targeting of your campaign and see the different variations you implemented in real time.
In the variation column, you can select which variation you want to display on the page. Click on one variation from the dropdown list to display the matching modifications on the page. Then, you can perform actions on your website according to the events you want to track and verify that they are correctly set up.
If you have trouble opening the QA Assistant, please refer to Troubleshooting: QA Assistant doesn’t load on my website.