Once you have defined targeting and before you launch the campaign and make changes accessible to users, you need to run your click trackings through the “QA process.
Running your click trackings through the QA process enables you to make sure click tracking is taken into account and visible in the campaign reports.
In a standard A/B test
To check that your click trackings have been deposited correctly in a standard A/B test, apply the following steps:
- Go to the Network tab.
- Check the Preserve log box in order for the data to be saved if you change pages.
- Filter using the datacollectAT command.
- Via the web page, click the tracked CTA.
- Via the Headers tab, click the highlighted link.
- Unfold the chevrons until you see the name of the CTA and the ID of the related test.
If click tracking wasn't deposited correctly, nothing will appear in the console when you click the CTA button. This can be due to a bad choice of selector during click tracking configuration in the variation editor.
In a redirect test
Click tracking works differently in the case of a redirect test because the page isn’t displayed in the variation editor.
If the selectors of the elements to be tracked are identical, the test will work just like a standard A/B test. However, if the selectors of the elements to be tracked are different (different IDs, class, div, etc.), you will need to deposit click trackings on both variations and give them the same name in order for them to be displayed in the same reports line.
To deposit click tracking in a redirect test, apply the following steps:
- Enter the URL of the page you want to redirect the visitor to in your browser.
- On the page, select the element you want to configure click tracking on.
- In the code, copy the matching selector.
- Return to the variation editor and open the click tracking configuration window.
- Select an element at random on the page and click Click tracking.
- Paste the selector you’ve copied from the console in the place of the selector you’ve selected.
- Enter a name for the tracking function (use exactly the same name as in the original version) and save.
To QA test the click trackings of a redirect test, follow the same steps as for a standard A/B test.
When you run checks in the console using the ABTasty.results function, it is normal for targeting to be rejected as the displayed page isn’t targeted.
To find out which campaign you are being redirected from, type the ABTasty.redirectedFrom command directly into the console. The campaign name is displayed.
Refer to the How do I set up a redirect test? support post for more information.