Pages

This document provides a technical overview of the architecture and key features of the Frosmo Platform. For a high-level introduction to the platform, see Introduction to the Frosmo Platform.

Frosmo Platform architecture

The following figure shows the main components and subcomponents of the Frosmo Platform architecture and the information flows between them.

Frosmo Platform architecture and information flows

Figure: Frosmo Platform architecture and information flows

For more information, see:

Frosmo JavaScript library

The Frosmo JavaScript library is the Frosmo presence in the front end. The library runs on top of a customer site in the visitor's browser, integrating the site with the Frosmo Platform. The library provides both the framework for the platform to operate on the site and Frosmo's custom solutions for improving the site. The library is platform-independent and can be used together with existing web application frameworks, such as Angular and React.

The Frosmo JavaScript library consists of two script files:

  • The Frosmo Core library implements the core functionality and services of the Frosmo JavaScript solution. The library manages modifications and segmentation, collects usage data, and fetches modification content from the back end. The library is the same for all customers and sites.
  • The Frosmo custom script contains the configurations and custom code specific to a single site. These are used to modify the content and functionality of the site. The configurations include, for example, cached modifications, placements, segments, and triggers. The custom script runs on top of Frosmo Core and is unique to each site (or group of sites managed as a single site). Changes made to a site in the Control Panel are automatically reflected in the custom script for that site.

The browser loads the Frosmo JavaScript library through two <script> elements placed directly in a web page's HTML code. The first element loads Frosmo Core and the second one loads the custom script for the site. Apart from adding these two elements to every page on a site, no other changes are required to use the Frosmo Platform. For more information, see Setting up the Frosmo Platform for your site.

The Frosmo JavaScript library is optimized for fast loading. Frosmo Core is only 50 KB in size, while the custom script usually ranges between 16-32 KB. For more information about the Frosmo Platform and site performance, see Measuring and improving website performance.

The Frosmo JavaScript library is often referred to simply as the Frosmo scripts.

Script hosting and delivery

The Frosmo Platform uses content delivery networks (CDNs) to deliver the Frosmo JavaScript library and any Frosmo-specific media files used on websites. A CDN is a network of global servers connected to each other and used to store and deliver web content, such as images, videos, style sheets, and JavaScript files. When a visitor browses a site, the content of the site is delivered by the CDN server geographically closest to the visitor, decreasing page load time.

By default, the Frosmo JavaScript library files are delivered through Amazon CloudFront, which serves the files using the CloudFront servers closest to the visitor. Frosmo can also use other CDNs based on customer requirements.

The Frosmo Platform uploads the custom script and associated media files (ones added directly to modifications) to the CDN every time they need to be updated, that is, every time something on the site is changed using the Control Panel. The assets are always exported to CloudFront and, when needed, copied from CloudFront to other CDNs.

Frosmo data layer

Customers can use the Frosmo data layer to implement basic data tracking by themselves, rather than have Frosmo do it in the custom script.

The data layer allows you to pass information from a web page to the Frosmo JavaScript library. The library then sends the information to the Frosmo back end. The library can also use the information directly in the browser to, for example, display content or manage segmentation. The exact behavior depends on how the Frosmo Platform has been configured for the site.

You can pass information about the following events and items through the data layer:

  • Conversions
  • Custom actions
  • Products
  • Transactions

For more information about the data layer, see Frosmo data layer.

Frosmo Control Panel

The Control Panel is the main Frosmo application for customizing and monitoring websites. In a nutshell, the Control Panel allows you to:

  • Configure how the Frosmo Platform modifies content and segments visitors for a site.
  • Monitor how well the modifications and segmentation perform on the site.

The Control Panel is responsible for managing the Frosmo JavaScript library. Changes made to a site in the Control Panel are automatically reflected in the custom script for that site.

The Control Panel uses the Graniitti API to access the Frosmo back end, and to deploy the Frosmo custom script to the CDN.

For more information about the Control Panel, see Introduction to the Frosmo Platform and our user guides.

Graniitti API

The Graniitti API provides secure access to the data in the Frosmo back end. The API allows client applications to, for example, retrieve and create modifications, and retrieve usage data collected by the Frosmo Platform.

Customers can use the API to, for example:

  • Provide data to custom dashboards and management UIs.
  • Provide an outside access point to usage data that is collected and stored by the Frosmo Platform.

The API uses token-based authentication for all requests.

For more information, see Graniitti API.

Message API

The Message API retrieves modification content from the Frosmo back end, so that the content can be displayed in the browser. The Message API uses segmentation data and previous usage data to dynamically select suitable content for the visitor.

The Message API also tracks what content is shown to whom and how many times.

Optimizer API

The Optimizer API receives and stores usage data from websites. In other words, the Frosmo JavaScript library collects usage data in the visitor's browser and sends the data to the back end by calling the Optimizer API. In the back end, the Optimizer API stores the data for further processing.

To secure the data during transit between the site and the Frosmo back end, the Frosmo JavaScript library communicates with the Optimizer API over an HTTPS connection.

Custom APIs

A custom API is a customer-specific API created for a specialized purpose that cannot be realized using the other APIs or the Frosmo JavaScript library. Frosmo creates custom APIs as needed.

Custom APIs are typically used to:

  • Implement product recommendations based on product tracking data retrieved from the Frosmo back end or from a customer's feed, or both.
  • Return specialized data to the browser, such as data stored in a customer's back-end system or data read from a feed.
  • Send data to another service, such as email addresses to a mailing list for marketing automation purposes.

Frosmo Platform servers

The Frosmo Platform is hosted on multiple regional servers for improved availability. A customer's site is typically hosted on the server geographically closest to the majority of the site's visitors.

Frosmo has regional servers for:

  • Americas
  • Asia
  • Europe
  • Finland

Modifications

In the Frosmo context, a modification is a real-time change to a web page designed to improve the usability and user experience of the website and guide visitors to complete a conversion. For example, modifications can be used to improve the sales funnel of an ecommerce site, leading to an increased conversion rate. 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. The code can consist of HTML, CSS, and JavaScript, in any combination.

The Frosmo Platform can use the data stored in the browser's local storage and cookies, such as segmentation data, to determine which modifications to show to the visitor. Modifications can also use data stored in the Frosmo back end.

Here are some examples of common modifications:

  • Add new content, such as personalized product recommendations or content generated from data feeds.
  • Modify existing content, such as images or links.
  • Remove unnecessary content, such as distracting elements, site navigation elements in shopping carts, or surplus elements in mobile-optimized layouts.
  • Modify the layout and styling of a page.
  • Add custom JavaScript code that interacts with custom APIs.

Modifications are grouped into the following types:

  • Basic modifications are used for content that is retrieved from the Frosmo back end and displayed only after the browser has rendered the page.
  • Cached modifications are used for static content that must be inserted into the page code before the page is rendered in the browser. (Like with all modifications, the content is maintained in the Frosmo back end, but unlike with the other modification types, the content is inserted in full in the Frosmo custom script for fast access.)
  • Recommendations generate content from product data based on the visitor's previous behavior on the site.

Frosmo Platform administrators manage modifications in the Control Panel.

For more information about modifications and related features, see Modifications.

For information about how conversions are attributed to modifications, see Introduction to conversion tracking.

Data collection and storage

The Frosmo JavaScript library collects usage data in the visitor's browser and sends the data to the Frosmo back end over an HTTPS connection. The library sends the data in the background so as not to interfere with the visitor's user experience. The Frosmo JavaScript library also stores selected data locally in the browser.

The data can be categorized into:

  • Modification performance data
  • Product data
  • Server logs
  • Visitor data

By default, the Frosmo Platform collects and processes only anonymous and pseudonymous information about visitors and their behavior on a website. The platform does not collect data that in itself enables the identification of an individual data subject.

For more information about what data the Frosmo Platform collects and where the platform stores the data, see Data collection and storage.

Integration with external systems and services

The Frosmo Platform can integrate with other back-end systems and online services, such as analytics tools, marketing automation systems, and data management platforms (DMPs).

Integrations are typically used for synchronizing segmentation data between the Frosmo Platform and an external back-end system, or for using the collected usage data outside the site. Integrations also allow the Frosmo Platform to input data about displayed or clicked content directly into an analytics tool, such as Google Analytics.

You can integrate the Frosmo Platform with, for example:

  • Analytics tools. If you want to use a separate web analytics tool, you should integrate it with the Frosmo Platform, since changes made to your site with Frosmo are not, by default, included in 3rd-party web analytics tracking. Integration ensures that you have a clear understanding of what is happening on your site.
  • Marketing automation systems. The Frosmo Platform can gather and process segmentation and visitor data for marketing automation systems, which can then use the data to target the appropriate audiences. You can set up integrations with, for example, ad platforms and email services.
  • Data management platforms. As with many other systems, extracting useful data from DMPs can be laborious and requires the use of multiple APIs. The Frosmo Platform can be used as a master API, an interface for all data calls between a DMP and a site.

For more information about integrations, see System and service integrations.

Frosmo Platform security

The Frosmo Platform can limit user access to the Control Panel by IP address. This means that users can access the Control Panel only from the designated IP addresses and from Frosmo premises.

The Frosmo Platform can force all content that is provided through the Frosmo JavaScript library to a site to load resources only from specified domains. When this feature is enabled, the Frosmo Platform validates all modification content before it is saved to the Frosmo back end. If the content contains elements that could be used to load or inject resources from non-authorized domains, the content is rejected.

For more information, see Security overview.

Browsers and other software

For information about how the Frosmo Platform works with browsers and other software, see:

Supported browsers

The following tables list the officially supported browsers for the Frosmo JavaScript library and the Control Panel. Both may work on other browsers and browser versions as well, but Frosmo does not officially support these.

Table: Browsers officially supported by the Frosmo JavaScript library

BrowserVersion
Google ChromeLatest version
Internet Explorer (IE)10 or newer
Microsoft EdgeLatest version
Mozilla FirefoxLatest version
OperaLatest version
Safari8 or newer

Table: Browsers officially supported by the Frosmo Control Panel

BrowserVersion
Google ChromeLatest version
Microsoft EdgeLatest version
Mozilla FirefoxLatest version

Ad blockers and content filtering software

The Frosmo Platform is not on any known basic ad blocking lists.

Some filter lists and software block the Frosmo Platform, for example:

  • EasyPrivacy
  • F-Secure Freedome VPN (only when tracking protection is enabled, and only for pages that use HTTP)
  • Ghostery (when the "Beacon" category is selected)
  • Opera's built-in ad blocker (which uses EasyPrivacy)

Private browsing

The Frosmo Platform interprets an incognito browsing session as a new visitor. This means that no segmentation data or other data previously stored in the browser is available for the session. Each new incognito session is counted as a new visitor.

  • No labels