1. Help Center
  2. Build
  3. Create a Client-Side Campaign

Personalizing your Visual Editor campaign

SiteSpect's Visual Editor allows you to make many changes to your webpages to update its visual appearance. In the default state these experiences are designed to be shown to all users but it is possible to include criteria to target these to specific groups of users or behaviours.

 

Build your Visual Editor Campaign:

1) Open your site in SiteSpect's Visual Editor.

2) Navigate to the page(s) that contain the element you wish to modify using Go To Page, Preview mode or right click 'Click Element' for the Visual Editor.

3) Hover over the element(s) you wish to update and select it with a left click. Once selected the element will have an orange border. A right click within this border will present you with options to modify the element.

4) Select the Edit options you need to make the changes you require. This can be as simple as a single HTML edit, text change, style change, image swap, element reorder or hide.

5) Alternatively you can layer multiple edit methods together, across multiple pages to build the experience you need. Utilising Page Categories in SiteSpect will enable you to target your changes to specific page groups or templates.

6) It is possible to have multiple variation groups within your Visual Editor campaign which can be added in the AB Build Flow before launching the Visual Editor.

7) Once you have completed your changes in the Visual Editor save them using the SAVE button in the top right of the page. Once the save is complete the button copy will update to SAVED to reflect this.

8) It is now safe to exit the Visual Editor back to the AB Build Flow.

 

Adding Criteria to Personalize your Visual Editor Campaign:

Audiences can be used to manage which users are exposed to your Visual Editor campaign. These criteria can be applied from the Audience section within the AB Build Flow once you have SAVED and EXITED the Visual Editor. 

The audience section references your library of existing audiences to include or exclude specific user types and can be searched by name or tag. An audience include combines audiences with an AND operator while exclude uses an OR. If you need to include two of the same audience type they should be defined as a single audience. E.g. UK + US rather than UK AND US.

Should you require a new audience there are 19 or so types ranging from cookies, entry URLs, concurrent campaign assignments, geo location, device type, browser type, user agent, time and many more here. These can be defined within the audience library or by selecting New > Create Audience from the left hand navigation.

It is important to consider that SiteSpect audiences manage campaign assignments. This means audiences are analyzed at the beginning of a users session and applied equally to all variation groups in the campaign. Successful audience assignments then become sticky for the user while that campaign remains active. This means that the audience criteria must be available on the users landing page in order to work effectively for the campaign. 

In the example below we are targeting US Smartphone users who are subscribed to our newsletter but excluding anyone on an iphone device.

 

Query Parameters can be used to manage landing page experiences for specific user types based on the parameters they arrive with. These can be applied from the Variation section with triggers in the AB Build Flow once you have SAVED and EXITED the Visual Editor. 

There are three campaign trigger types that are commonly used to define a query parameter:

Query parameters should only be used to apply changes on the landing page where they are presented. If changes are required later in the users journey then using audiences (e.g. entry URL) is preferable to make the change sticky to the users sessions. Unlike audiences it is possible to apply different query parameter triggers across different variations.

 

  1. In order to apply a change for a specific query parameter, make the change in the Visual Editor you require and return to the Variation section of the AB Build Flow.



  2. Select a trigger type for your change to enable you to specify a query parameter related to your variation change. In the example below the shoes landing page hero image is being replaced with one for sneakers when a user arrives with a sneakers query parameter. This has been applied in a URL Path trigger.



  3. Once your first variation is set up for your query parameter you can simply duplicate this using the Make A Copy button on the right hand side of the variation.



  4. In the duplicated variant update the variant name, trigger parameter and ‘replace with this’ to customize the variant to the parameter. In the example below the shoes landing page hero image and parameter are updated for boots instead of shoes or sneakers.



  5. This process can be continued in additional variant duplicates until all the scenarios have been covered.

     
  6. If you are unable to host the images you can use SiteSpect file storage to do this for you.
  7. Save the campaign with the newly duplicated variants and query parameters. Use SiteSpect Preview to QA and confirm the changes apply as expected.

 

Personalization Metrics can be used to incorporate user behaviours to manage when experiences are displayed in SiteSpect.  These can be applied from the Variation section with triggers in the AB Build Flow once you have SAVED and EXITED the Visual Editor. Specifically the Visitor Behaviour trigger option.

 

To enable a metric in SiteSpect for Personalization it must first be set to ‘Use in a Campaign Trigger or Audience to personalize the Campaign’ which can be found at the bottom of each individual metric page.

  Personalisation Metric1

 

  1. In order to apply a change for a specific personalization metric, make the change in the Visual Editor you require and return to the Variation section of the AB Build Flow.



  2. Select a trigger type of Visitor Behaviour from the dropdown.
  3. Choose the option of metric or custom variable depending on how your personalization metric is configured.
  4. Select the name of the data point you need. In the example below this is the Shoes = Sneakers metric.
  5. Define if the personalization data point should be cross session (user level) or in session (visit level).
  6. Outline the minimum and maximum hits and time elapsed for that metric to customize the behaviour you wish to target.
  7. You can add multiple triggers of any type including additional personalization metrics into your variation using the AND OR boolean operators. 



  8. Once your first variation is set up for your personalization metric you can simply duplicate this using the Make A Copy button on the right hand side of the variation.



  9. In the duplicated variant update the variant name, trigger metric and ‘replace with this’ to customize the variant to the personalization metric. In the example below the shoes landing page hero image and trigger metric are updated for boots instead of shoes or sneakers.



  10. This process can be repeated in additional variant duplicates until all the scenarios have been covered.
  11. If you are unable to host the images you can use SiteSpect file storage to do this for you.
  12. Save the campaign with the newly duplicated variants and personalization metrics. Use SiteSpect Preview to QA and confirm the changes apply as expected.