Once you have defined targeting and before you launch the campaign and make changes accessible to users, you can run it through the “QA” process.
Running your campaign through the QA process enables you to view it in the same conditions as your visitors will. This way, you can make sure that visual changes are displayed correctly, that targeting criteria are complied with and that click tracking is taken into account and visible in the campaign reporting section.
When you check that your variations apply correctly to all browsers, you may not be assigned to your campaign or to all your variations. For more information, refer to Checking why you are not assigned to a campaign or variation.
Making sure you are assigned to the campaign and running checks
Use the ABTasty.results and the ABTasty.getTestsOnPage() commands to find out which campaign and which variation you are assigned to.
To access the console, apply the following steps:
- Open a private browser window.
- Enter the URL of the page you have targeted and want to check.
- Right-click and select Inspect:
The console is displayed.
To find out if you are assigned to a campaign or variation, apply the following steps:
- From your browser console, copy and paste the following commands:
- ABTasty.getTestsOnPage(): displays the list of campaigns you are assigned to.
- ABTasty.results: displays the list of campaigns in progress on the website, which you therefore aren’t assigned to.
If you aren't assigned to the campaign, the main results displayed in the console are as follows:
- Url_rejected: the issue stems from URL-based targeting. Either you aren't on the correct URL (this can be related to the https or to the URL settings) or the condition isn’t met.
- Targeting_rejected: the targeting conditions, other than the URL, aren't met.
- Missing_data: the reason depends on the website. This can happen on Ajax coded pages, for instance.
For more information, refer to Checking why you are not assigned to a campaign or variation.