🛠️ [Troubleshooting] Checking if a page is assigned to a campaign

⚡	The following command lines/instructions are compatible with any version of the AB TAsty Generic Tag from 3.0 onwards.

You can determine which campaign you are currently seeing and which variation you are assigned via 2 methods:

• By using the QA Assistant
• By using your web browser’s console

Checking with the QA Assistant method

You can launch the QA Assistant from the platform: 

1. Go to QA & Overview step of your campaign
2. 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, like that you will be able to browse other web pages.

Or directly from your website page: 

1. Go to your website
2. From the keyboard, type alt+Q+A (for Windows) or ctrl+Q+A (for 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, that is to say 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, which relates to a specific campaign, 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 based on which the campaign is launched.
• QA mode: whether the QA mode is enabled on the campaign or not.

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

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 your current status for each targeting criteria and, if you are rejected, understand why you are not affected to 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.

Learn more on how to use the QA Assistant on desktop and on mobile.

 

Checking with the web browser’s console method

1. Go to the page you wish to verify.
2. Display the console (right click+Inspect Element or CTRL+MAJ+ J in Chrome or F12 in Windows).
   A navigation bar will open at the bottom or on the side of your screen.
3. Select the Console tab.
   Example in Chrome: Once the Console tab is open, several instructions (command lines) can be entered. 

ABTasty.results

ABTasty.results will return all campaigns that are live on the website, even if you are not on the right page. In this case, the status will specify if you are seeing a campaign or not, and if not, why you are not seeing it.

 

These following statuses may apply:

Status	Explanation
"accepted"	You are seeing the test, the name of which is mentioned above.
“target_pages_rejected”	You do not enter the page URL(s)s targeting conditions configured from the targeting page.
"audience_rejected"	You are being rejected from a specific test because you do not match the targeting criteria added to the campaign. To see which targetings you do not match, click the targetings object listed below in the console. Each targeting criterion added to the campaign will be listed in that object and will return true (if you match the criterion) or false (if you do not match the criterion).
“trigger_rejected”	You do not enter the targeting conditions of the trigger configured from the targeting page. Check what has been set up to be sure you assign yourself to it correctly.
"pending"	Targeting is set with AJAX mode and still waiting for the element to be present on the page before applying; or targeting includes a geolocation, IP, weather, browser, device, or DMP criterion which has not yet been found.
“qa_parameters_rejected” or “QA ejected”	You are not part of the conditions configured in QA mode (IP address or cookie). Make sure that the entered IP address is yours or that you have added the targeted cookie. Otherwise, refresh the tag and try again in a new incognito window (make sure only one window is open).
“master_campaign_not_checked”	In personalizations or multipages test that contain scenarios or subtests, we have two types of IDs: The ID of the global test that will always be rejected The ID of each subtest or scenario (which will generally be the global ID + 1 (example with a global test ID = 675391, each subtest will have as ID 675392, 675393, 675394 ...) You have to look at the subtest ID because the global ID will always have the status "master_campaign_not_checked".

Example:

ABTasty.getTestsOnPage()

ABTasty.getTestsOnPage() (parentheses are required!) will return all live campaigns on the page you are currently visiting and for which you match the targeting criteria.

Example in Chrome: 

If a campaign that should be listed above is not, you can use ABTasty.results to understand, thanks to the status parameter, why you are not seeing it. 

ABTasty.redirectedFrom

ABTasty.redirectedFrom will return from which redirection campaign you have been redirected from if this is the case. This instruction is available once the redirection has applied, not on the original page.  

Example: 

Understanding the other parameters

• name: name of the campaign you are looking at.
• type: will return the type of campaign (ab - which stands for a/b test -, personalization, multipage, etc.)
• variationID: will return the variation you are currently seeing. 0 always relates to the Original. Any other built-in variation is a 6-digit ID.  
• variationName: will return the name of the variation you are currently seeing, as defined in the editor (default names are always "Variation 1", "Variation 2", etc.)/