Chord Release Notes: May 6 – May 19, 2026

Key updates this release include Chord AI improvements — feedback memory, live documentation grounding, and smarter date handling — plus several CDP destination updates for Northbeam, Google, Facebook, and Pinterest. We've also included a preview of Chord AI in Claude, coming in an upcoming release.

New features and improvements

Chord AI

In-thread feedback memory

When a user drops feedback mid-conversation — a rule, preference, or correction — Chord AI now recognizes it, saves the rule to memory, and acknowledges with a short confirmation. Vague feedback is routed back through the normal clarification path instead of being silently ignored.

Continue conversation card

Visiting Copilot now lands on a fresh empty state with a "Continue conversation" card for your most recent thread (showing the thread title and a relative timestamp) instead of auto-redirecting. New conversations stay one click away, and there is no card for first-time users.

Grounded in live documentation

User-guide and meta questions now retrieve from the live docs.chord.co content rather than a bundled snapshot. Updates to Chord documentation are reflected in Copilot answers automatically.

Smarter handling of relative dates

Questions with relative time references ("revenue this month", "last quarter", "in November") now resolve against today's date instead of being guessed against a stale training cutoff.

Coming soon

Chord AI in Claude

Foundational work has shipped this cycle to host Chord AI as a Model Context Protocol (MCP) server with OAuth-based sign-in, paving the way for users to query their Chord data directly from inside Claude. The full integration will land in an upcoming release. Stay tuned!

Chord CDP

Northbeam Pixel destination

New device-mode destination for Northbeam, with configuration fields for Data Client ID and custom goal IDs (Product Viewed, Add to Cart, Checkout Started).

Google Consent Mode v2 for Google Ads and GA4

Google Ads (Gtag) and GA4 (Device Mode) destinations now support Ad Consent Category and Analytics Consent Category fields, bringing both to parity with Google's Consent Mode v2 requirements for EEA traffic and enabling conversion modeling for non-consenting users. The Consent Requirements section is now visible on the Google Ads destination as well.

Facebook Pixel: Support for multiple pixel IDs

The Facebook Pixel destination now accepts multiple Pixel IDs. Existing destinations with a single Pixel ID auto-migrate to the new array on first open, with no manual intervention needed.

Pinterest Tag: Enhanced Match Loading toggle

A new "Use Enhanced Match Loading" toggle on the Pinterest Tag destination enables sending a hashed email with the Pinterest tag load call, improving conversion attribution and making reporting more resilient to third-party cookie loss.

Function logs: Error and delivery metrics exposed

Function logs now expose connection-level error and delivery metrics, with improved navigation.

Fixes

• Fixed the Recharge API key validation, which now uses a working endpoint so connecting a Recharge data source succeeds reliably.

• Fixed an issue where an expired downstream session could leave a user appearing logged in to the platform while Copilot calls failed silently — affected users are now logged out and prompted to sign in again.

• Resolved a regression that caused every feature-flag-gated navigation link to appear in the sidebar for certain brands.