August 26 – September 9, 2026 Release Notes

New features

OpenAI Ads Pixel and Conversions API destinations

Send conversions to ChatGPT Ads from Chord's CDP, either server-side through the Conversions API or in the browser via the Pixel, with custom event mapping on both. Note that OpenAI deduplicates on pixel ID, event name, and event ID together; if you run both destinations, use matching pixel IDs and event mappings, or one purchase will be counted as two conversions with no error to warn you.

Attentive data source connector

Attentive can now be connected from the Data Sources page with a single API key. Attentive sends events by webhook rather than exposing message history, so data is captured from the day you connect forward; there is no historical backfill. If a key is rejected, the error now tells you whether the key itself is wrong or simply lacks webhook access, and links to the relevant documentation.

Improvements

Bot traffic filtering now applied by default across existing reporting

Bot traffic filtering has moved downstream into a single filter logic, and existing CDP-based reporting and content now includes this filter by default to all existing reports rather than requiring it to be added separately. Monitoring for new bot traffic is now automated.

Ask Chord answers questions about your saved audiences

Asking Ask Chord for the query behind a named audience now returns the real definition from your reporting model, instead of guessing at a warehouse table that may not exist.

Classic Monitors has been retired

The Monitors page has been removed. It carried a deprecation notice through the previous release.

Fixes

• Fixed an issue with audiences being reported as failed after building successfully, caused by the status check treating a single dropped request or a slow watcher as proof of failure, and by a reporting deploy that took longer than expected being counted as failed even though it had gone through.

• Fixed an issue with TikTok audience syncs that could not be created, caused by a required field blocking the wizard, and by syncs created through a workaround never resolving their audience at run time.

• Fixed an issue with Klaviyo syncs to Profile & List that could not be created, caused by a required field being removed during setup and never replaced, leaving an error with nothing on screen to correct.

• Fixed an issue with Ask Chord answers appearing correctly formatted and then being replaced moments later by a plainer, text-heavy version, caused by answers being identified by their position in the response instead of reliably.