The Frosmo Platform changelog tracks both main releases and maintenance releases, starting with Elephant Point. The changelog provides summary information about the changes in each maintenance release. The changelog also lists the platform component versions in each main and maintenance release.

The releases are listed in descending order by date, with the latest release on top.

For detailed information about the main releases, see the Frosmo Platform release notes.

For detailed information about the Graniitti API changes in each release, see the Graniitti API developer guide.

Frosmo Platform releases

Maintenance release (2019-11-11)

Improvements

In the Control Panel:

• Simplified the workflow for defining segments for a modification. The new workflow runs as follows:

  1. In the Basic settings view, click Define segments.
  2. Click Select segments or Select more segments, depending on whether you already have segments selected.
  3. Select the segments, and click Select.
  4. Select whether visitors should be included in or excluded from the selected segments.
  5. Click Save.

  For comparison, here's the old workflow:

  1. In the Basic settings view, click Define segments.
  2. Click Create segment combination.
  3. Select whether visitors should be included in or excluded from the selected segments.
  4. Click Select segments.
  5. Select the segments, and click Select.
  6. Click Save.

• You can now define a Preview URL for a placement. The URL is used for previewing the variations of modifications that use the placement. The URL must be the absolute URL of a page for which the placement is valid.

  

Bug fixes

In the Control Panel:

• Fixed a bug in templates where template content was not added to the custom script if the export was set to Automatic and the template was added to a modification before activating the modification.

Platform component versions

Maintenance release (2019-11-04)

Improvements

In the Control Panel:

• On the modifications overview page, in the multi-selection menu bar, removed the Statistics button, added the statistics download functionality under the Analyze menu as the Download report option, and renamed the menu to Statistics.

  

• For placements, increased the maximum length of the target element selector from 256 to 512 characters.

Platform component versions

Maintenance release (2019-10-28)

This release only includes Frosmo-internal improvements.

Platform component versions

Maintenance release (2019-10-14)

Improvements

In the Control Panel:

• The Export option for modification templates now has three  possible values:
  • Automatic: The template is automatically added to the custom script of the site if the template is used in an active variation of an active modification. This is the default value.
  • Always: The template is always added to the custom script.
  • Never: The template is never added to the custom script.
• Removing a workspace now also removes all the content of that workspace (modifications, placements, templates, triggers). This does not affect content used in production.

In Frosmo Core:

• Trigger rules now support matching against Boolean values when the rule contains a value defined as "is exactly true" or "is exactly false".

  

In the Preview Tool (Frosmo Preview):

• When you select a modification to preview, the variation selected by default is now the one with the lowest ID number (normally, variation 1). You can select another variation to preview from the Variation drop-down menu.

Bug fixes

In the Control Panel:

• Fixed a bug where, if you used a production trigger in a workspace placement, and then removed the workspace without first explicitly removing the placement from it, the trigger could no longer be removed.
• Fixed a bug where, if you created a placement in production with a trigger attached to it, and then added the placement to a workspace, the attached trigger was not automatically added to the workspace.

Platform component versions

Maintenance release (2019-10-07)

Improvements

In the Control Panel:

• The Export option for modification templates is now enabled by default, when you create a new template. This means that the template is automatically added to the custom script of the site if the template is used in an active modification.
• The modification statistics tables now show the variation title along with the performance statistics, making it easier to compare variation performance.
• In workspaces, the maximum length for a workspace title is now 128 characters instead of 32 characters.
• Previously, when a site had single-page application (SPA) support enabled and a page change event occurred, the order for evaluating segmentation rules and requesting modifications from the server was different than on a normal page load. Now, the order is similar regardless of whether the page is in a single-page application, or in a normal website.

In Frosmo Core:

• You can now use the frosmo.load and frosmo.ready events to verify that the Frosmo Core script has been loaded and successfully initialized. The following example shows how to add listeners to catch the events.

  window.addEventListener('frosmo.load', function () {
      var easy = window.frosmo.easy;
      easy.console.log('Frosmo Core has loaded (externally dispatched event)');
  });
  
  window.addEventListener('frosmo.ready', function () {
      var easy = window.frosmo.easy;
      easy.console.log('Frosmo Core is ready (externally dispatched event)');
  });

Bug fixes

In the Control Panel:

• Fixed a bug in triggers where, if you set the Evaluation point as Core event and the event type as Other predefined event and then entered the event name, the event name field disappeared from view.

Platform component versions

Maintenance release (2019-10-01)

Bug fixes

In the Control Panel:

• Fixed a bug where, if you tried to duplicate a placement, nothing happened, and the placement was not duplicated.

Platform component versions

Maintenance release (2019-09-23)

Improvements

In the Control Panel:

• When you open a template for editing, the editor now shows which modifications currently use the template.
• If you rename a template, the new name is now automatically updated to every modification variation that uses the template.

In Frosmo Core:

• If a trigger has an alias, when the trigger is fired, Frosmo Core now also sends the trigger data with the alias event. The alias event contains the same data as the trigger.fire event for the trigger. For example, if a trigger has the alias productPush, when the trigger gets fired, Frosmo Core now sends the same trigger data with both the trigger.fire event and the productPush event.

Bug fixes

In the Control Panel:

• Fixed a bug where, if you tried to remove a template that was used in one or more modifications, the UI did not display a proper message about why you could not remove the template.
• Fixed a bug where, if you tried to remove a production placement that was used in a workspace modification, the operation failed even if the workspace and therefore the modification had been removed.

Platform component versions

Maintenance release (2019-09-16)

This release only includes Frosmo-internal improvements.

Platform component versions

Maintenance release (2019-09-09)

Improvements

In Frosmo Core:

• If the data layer module is initialized for a site, Frosmo Core now automatically initializes the data layer on page load by creating an empty window.dataLayer array. If the array already exists on the page, Frosmo Core uses the existing variable.

Bug fixes

In the Control Panel:

• Fixed a bug in workspaces where a workspace modification sometimes failed to display in preview mode if the workspace placement for the modification was created from a production placement.

In Frosmo Core:

• Fixed a bug in segmentation where a visitor assigned to a segment in a mutually exclusive segment group was incorrectly removed from that segment. If the visitor completed an action that had previously placed them in a different segment in the same group, the visitor was removed from their current segment for that page load, leaving them in no segment in the group. The next page load placed them back to the correct segment. Now, the visitor correctly remains in their current segment.
• Fixed a bug in segmentation where defining a segmentation rule with a query selector matching a regular expression for any value (.) resulted in the visitor getting segmented without having any query selector in their page URL. Now, the visitor only gets segmented if their page URL contains the specified query selector (with any value).
• Fixed a bug in segmentation where URL changes in a single-page application (SPA) were not correctly registered, resulting in the visitor not getting segmented if a segmentation rule depended on a specific URL. Now, SPA URL changes are correctly caught, and segmentation based on those URLs works as expected.

Platform component versions

Maintenance release (2019-09-02)

This release only includes Frosmo-internal improvements.

Platform component versions

Maintenance release (2019-08-26)

Improvements

In Frosmo Recommendations:

• When retrieving most_viewed or most_converted recommendations with the Recommendations API, you can now filter the returned recommendations by only some of the request parameters defined in a recommendation configuration. You can define values for only those parameters by which you want to filter the recommendations, and leave the remaining parameters with empty values. Previously, you had to either define values for all the parameters or leave all the values empty. The following example request now returns recommendations for all shoes irrespective of their color, whereas previously the request would've failed unless you also defined the color or left both parameters with empty values.

  GET https://inpref.com/recoApi/v2/?method=multifetch&
      origin=shop_company_com&
      recos=[{
        "name": "Most viewed products",
        "params": {
          "type": "Shoes",
          "color": ""
        }
      }]

Platform component versions

Maintenance release (2019-08-12)

Improvements

In the Control Panel:

• When creating or editing a modification template, clicking Save no longer closes the editor. Instead, to close the editor, click Close. If you have unsaved changes in the editor, the Close button is replaced by the Cancel button, which discards the unsaved changes and closes the editor.

Platform component versions

Maintenance release (2019-08-05)

Improvements

In the Control Panel:

• You can now manually queue recommendation generation at any time, even if generation is already ongoing for a recommendation. This allows you to, for example, immediately regenerate a recommendation after changing its configuration, regardless of the current status of the recommendation. Previously, the quick menu option to generate a recommendation was disabled if the recommendation was already being generated.

Bug fixes

In the Control Panel:

• Fixed a bug where changes to a template were not correctly shown in the template editor unless you reloaded the template overview page after saving the changes. Now, if you edit and save a template, and then immediately edit the same template again, the template editor correctly loads the latest, edited version of the template.

Platform component versions

Maintenance release (2019-07-01)

This release only includes Frosmo-internal improvements.

Platform component versions

Maintenance release (2019-06-17)

Improvements

In the Control Panel:

• Made numerous minor usability improvements across the UI.

In Frosmo Recommendations:

• Made numerous minor improvements to enhance the back-end processes for handling recommendation data.

Platform component versions

Maintenance release (2019-06-03)

Improvements

In the Control Panel:

• For modification templates:
  • Updated the UI for improved usability and a new look-and-feel.  
  • Exporting a template is now enabled by default. Exporting the template adds the template content to the custom script of the site, which is mandatory for most modifications to function as expected.
• Made minor usability improvements across the UI.

Platform component versions

Maintenance release (2019-05-28)

Bug fixes

In Frosmo Core:

• Fixed a bug where trigger counts were not always saved correctly, which resulted in visitors not being segmented correctly. Now, the saving function is always called before the segmentation is evaluated so that any trigger-based segmentation works as expected.

Platform component versions

Maintenance release (2019-05-20)

Improvements

In the Control Panel:

• Improved the usability of the UI:
  • For modifications, in modification content settings, added a Select template button for variations. The button opens a modal window where you can search for and select the template you want to use with the variation. Previously, you had to know and manually enter the template name.
  • For templates, added search, expand/collapse, and sorting options to the templates overview page.
  • For all sliding modal windows, added a close button ("X") to the top left corner, next to the modal title. This button works the same as the Cancel button at the bottom of a modal window.
  • Made numerous minor adjustments and tweaks across the UI.
• Migrated all sites that still used the legacy segmentation UI ("V1") to use the new segmentation UI ("V2").
  • If your site has segments created with the legacy UI, the segments are still fully functional, and you can access them by switching to the legacy UI from the Settings menu on the Segments page.
  • For more information about the segmentation UI redesign, see the Lynwood release notes.

In Frosmo Recommendations:

• Updated the Product API to consistently select which product data attribute value to return if the same attribute occurs multiple times in the source product data. In the source data, the same attribute can be defined in the data field, in the promotionLabel field, and in its own, dedicated top-level field. In case of duplicate attributes, the order of preference for selecting which attribute value to return is as follows:
  1. data
  2. promotionLabel
  3. Dedicated field

Bug fixes

In the Control Panel:

• Fixed a bug in triggers where, if you selected the Data layer event evaluation point and the Event data rule for a trigger, the UI would not allow you to manually enter property names such as ["gtm.elementId"]. Instead, you had to copy and paste these name values to the property name field. You can now enter such values normally.

Platform component versions

Maintenance release (2019-05-13)

Bug fixes

• Fixed a bug where, if you removed the segment combination defined for a modification, the change was not saved and the modification was still displayed only to the visitors in those segments. Now, if you remove the segment combination defined for a modification, the modification is displayed to all visitors.

Platform component versions

Goodnews Bay (2019-05-06)

Release notes

Platform component versions

Maintenance release (2019-04-08)

Improvements

In the Control Panel:

• Added short instructional videos for placements and segments. If you have no placements/segments created, the video is shown on the placements/segments overview page. If you have one or more placements/segments, you can find the video in the help text.
• Updated the placements UI for improved usability and a new look-and-feel. The new UI provides the same functionality as the old one.
• For modifications, updated the placement selection drop-down menu to a button that opens a modal window where you can search for and select the placement, and view information about the available placements.
• For triggers, added the Data layer event evaluation point. Use this evaluation point to fire triggers every time a data layer event occurs on a page.
• For triggers, updated the Event data rule:
  • Added support for property names that contain one or more periods.
  • Added automatic normalization and trimming for the property name on save.
  • Added a tooltip with detailed instructions and a dynamically generated example of the expected event data object.
• Made numerous minor usability improvements across the UI.
• Discontinued official support for Internet Explorer. For a list of supported browsers, see Technical overview.

In Frosmo Core:

• For triggers, added support for the Data layer event evaluation point.

In Frosmo Recommendations:

• Updated the Recommendations API to version 2. While deprecated, version 1 remains accessible, and requests that use version 1 work normally. For more information, see Recommendations API.

Bug fixes

In the Control Panel:

• Fixed a bug in password creation where the UI did not accept a password with one or more special characters but no numbers. The UI now correctly accepts passwords that contain at least one number or one special character.

Platform component versions

Maintenance release (2019-03-11)

Improvements

In the Control Panel:

• Increased the maximum size of modification template content to 512 KB (524 288 characters). If a template exceeds this limit, the Control Panel displays a warning and does not allow you to save the template until you reduce its content size to conform to the limit.
• In modification analytics, advanced tracking events are now sorted in ascending order by variation ID.

In Frosmo Recommendations:

• Improved the scheduling process for generating recommendations. This fixes the issue where the recommendation status (returned by the Graniitti API and visible in the Control Panel) did not always reflect the actual state of the generation.

Bug fixes

In the Control Panel:

• Fixed a bug in modification analytics where the advanced tracking statistics were not updated with event data when switching from a time period that had no events to a time period that did have events. The statistics view continued to incorrectly display a message that there are no events for the selected time period.
• Fixed a bug in segment settings where a conversion, product purchase, or product view segmentation rule did not display the product name when a single product was selected.

Platform component versions

Maintenance release (2019-02-27)

Bug fixes

In Frosmo Core:

• Fixed a bug where API calls related to advanced tracking were not sent on the next page load in case they failed on the previous page load.

Platform component versions

Maintenance release (2019-02-25)

Bug fixes

In the Control Panel:

• Fixed a bug where the Data Management > Segmentation section was not visible in the navigation menu after changing from one site to another.

In Frosmo Core:

• Fixed a bug where calling the datalayer.push() function in the browser console returned an undefined value instead of the original return value.

Platform component versions

Maintenance release (2019-01-23)

Bug fixes

In Frosmo Core:

• Fixed a bug where Google Analytics tracking events were triggered before the required tracking ID was registered, resulting in no tracking events being sent. This bug only affected sites that use multiple tracking IDs and where the required tracking ID gets registered after a long delay.

Platform component versions

Maintenance release (2019-01-14)

This release only includes Frosmo-internal improvements.

Platform component versions

Funny River (2018-12-03)

Release notes

Platform component versions

Maintenance release (2018-11-13)

This release only includes Frosmo-internal improvements.

Platform component versions

Maintenance release (2018-11-05)

Improvements

In the Control Panel:

• For workspace modifications, added the Resolve button also for cases where the original production modification is deactivated. For more information, see Publishing a workspace.

Bug fixes

In the Control Panel:

• For workspace modifications, fixed a bug where cached modifications were published from a workspace to production as basic modifications rather than as cached ones.
• For workspace modifications, fixed a bug where the Add existing modifications to workspace view did not retain your selection if you filtered the list of modifications so that your selected modifications were not shown.

Platform component versions

Maintenance release (2018-10-15)

This release only includes Frosmo-internal improvements.

Platform component versions

Maintenance release (2018-10-01)

Improvements

In the Control Panel:

• Updated the Graniitti API page to show the relevant Graniitti API URLs.
• Updated the product selector menu for segmentation rule settings to list products in descending order by update date and time.

Bug fixes

In the Control Panel:

• Fixed a bug where the UI allowed you to save only 999 values for a custom action.
• Fixed a bug where the workspace overview page incorrectly displayed the Resolve button for modifications.

Platform component versions

Maintenance release (2018-09-03)

This release updates the Graniitti API.

Platform component versions

Maintenance release (2018-08-27)

This release only includes Frosmo-internal improvements.

Platform component versions

Maintenance release (2018-08-23)

This release updates the Graniitti API.

Platform component versions

Elephant Point (2018-08-20)

Release notes

Platform component versions