By default, all Ascend experiments evaluate and render as soon as the Ascend snippet has been loaded on the page, which means that a visitor must match a target URL path, audience segment, and meet traffic allocation rules. Once a visitor is bucketed into an experiment, the actual code to change any elements on the page will run as soon as those elements appear in the DOM.

There are times, however, in which a user may want to delay the rendering of experimental treatment until a certain state has been reached within an application. The Ascend activation mode allows users to set up an experiment to only render page-associated elements when an API call is made.

Why would you use Manual Activation Mode?

  • You are able to deploy the Ascend API call code to your site and would prefer calling activate from within your native JavaScript for finer-tuned control
  • Your site is set up such that experiments need to be manually activated at some time after Ascend loads
  • A very specific action must be taken on the page to activate an experiment, and that action can only be captured from within your site's native code

Some example use cases:

  • You are using a multi-step form, and navigating the form does not load a new page.
  • You are running a scroll-depth based experiment.
  • You run an ecommerce site and would like to run an experiment only when a customer updates their shopping cart.
  • Your site is built using a single page application framework, like Angular, Ember, or KnockoutJS. We currently do not support React applications out of the box, or any other framework utilizing a shadow DOM.

Triggered Activation Mode Configuration:


Once a page has been set up to use manual activation, the elements assigned to that page will not render until the activation call has been made on the client.

Did this answer your question?