- Optimizely Web Experimentation
- Optimizely Web Personalization
Are you experiencing any of the following issues:
- You published your campaign, but do not see the personalized experience that you expect.
- Unsure if you are qualifying for an audience.
- You want to know if you are in the holdback of a campaign.
If you want to test unpublished changes in your campaign, see Preview mode and publishing in Optimizely Web Experimentation.
Check that the snippet is configured
First, check that the Optimizely Web Experimentation snippet is installed and configured to include Optimizely Web Personalization. See How the Optimizely Web Experimentation snippet works: Order of activation. You will do both of these things in the browser console.
- Load your page in a browser and open the developer console.
- Once the console is open, type optimizely. If it returns an object, Optimizely Web Personalization is enabled. If it returns an error, such as
optimizely is not defined, the snippet is not implemented correctly. See Implement the one-line snippet for Optimizely Web Experimentation.
- Check that the snippet installed synchronously at the top of the page. Make sure that the snippet is at the top of your <head> tag. See Implement the one-line snippet for Optimizely Web Experimentation.
- Make sure Optimizely Web Personalization is included in the snippet. In Optimizely Web Personalization, navigate to the Settings dashboard. Under the Implementation tab, toggle the drop-down list to Enabled.
Check that the snippet is up to date
Check the console log
If you run into issues during your QA process that you cannot easily diagnose, the Optimizely Web Experimentation log is a valuable resource. Think of the log as a way of "reading Optimizely Web Experimentation's mind."
You can also read about campaign activation in the developer documentation to learn how to search the console log and see if you are in the campaign.
- If you are in the campaign but you are not seeing the experience you expect, check if you are in the holdback. Not sure what a holdback is? See Six core concepts of Optimizely Web Personalization.
- If you are not in the campaign, check your URL targeting. See Target URLs to choose where your experiment runs.
Check the holdback
Are you not seeing a personalized experience because you are in a campaign holdback? Here is how to check.
In the console log, use the following methods:
- If the value returned is
true, you are in the holdback. So, not receiving a personalized experience is expected behavior. Try visiting the page again with an incognito browser.
- If the value returned is
false, you are not in the holdback. Next, check that you are qualifying for the audience you expect.
Check audience prioritization
Check your audience prioritization. If your campaign has multiple experiences, your prioritization setup determines which experience a visitor sees if they qualify for two or more audience.
In the console log, enter:
Then expand the array to see audiences prioritized from first to last.
- If audiences are prioritized incorrectly and the snippet is up to date, return to your campaign to check your audience setup.
- If the setup looks right but you are still not seeing the experience you expect, consider filing a support ticket.