October 7 – October 19, 2026 Release Notes

New features

Amazon Conversions API CDP destination

Amazon Conversions API is now in the CDP destination catalog, available to all workspaces. This is a server-side destination only; there is no browser pixel counterpart. Configure your advertiser ID and credentials, with optional dataset naming and event mapping; region, event source, country code, and page-event forwarding all have sensible defaults.

Avoid running a second Amazon destination alongside it, which would double-count your conversions. See the Amazon Conversions API documentation for setup steps, event mapping, and identity handling.

Improvements

Pick your ad accounts when connecting a source

Connecting Facebook, Google, TikTok, or Bing Ads now asks which ad accounts to sync rather than syncing everything the authorizing login can reach. This matters most on agency or shared business logins, where the previous behavior could pull other brands' ad accounts into your data. Other data sources are unchanged.

More accurate channel performance in Ask Chord

Channel performance now groups paid channels the same way the rest of your reporting does, so Meta campaigns no longer appear as separate channels showing no spend. Results also report against both created and completed orders, and Ask Chord will follow your stated preference if you tell it which basis you want.