A single page application (SPA) is an application where the page loads only once on the visitor’s web browser. An SPA is fully loaded on the initial page load and then page regions are updated with new page fragments loaded from the server on demand.

Normally, Engagement Engine carries out the site evaluation and loads the rules for a page on page load. As the page load happens only once with an SPA, this means that a different approach is required when using Engagement Engine with an SPA. For an SPA, the initial site evaluation and loading of rules is performed when the page loads. Subsequent site evaluations and loading of rules are performed when the hash fragment changes, or when you use the HTML5 pushState method.

You can set Engagement Engine to work with an SPA by clicking on the Settings button in the navigation bar, checking the Website utilizes a single HTML page check box and clicking on the Save button. This is an account level setting and instructs Engagement Engine to treat each of your sites as an SPA.

If your sites contain a mix of non-SPA and SPA pages, your course of action depends on whether you are using hash fragments or the HTML5 pushState method on the non-SPA pages. If you are not using hash fragments or the HTML5 pushState method on the non-SPA pages, then you should check the Website utilizes a single HTML page checkbox and click the Save button. If you are using hash fragments or the HTML5 pushState method on the non-SPA pages, then you should not check the Website utilizes a single HTML page checkbox, and should instead use the eeSPA flag when adding your page tag to the SPA pages.

For more information on using the eeSPA flag, please refer to the Page Tag Modifications section of this document.

Note: Changing the Website utilizes a single HTML page setting instructs Engagement Engine to perform an auto-publish for each of your sites. This ends any A/B tests that are currently active.