Last updated
Was this helpful?
There are two ways to determine which campaign you are currently seeing and which variation you are assigned: by using the or your web browser’s console.
To launch the QA Assistant from the platform, follow these steps:
Go to the QA & Overview step of your campaign.
Click Open QA Assistant, the URL set up in the Main information step opens in a new tab. The QA Assistant opens via a panel at the bottom of your page. 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, but it will be minimized so you’re able to browse other web pages more easily.
Or directly from your website page:
Go to your website.
From the keyboard, press alt+Q+A (on Windows) or ctrl+Q+A (on a Mac): The QA Assistant opens via a panel at the bottom of your page.
The campaigns tab is displayed by default and is divided into two different sections:
The top section displays all campaigns that are live on the active page. These are the campaigns you are assigned to.
The bottom section displays all campaigns that are currently live on your website, whether you are assigned to them or not.
Each line relates to a specific campaign and displays the test type, the campaign name, the campaign ID, and the targeting configuration, including the following information:
Page URLs (Where): the page URLs where the campaign is displayed.
Segment (Who): the segment of visitors targeted by the campaign.
Trigger (How): the trigger that’s set up to launch the campaign.
QA mode: indicating whether the QA mode is enabled on the campaign.
On the right of each line, you can see the overall campaign status:
Here is how it looks like on the mobile version of the QA Assistant:
For example, here, we can see we’re rejected from our test and the reason is the QA. (You will be able to see every reason you are not affected to a test in the table below).
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 your current status for each targeting criterion and, if you are rejected, understand why you are not triggering the campaign.
From there, you can go to the Targeting step of your campaign in order to edit the targeting set. If you are looking for a specific campaign from the search bar, you can enter the campaign ID, campaign name, or campaign type.
To launch the QA Assistant from your browser’s console, follow these steps:
Go to the page you wish to verify.
Display the console (right click > Inspect Element or CTRL + shift + J in Chrome / F12 in Windows).
A navigation bar will open at the bottom or on the side of your screen.
Select the Console tab.
Example in Chrome:
Once the Console tab is open, you can enter various instructions (command lines).\
Entering the command ABTasty.results will return all campaigns that are live on the website, even if you are not on the page where they’re live. The status field will indicate whether you are seeing a campaign and, if not, why you are not seeing it.
Status
Explanation
“accepted”
You are seeing the test named above.
“target_pages_rejected”
You do not meet the targeting conditions configured on the targeting page.
"audience_rejected"
You were rejected from a specific test because you do not match the targeting criteria for the campaign. To see which targeting criteria you do not match, click the targeting object below in the console. Each targeting criterion added to the campaign is listed in that object and will display true if you match the criterion or false if you don’t match it.
“trigger_rejected”
You do not meet the targeting conditions of the trigger configured on the targeting page. Check what trigger has been set up to ensure you assign yourself to it correctly.
“pending”
Targeting is set with AJAX mode and is waiting for the element to be present on the page before applying. Alternatively, targeting includes geolocation, IP, weather, browser, device, or DMP criterion which has not yet been found.
“qa_parameters_rejected” or “QA rejected”
You do not meet the conditions configured in QA mode (IP address or cookie). Ensure the IP address entered is yours or that you have added the targeted cookie. Otherwise, refresh the tag and retry in a new incognito window (make sure to close all other browser windows).
“master_campaign_not_checked”
In personalizations or multipage tests that contain scenarios or subtests, there are two types of ID:
The ID of the global test, which will always be rejected
The ID of each subtest or scenario (which will usually be the global ID + 1 (e.g. if the global test ID is 675391, each subtest will have an ID of 675392, 675393, 675394, etc.)
Check the subtest ID because the global ID will always have the status "master_campaign_not_checked".
Example:
Entering the command ABTasty.getTestsOnPage() (parentheses are required!) will return all live campaigns on the page you are currently visiting if you match the targeting criteria.
Entering the command ABTasty.redirectedFrom will show you which redirection campaign has redirected you to the current page. This command is available once the redirection has been applied, not on the original page.
Example:
name: displays the name of the campaign you’re viewing
Type: displays the type of campaign – “ab” (which stands for a/b test), “personalization”, “multipage”, etc.
variationID: displays the variation you are currently seeing. “0” always refers to the original version. All other variations are indicated by a six-digit ID
variationName: displays the name of the variation you are currently seeing, as defined in the editor (default names are “Variation 1”, “Variation 2”, etc.)
Note: To learn more, refer to.
Example in Chrome:
If you don’t see a campaign listed here, you can use to understand why it’s not listed, by checking the status parameter.