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.
Before running the QA, make sure you are assigned to the campaign. For more information, refer to Assigning yourself to a campaign.
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 ariane.abtasty command.
- Via the web page, click the tracked CTA.
- Click the most recent Hit.
- In the Headers tab, go to the Request Payload section.
- Unfold the “h” chevron and the following chevrons until you see the name of the CTA and the ID of the related test.
If click tracking wasn't deposited correctly, the hit related to click tracking will not 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.
To implement a Click tracking in a redirect test, refer to Measuring the number of clicks on an element (Track clicks) in a Redirect test.
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.