DATE:
AUTHOR:
Chord Product Team
Feature Announcements

November 3 – November 16, 2026 Release Notes

DATE:
AUTHOR: Chord Product Team

Improvements

CDP Destination catalog grouped by purpose
The CDP destination catalog now organizes every destination into labeled categories.

New configuration options across destinations
Several destinations now expose settings the CDP could already act on but Hub had no field for:

  • OpenAI Ads Conversions API: set a storefront URL so server-side events such as Order Completed are accepted instead of rejected for having no source URL.

  • Klaviyo: pin a specific API version rather than always tracking the latest, and choose whether to include external IDs.

  • Microsoft Conversions API: specify how each event's consent is reported, so tracking reflects your consent policy.

  • Meta Conversions API: add a test event code to verify server-side events before going live, matching the TikTok workflow.

  • Reddit Pixel and Conversions API: set a dedup source property so events reported by both surfaces are counted once.

  • Snowflake: the username field now appears for key-pair authentication, which requires it.

Meta Pixel requires a Pixel ID
The Meta Pixel destination now marks the Pixel ID as required and will not save without one, so a destination can no longer be set up in a state where it silently does nothing. Existing destinations are unaffected.

Fixes

  • Ask Chord now saves the actual customer list when you create an audience. Previously, if a summary query such as a count per segment ran after the list, the audience could be built from those totals instead of the customers.

Powered by LaunchNotes