In the Frosmo Platform, a modification is a real-time change on a web page designed to personalize or otherwise improve the user experience or usability of a website and guide visitors to complete a conversion. In technical terms, a modification is a managed piece of code that changes the content, appearance, or behavior of a page directly in the visitor's browser. Personalized modifications are based on the visitor attributes that can be either rule-based (segmentation) or data-based (machine learning algorithms). You can also use modifications to collect usage data from the site.

Here are a few examples of common modifications:

You define modification content (HTML, CSS, JavaScript) in the Frosmo Control Panel. The only tool you need is a browser running the Control Panel. You can create content templates that allow you to define content once and then reuse that content across multiple modifications. Optionally, you can customize the content for each modification based on content options defined in the templates.

Before you start working with modifications, see:

How modifications work

A modification configuration defines all the settings for a modification. The configuration determines the who, where, what, and when of displaying a modification.

The main parts of the configuration are:

The configuration can also have additional conditions, such as:

Modification flow

This is how modifications work in the visitor's browser:

  1. The visitor navigates to a page.
  2. The browser starts loading the page.
  3. The browser loads the Frosmo scripts, allowing the Frosmo Platform to interact with the page.
  4. The platform checks if there are any valid placements for the page.
  5. If there are valid placements, the platform checks if the placements have modifications assigned to them and whether those modifications are valid for the current visitor.
  6. If the placements have valid modifications, the platform retrieves the content of the modifications (either from the back end or directly from the custom script) and then renders the content to the page.
  7. The browser finishes loading the page.

Figure: Frosmo Platform interaction with a website

In the page code, the content of a modification gets rendered as follows:

Where to go next