...

• Updated the validation for recommendation configurations (/sites/<site_id>/recommendations) whose type is bundle_converted, bundle_viewed, or bundle_viewed_converted: The API now expects a bundle configuration to contain an options property field with a product_attrs child propertyfield, which is used for filtering the generated recommendation data by a product attribute.

...

• In recommendations (/sites/<site_id>/recommendations), updated the requirements for recommendation configurations based on the built-in recommendation types:
  • For the most_viewed and most_converted recommendation types:
    • If there are segment IDs defined in the options object, you can only filter recommendation data based on those segment IDs (not by any segment ID, as before).
    • You no longer need to define parameter values in the params property field. You can pass an empty string as a value. However, you must define at least one parameter (even if it's value is an empty string). 
    • The number of parameters defined in the params property field must match the number of attributes defined in the product_attrs property  field of the options object. If there are segment IDs defined in the options object, there must be an additional parameter for the segment ID included in the params property field.
    • If the category_delimiter property field is defined in the options object, the type product attribute must also be defined in the product_attrs property field.
  • The bundle_converted, bundle_viewed, and bundle_viewed_converted recommendation types only take a single parameter in the params property field.
  • The value property field of the data point object has been deprecated.

...

Improvements

• Added the status property field to the objects returned by the /sites/<site_id>/positions/<position_id>/messages endpoint. The status property field indicates the status of the corresponding modification: active, inactive, invalid, past, or upcoming. The Frosmo Control Panel uses the status property field in the Edit placement view to list the modifications that use the placement by modification status.

...

• Migrated all existing production modifications to use the segment_rules property field in place of the contexts.segments and contexts.segment_criteria properties for defining their segment rules. The contexts.segments and contexts.segment_criteria properties are no longer used by any production modification. For more information about this change, see the changelog entry for version 0.43.0.

...

• Added support for the segment selection feature for modifications, which combines selecting segments and defining a segment combination into a single workflow in the Frosmo Control Panel:
  • All new modifications must define their segment rules in the segment_rules property field of the modification object (/sites/<site_id>/messages). Previously, only cached modifications used the segment_rules property field, while other types of modifications used the contexts.segments and contexts.segment_criteria properties.
  • The contexts.segments and contexts.segment_criteria properties, which store segment and segment combination data, respectively, are now effectively deprecated. Existing production modifications that use these properties will be gradually migrated to use the segment_rules property field.

Graniitti API 0.42.3 (2019-04-08)

...

• When you export a custom script to the CDN (/sites/<site_id>/js/export), the API now excludes the profile property field from cached modification objects in cases where the site does not have selective profiling enabled. Previously, the API exported the profile property  field for cached modifications regardless of whether or not the site used selective profiling.

...