We'll show you how to publish an experience and what happens under the hood when you do that.
Once you have created and configured an experience and previewed it on-site, the final step is to launch in on your site.
When you are ready to go live with the experience, select Publish experience
Your experience will be live on your site in a few minutes and you'll now see it in your Live view.
Experiences are deployed onto the client site through the smartserve.js script. In this section, we will cover the process of how experiences are deployed and how to optimize the code for site performance.
When a new experience is published or paused, smartserve.js is re-published to the client site through our CDN. This can take up to five minutes.
When loaded, smartserve.js assesses whether a visitor meets the conditions for any segments linked to the experience. If they do, smartserve.js then assesses whether trigger conditions have been met. Only then will the visitor be served the experience.
When optimizing for performance, we recommend that customers are creative in the use of images and use CSS, where possible, in place of images. Where images are required, use the compressed or progressive JPEG file types.
For experiences with a requirement to minimize flicker and page load times, such as homepage takeovers and landing page tests, we recommend implementing smartserve synchronously.
Where possible, test builds should:
Qubit has developed a 'poller' that can be used to poll for elements on the page that are used as requisites for building personalizations.
See Polling for elements.
For experiences to run on QA and UAT sites, which are typically protected by a firewall, the following IPs need to be whitelisted: