Register today for Oracle CloudWorld. October 17th - 20th, Las Vegas

Register now

Hillel Cooperman, Senior VP of User Experience Design, has a message for you on Oracle CloudWorld

Watch now
Engagement Engine: Supports a combination of SPA and non-SPA pages — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Engagement Engine: Supports a combination of SPA and non-SPA pages

Accepted answer
16
Views
3
Comments
edited May 18, 2016 4:53PM in Communication Channels 3 comments

Content

I've been asked this question a few times and thought this information would be useful to the Community...

SPA=Single Page Application

Question:

If our company has a combination of SPA and non-SPA pages, can we still use the Engagement Engine to deploy rules?

Answer:

A company can have one (1) Engagement Engine account they use across both SPA and non-SPA pages; the only update to the implementation is that SPA pages must include the SPA version of the Engagement Engine page tag, and non-SPA pages can use the traditional version of the Engagement Engine page tag.

If a site contain a mix of non-SPA and SPA pages, the course of action depends on whether hash fragments or the HTML5 pushState method are used 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 (select) 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 (do not select) the "Website utilizes a single HTML page" checkbox, and should instead use the eeSPA flag when

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!