How to use the QA Assistant on mobile
Last updated
Was this helpful?
Last updated
Was this helpful?
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 .
You can also use the QA Assistant on mobile devices, for more information, refer to .
⭐ 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.
The QA Assistant can be enabled on any website where the AB Tasty tag is implemented. There are 2 ways of launching the QA Assistant on your mobile device:
From the QA step, activate the by IP by enabling QA parameters
Click Share link.
Copy the link and send it to your mobile device.
Click the link. OR
Choose the option "Open QA Assistant on mobile"
and scan the QR code with your mobile device.
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.
🚩 Heads up
To access the QA Assistant on mobile, you must include the IP address of the mobile device used for the QA by enabling the IP Address parameter.
The sharing link can only be used once and has a validation limit of 8 hours. To generate a new link, click again on “Share link” from the QA step.
When opening the QA Assistant on a browser's emulator, make sure the zoom of the emulator is set at 100% in order to use the feature in the best conditions.
The QA Assistant on mobile displays two tabs that enable you to view and control various information on your website/page:
The campaigns tab is displayed by default and displays all campaigns that are live on the active page, whether you are assigned to them or not.
Each line, which relates to a specific campaign, displays the campaign type icon, the campaign name, the campaign ID and the overall status.
Icon
Status
On click
✅
Accepted
You can see the variation you are assigned to by clicking the campaign row. Then, you can switch to another variation by clicking Switch variation.
❌
Rejected
You can see the details of the targeting configuration (page URLs, Segment and Trigger) with the exact values you configured in AB Tasty and understand why you are rejected.
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
Overall status: general status of the campaign on the session, the global result of the previous criteria
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.
🚩 Heads up
For iPhone devices, since the iOS15 update, Safari automatically blocks/hides IP addresses to websites. As a consequence, you will see the “QA Rejected” status in the QA Assistant even if the QA conditions are met. To avoid this, go to your Safari settings > ‘Hide IP Address’ > ‘Off’. AB Tasty will then be able to read the IP addresses and affect the visitor to the campaign.
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
The 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.
Only events triggered when the QA Assistant is opened will be stored and displayed into the QA Assistant interface.
You can clear the events list by clicking on the “Clear history” button.
Using the QA Assistant on mobile devices can be useful in the following cases:
You want to check that the modifications, targeting and trackings of your campaign have been implemented correctly on mobile devices before pushing it live.
You want to know which campaigns are currently running on a specific page of your mobile website and their targeting conditions.
You want to understand why you don’t see a specific test on your mobile page. You can quickly see why you don’t match the targeting conditions, before changing the targeting section of your campaign.
If you have trouble opening the QA Assistant, please refer to .