Creating a Target using the Advanced Editor
Targeting is where alternative experiences are delivered based on specific segmentation rules. The advanced editor can be used to generate sophisticated targets based on flexible rules that can deliver a fully personalised experience.
To Create a Target
To create a Target, highlight “Web Page” then “Target” and click on “Advanced Editor”
Project Name – Projects are containers for tests on the same location
Description – (Optional) but it is a good idea to add something here so you can remember exactly what this project is about
Project Location – This defines the pages that are in scope for the project. Locations can be defined using the Location Manager. Click in the field to select an existing location
Manage locations – Click here to generate a new location. Locations can be defined as single or multiple URLs or Regular Expressions to URLs that match a pattern.
Test Alias – The test Alias is a label used to address the specific project. It is automatically generated by Optimize, but can be edited if necessary
Target Details – this moves you on to the next stage
Once you have completed the form and you have clicked on the test details button you will see the Target Details Screen
Test Details Screen
Test Name – Provide a name for your test
Description – (Optional) Once again add a description to make it easier to understand later
Pre-Rendering Script – (Optional) Click on this button if you want to execute any Jscript across all variations before the page has loaded. For example, you may want to load any coding libraries or define functions that are relied upon when transforming or tracking
Variation – For target projects, a minimum of two variations is required. Each variation will require a name e.g “Control” and “Experiment 2”. You are able to nominate either variation as being the control for reporting by clicking on the radio button.
- Give the Default content a name
- Add a variation Segment
- Search for existing segments
- Add additional Variations
Variation Script – In this flyout, enter the script to be executed when the visitor is exposed to this variation. Typically this would be the code used to transform the page/ experience.
Post-Rendering Script – In this flyout, enter any additional script to be executed across all variations once the page has loaded. Typically this would contain the script used for tracking visitor engagement.
Add Pre and Post rendering scripts as required. Select “Audience” to control the overall audience exposure to the targeting rules and “Goals” to track progress.
Targeting rules are processed in order. If rules are not mutually exclusive, then the 1st rule that the visitor qualifies for is allocated. If a visitor does not qualify for any of the rules then they are served the “default content”.
Unlike Tests where the user experience is persistent upon qualification, target rules are evaluated on each pageload allowing visitors to move between segments.