This guide is for developers who want to set up data tracking using the default data layer events supported by the Frosmo Platform. If your site has or is getting a basic feature setup from Frosmo, see the appropriate site preparation guide instead. Basic feature setups rely on their own dedicated data layer events.
To use the data layer on a site, the data layer module must be enabled for the site.
For an introduction to product tracking in the Frosmo Platform, see Data tracking solutions.
Tracking products with the data layer means triggering a product view event whenever a visitor navigates to a product page or otherwise views a product on a site. The data you pass in the product view event is the product data for the viewed product.
You can trigger product view events from:
- Page code (meaning directly from the site source code)
- Shared code
Page code is the recommended solution. If you cannot use the data layer in your page code, use shared code.
Figure: Tracking products by triggering a product view event from a page (click to enlarge)
When you trigger a product view event, how the Frosmo Platform handles the event and the products defined in the event data depends on the event's mode setting:
mode: 'set':- If a product is not in the product database, the platform adds the product to the database. The platform uses the product ID to uniquely identify the product.
- If a product is already in the product database, and if the event data differs from the product data in the database, the platform updates the data in the database. The platform only updates product attributes whose values differ and adds attributes that do not already exist in the database. The platform does not remove existing product attributes that are missing from the event data.
- If a product is already in the product database, and if the event data does not differ from the product data in the database, the platform ignores the event data.
- The platform does not increment the view count for the product.
mode: 'setView'(default):- If a product is not in the product database, the platform adds the product to the database. The platform uses the product ID to uniquely identify the product.
- If a product is already in the product database, and if the event data differs from the product data in the database, the platform updates the data in the database. The platform only updates product attributes whose values differ and adds attributes that do not already exist in the database. The platform does not remove existing product attributes that are missing from the event data.
- If a product is already in the product database, and if the event data does not differ from the product data in the database, the platform ignores the event data.
- The platform increments the view count for the product by one.
mode: 'view':- The platform does not save any data to the product database. Whether or not a product is already in the database, the platform neither adds nor updates the product data.
- The platform increments the view count for the product by one. Even if a product is not in the product database, the platform adds a view for the product ID in product statistics.
To verify that the tracked product data is correctly stored in the Frosmo back end, view the product data in the Frosmo Control Panel.
Triggering product view events
To trigger a product view event, call the dataLayer.push() function with the following object:
dataLayer.push({
frosmo: {
view: {
products: [{
/* Standard attributes */
id: '<product_id>',
availability: '<product_availability>',
brand: '<product_brand>',
image: '<product_image_url>',
name: '<product_name>',
originalPrice: <product_original_price>,
parentId: '<parent_product_id>',
price: <product_current_price>,
type: '<product_type>',
url: '<product_page_url>',
/* Custom attributes */
<key>: <value>,
...
}],
/* Optional */
mode: 'set|setView|view'
}
}
});
The frosmo.view object contains the event data.
view object
The view object contains the data of a single product view event.
Table: view object properties
| Property | Description | Type | Role |
|---|---|---|---|
products | List of viewed products. Define each product as a product object. You must define at least one product. If the list is empty, the platform ignores the event. | Array of product objects | Required |
mode | Set how the Frosmo Platform treats the event and event data. The possible values are:
The default value is If the site's product data comes exclusively from a product data feed, always set this to | String | Optional |
Product object
The product object contains the data (attributes) for a single product. You can define standard attributes and custom attributes for a product.
The Frosmo Platform automatically trims string values by removing opening and ending white spaces. Empty string values are valid for all string attributes except id.
Standard attributes
To get the most out of the Frosmo Platform, include as many optional standard attributes in your product data as possible.
Table: Product object properties (standard attributes)
| Property | Description | Type | Role |
|---|---|---|---|
id | Product ID. The value must be a non-empty string. | String (256) | Required |
availability | Product availability in the web store. The possible values are:
If you provide a value other than one of those listed, the data layer push fails, and no product data is updated. | String | Optional |
brand | Brand name for the product, or the company that produces the product. | String (2048) | Optional |
categories | Categories to which the product belongs. This can also be keywords, tags, types, or any other set of classifiers used on the site. You can define a hierarchy of parent and child categories as a breadcrumb using
The maximum stringified length for the array is 2048 characters. If you only need to define a single category for a product, use the Use either | Array of strings (2048) | Optional |
image | Product image URL. Even if you do not have a value for this property, it is recommended that you nonetheless pass an empty string. | String (2048) | Optional |
name | Product name. Even if you do not have a value for this property, it is recommended that you nonetheless pass an empty string. | String (256) | Optional |
originalPrice | Original unit price for the product. Use this property for the original starting price before any discounts. | Number | Optional |
parentId | ID of the parent product, if the current product is a product variant. If your site has a product feed that provides the baseline product data to the Frosmo Platform, you can omit this parameter or set it to If your site does not have a product data feed, and if you know the ID of the parent product, use this property to define the current product as a variant of the parent. If the parent product does not exist in the database, the platform ignores the product view event. Do not define this property if the product is itself a parent product. Parent products cannot have parents, and product variants cannot have variants. If you define a parent product ID that differs from the one already stored for this product in the database, the new ID overwrites the existing ID. For recommendation generation purposes, the platform calculates product variant statistics (views, conversions, transactions) for the parent product. Recommendations only return parent products (as they contain the combined statistics for a product). | String (256) | Optional |
price | Current unit price for the product, such as a discount price. Even if you do not have a value for this property, it is recommended that you nonetheless pass an empty string. | Number | Optional |
type | Product category. This can also be a keyword, tag, type, or any other form of classification used on the site. Define a hierarchy of parent and child categories as a breadcrumb using Even if you do not have a value for this property, it is recommended that you nonetheless pass an empty string. This property can be used in segmentation rules and therefore needs to have a value. If you need to define multiple categories for a product, use the Use either | String (256) | Optional |
url | Product page URL. Even if you do not have a value for this property, it is recommended that you nonetheless pass an empty string. | String (2048) | Optional |
Custom attributes
If the standard attributes are not sufficient to track your product data, define the necessary custom attributes to complement the standard ones. You can freely define as many custom attributes as you need for your products.
A custom attribute must meet the following requirements:
The attribute name must be a string with a length of 1-32 characters. If the name is empty or longer than 32 characters, the platform ignores the product.
The platform automatically trims leading and trailing spaces from the attribute name. The platform validates the length of the trimmed name.
The attribute name cannot be any of the following:
created_atfeed_updated_atupdated_at
These names are reserved for read-only attributes that the platform automatically creates and updates for a product. If you include any of these attributes in the product object, the platform ignores the entire product view event.
- The data type of the attribute value must be one of the following:
- Array
- Boolean
- Datetime string (ISO 8601)
- Number
- Object
- String
- The attribute value can also be
null. - The maximum length of the attribute value is 2048 characters. If the value is an array or object, the length is the JSON-stringified length of the array or object.
If the custom attribute is an object, the object properties can be anything you want them to be. The Frosmo Platform does not validate the properties against any data model or schema.
You cannot filter recommendation data by object properties. If you want to use a custom attribute for filtering recommendations, use one of the other supported data types.
Product view examples
Retail
iGaming
Testing product tracking
For instructions on how to test that products are correctly tracked on a site, see Testing data tracking.
Triggering product view events (deprecated method)
Do not use this method if you are preparing a site for integration with the Frosmo Platform.
This section documents the legacy method for tracking products with the data layer. This method is officially deprecated, and the documentation is no longer maintained. If your site still uses this method, it is recommended that you migrate to the current solution. Contact Frosmo support to discuss the migration.
