Support for Single Page Applications (SPAs)

Out of the box, Ascend supports dynamic content such as the content of a multi-step web form or a dynamic product detail page image. 

While Ascend currently does support Shadow DOM/virtualization based web applications, these implementations require additional Solutions Engineering oversight. Please reach out to your solutions engineering contact if you believe your site is a single page application.

How are Single Page Applications different from traditional websites?

On traditional websites, when visitors click links, the links generally lead to a new URL and load an entirely new page. In SPAs, the whole page doesn’t reload; instead, certain content is changed, loaded, and swapped out within the same page.

Think of the page like a sheet of stationery with a letterhead. In a traditional web page, each page would use a new sheet, even though the letterhead doesn't change; this leads to high waste. With SPAs, however, you use the same sheet all the time, write content under the letterhead, and erase it once you need the space for new content.

How does Ascend work in Single Page Applications?

When using Ascend on SPAs, consider that Ascend generally loads once per pageload, in the <head> tag of a page. 

Ascend's default activation mode presents a problem for SPAs: because the snippet is never reloaded when the visitor takes action, Ascend won’t re-check for URL Targeting or Audiences, and it won’t load any new variation code. Even if you see the URL changing, the whole page will not be reloading. Review the activation mode article to learn how to set up conditional or triggered activation of a page in your website funnel. 

 

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk