Overview

This article lists recent updates and changes to the Kamino developer documentation.

Changelog

April 4, 2026 - Multilingual Product Catalogue details

Impacted documentation:

• Integrate JavaScript tag 
• Comply with Digital Services Act (DSA) requirements 

Updates:

• Updated device types from web_Desktop to desktop.
• Moved the Legal file to the introductions section rather than the Display-video introduction.

April 8, 2026 - Multilingual Product Catalogue details

Impacted documentation:

• Share multilingual product catalog 

Updates:

• Added a new page to detail requirements for a product catalog containing several languages.

September 26, 2025 – Filters integration

Impacted documentation:

• Enhance ad relevance with filters 
• Product catalog attributes – updated custom_labels attribute description
• API Delivery – Get Creatives – new filter parameter added

Updates:

• Created a new "Filters" documentation page containing definitions, syntax, operators, and examples.
• Updated the "Products Feed Attributes" page to clarify custom_labels usage for filters.
• Added filter parameters to the API Delivery Get Creatives endpoint.

September 9, 2025 – Visimax new format creation

Impacted documentation: Ad format: Visimax

Updates:

• Created new format guidelines for rendering and tracking within the Visimax documentation.

July 10, 2025 – Kamino JS tag integration guide

Impacted documentation: Integrate JavaScript tag 

Updates:

• Restructured the Kamino JS tag integration guide to improve clarity and usability.
• Introduced the retailerData global object, which is required before the tag loads.
• Added a detailed field reference for user, context, and cart blocks.
• Provided SPA guidance and guidelines to handle retailerData and the JS tag on route changes.
• Included instructions on tag integration and placement best practices.
• Added multiple HTML examples for various page contexts, such as Category, Search, and Confirmation.

June 16, 2025 – Products catalog attributes updates

Impacted documentation: Product catalog attributes 

New fields added:

• retailer_parent_id – new attribute to group product variants under a common parent product. Example: ABCD1234

Field updates and enhancements:

• retailer_product_category – enhanced to support multiple category paths separated by |.
  • The first category path is considered the principal one.
  • Up to 10 levels are ingested per category path.
  • Example: Jedi women > Accessories > Swords | Star Wars > Gear > Combat
• retailer_product_category_id – updated example to reflect multiple category paths separated by |, in sync with retailer_product_category.
• store_ids – renamed to store_id for clarity (singular form).
  • Each product-store combination must be represented as a separate row, element, or object.
  • All other fields, such as price and stock, must reflect store-specific values.