When configuring a test or personalization, there are 5 steps you need to follow before starting your campaign and making changes accessible to your users.
Targeting definition is step 3 of the campaign configuration process.
If necessary, you may also configure the visitors who will see your changes, i.e. your campaign “audience”.
Once targeting is complete, you can run the QA process for your campaign via the targeting configuration page.
The changes configured within your campaign are only visible to you, not your visitors.
However, your campaign will look just like it would for your visitors: check 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.
Displaying the targeting configuration screen
- From the dashboard, click , then 3 Targeting.
- From the variation editor, display the left-hand pane of the campaign and click 3 Targeting.
Running the QA process using versions 2.3 and earlier
Choose from 3 QA modes:
- Using the Preprod (preproduction) mode);
- Starting your campaign in Prod (Production) mode, having previously configured IP address targeting;
- Starting your campaign in Prod (Production) mode, having previously configured cookie targeting.
For more information, refer to QA a test before rollout.
Running the QA processes using versions 2.4 and later
In order to run your campaign through the QA process, you need to:
- Enable the QA mode option.
- Enable the Target an IP address or the Target a cookie setting, or both depending on your needs.
For more information, refer to Using the QA mode.