Customer Data Platform

Self-serve Locations management

You can now create and manage Stores, Zones, Concepts, Tills, Labels, and dynamic Collections from a single Locations page, without a support ticket or data import. Enabling a Concept as an Organization Unit may still require a Platforms ticket.

Documentation link: Manage locations (Stores, Zones, Concepts, and Tills)

Tier Upgrade History ISO Timestamp Field

The customer tier/slab upgrade history response now includes a changedOnISO field, a reliably formatted ISO 8601 timestamp for when a tier change occurred. Use this field instead of the existing changedOn field, which has a known issue where it can return the calling system's local time incorrectly labeled as UTC.

Documentation link: Get Customer Details (V2)

Engage

Archive and unarchive templates

Templates (creatives) can now be archived to keep the templates list clutter-free, and unarchived at any time to bring them back. Archiving never deletes a template or affects campaigns and journeys that already reference it. Not available for Zalo, and WhatsApp/RCS templates must reach a final approval status before they can be archived.

Documentation link: Archive and unarchive templates

Loyalty

Activity-Level Breakdown in the Points Ledger Explode API

The Points Ledger Explode API can now return a breakdown of how promotional points were earned across individual activities, such as specific milestones or streaks, instead of just the total. This makes it easier to explain to a member exactly which activities contributed to a points award.

Documentation link: Get Points Ledger Explode Info

Spend Thresholds and Wider Filtering for Loyalty Promotions

The Issue Currency action with fixed allocation now supports an optional spend threshold, so a reward only pays out once a member's qualifying spend on filtered items or tenders crosses a value you set. Line-item filtering for issue actions also now covers tender types and product attributes, not just SKUs, brands, and categories, and each filter block can hold up to 200 attribute keys, up from 2.

Documentation link: Create a Loyalty Promotion