September 23 – October 6, 2026 Release Notes

New features

Rokt Pixel and Rokt Events API destinations

Rokt is now available in the CDP destination catalog, in both on-device and server-side form:

• Rokt Pixel: Runs in the browser. Takes either an API Key or an Account ID, depending on which your Rokt setup provided. Email format, development mode, and custom event mapping are all configurable.

• Rokt Events API: Server-side. Previously this could only be set up outside Hub — it's now available directly from Add Destination.

One thing to know before you enable it: if you configure Rokt Pixel using an Account ID, Rokt's integration can display an offer on your order confirmation page. That's a visible change to your storefront, so confirm it's what you want first.

Improvements

Clearer destination status on Data Activations

Destination status now shows more accurately on Data Activations. Before, any destination that hadn't passed a connection test showed a red "Broken" badge, even if its syncs were working fine. Now you'll see one of these instead:

• Not testable: Chord can't run a connection test for this destination type. This includes HTTP Request destinations, such as Chord Event Triggers.

• Not tested yet: The destination hasn't had its first connection test.

Neither status means something is wrong. Your syncs keep running as normal.

Create Audience now only appears when your workspace is ready

The Create Audience button in Ask Chord now appears only in workspaces set up for audiences (Analytics enabled, reporting connected, and an audiences folder in place). This prevents the button from showing where audience creation would fail.

Easier-to-read error messages on connection forms

When you add or edit a data source or destination, error messages are now easier to read. Before, they showed as dark red text on a bright red background, which didn't meet accessibility contrast standards.