A trigger allows you to detect a particular event, such as a click, on a web page and take a predefined action based on that event. You can use triggers to define:

A trigger consists of two parts:

For example, you can configure a trigger to be fired when the Frosmo script is loaded (= evaluation point) and if the current page URL is www.frosmo.com (= rule). Or you can determine a trigger to be fired every time a visitor clicks a specific button (= evaluation point, no rules).

Selecting the correct evaluation point for the trigger is important, as it determines when or if the trigger gets fired.

To learn more about triggers, see:

How triggers work

The process for evaluating and firing a trigger on a page flows as follows:

  1. A visitor navigates to the page in their browser.
  2. The browser requests the page from the web server.
  3. The web server responds with the resources (HTML, CSS, and JavaScript files) for the page, and the browser starts building the page DOM.
  4. The browser loads the Frosmo scripts.
  5. The browser starts parsing and evaluating the Frosmo scripts.
  6. Frosmo Core initializes triggers defined for the site.
  7. Frosmo Core initializes all other features defined for the site.
  8. The browser completes parsing and evaluating the scripts.
  9. The browser renders the page, displaying it to the visitor.
  10. When the trigger evaluation point is reached and the trigger rules are met, the trigger fires on the page. This can happen even before the Frosmo scripts are fully evaluated, since a trigger can be bound to an event that occurs before the evaluation completes.

Triggers in the Frosmo Platform

Figure: Triggers in the Frosmo Platform

Where to go next