April 2025 Release Highlights - Dynamic Data Settings, New Predictive Audiences, and more!

Spring’s in full swing—and so is our platform! April’s updates are all about maximizing value with minimal lift. We’re pushing forward on clarity and trust so your team can do more with the data you already have.

Here's what's new and how it helps you stay focused on growth, not guesswork.

New Feature Highlights

• Dynamic Data Settings : Dynamic Data Settings is designed to give you more control over how your data is configured. These updates reduce complexity across your analytics workflows and make it easier to get the insights you need, faster. Here's what you can directly configure through the Chord data platform:

  • Time zone — Set a single, default time zone for your organization to streamline reporting and reduce clutter in your analytics.

  • Week start day — Choose the day your reporting week begins.

  • Calendar type — Select from standard or fiscal calendars for more relevant reporting.

  • Note that changes to the start of week and fiscal year setting won’t immediately apply to Quickstarts and Chord-provided dashboards. These updates are coming in a fast-follow release.

  • Need more details? Check out our documentation.

Improvements

• New Predictive Audiences : Chord added three new predictive audiences to the platform! You can now find and activate At-Risk Customers, Almost-Purchasers, and Motivated Customers under Prebuilt Audiences. For more information about these predictive audiences, click here.

• Enhanced Sessions Dataset : We now have additional sessions datasets for the following datapoints - Order-level: Purchase details; Attribution-level: Fbclid and Msclkid, in addition to the existing gclid; and User-level: First and last order dates for cohorting and audience filtering.

• Platform Roles & Permissions : We’ve made some behind-the-scenes updates to improve roles and permissions on the platform. These updates will allow for easier team management and better access control. Click here to view the latest documentation updates on user roles and permissions.

Fixes

• We fixed an issue within our model amplifications content validator.