Once you have defined targeting and before you launch the campaign and make changes accessible to users, you need to 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 decide to 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 Assigning yourself to a campaign.
If you cannot view your changes, it may be for one of the following reasons:
- The AB Tasty tag is out of date,
- There is a targeting error,
- You are assigned to the original version.
The AB Tasty tag is out of date
When you launch your campaign to run it through the QA process, the tag is updated automatically. However, if you make changes once the campaign has been started, the tag isn't updated automatically. If the tag is out of date, changes made to the campaign will not be visible in QA mode, even though changes have been saved on the interface.
In this case, click the green arrow button in the top right-hand section of the interface (all steps but the variation editor) to force a tag update. If on the variation editor, pause and play again the campaign from the left sidebar.
There is a targeting error
In production, you may not be assigned to a campaign at all. This is the case if the targeting criteria aren't met, for instance. The most frequent errors are often due to incorrect page targeting, to a targeted IP address which does not match your own, or to the fact that the targeted device differs from the one you are running the QA process on.
In this case, to correct these errors, return to the targeting step of your campaign and apply the following steps:
- Make sure the targeted IP address matches your own. If necessary, you may add several different IP addresses.
- Make sure the target pages coincide with the page you want to view.
- Make sure the targeted device (if applicable) coincides with the one you are using to run the QA process.
- Open a new private browser window or delete your cookies before refreshing the page.
To find out which campaign you are assigned to, enter the ABTasty.results command via the Chrome console. The list of campaigns is displayed, along with the variation you are assigned to.
Again, for more information, refer to Assigning yourself to a campaign.
You are assigned to the original version
In production, you may be assigned to the campaign’s original version, particularly if traffic allocation is set to a 50/50 ratio.
In this case, to avoid seeing the original version, set traffic allocation to 100% on the variation you want to see.
Once you’ve finished running the QA process, change the split traffic back to 50/50 in order for it to be evenly divided between the variations.
To find out which variation you are assigned to, enter the ABTasty.getTestsOnPage command via the console. The list of campaigns is displayed, along with the variation you are assigned to.
For more information, refer to How to make sure you are assigned to a campaign.
In most cases, if you cannot see your changes when using the QA mode, it is for one of these reasons. If this isn’t the case, the problem is due to the changes themselves (for instance if they weren’t made on the correct selector). In this case, please contact your dedicated CSM.