July 28 – August 12, 2026 Release Notes

New features

Shared team memory

Ask Chord can now write durable context back into its own knowledge base mid-conversation and search it later, so definitions and conventions your team establishes once are available to everyone in the workspace, with per-user scoping where you need it.

Paths to Conversion reporting

New views covering how many touchpoints precede a conversion, the time from first touch to purchase by channel and campaign, and the most common conversion paths so you can see how channels actually work together rather than in isolation.

Paid Media and Conversion Funnel dashboards

Two new dashboards built on the multi-touch attribution model: paid media performance at the channel, campaign, and ad level with revenue, ROAS, CPA, and CAC, and a dedicated conversion funnel view.

Facebook Ads placement reporting

Placement-level breakdowns are now available across all Facebook Ads connections, so you can see performance by where an ad actually ran, not just by campaign.

Finance-grade Shopify sales reporting

Chord now ingests Shopify's sales agreement stream (the same event stream behind Shopify's own finance reports). It covers every sale, discount, return, exchange, order edit, return fee, and tax amount, dated when booked, and validates against Shopify's admin reports to the cent.

This isn't a correction; Chord's prior reporting was already accurate. This new dataset is simply built to mirror Shopify's own revenue accounting method exactly.

Click ID support across CDP destinations

Chord's CDP now captures and forwards the click identifiers that ad platforms need for accurate conversion matching, carried from the storefront through to backend events and on to destinations.

Improvements

Substantially more reliable answers in Ask Chord

Schema discovery now returns column-level detail in a single step and indexes every table in your warehouse, eliminating cases where the AI quietly settled for a worse table. Invalid table or column errors now come back with a "did you mean" suggestion, dialect guidance was added to prevent repeated query syntax mistakes, and a query-formatting bug behind roughly a third of failures was fixed.

Customer counts based on created orders

New, returning, and total customer logic now keys off created, non-cancelled orders rather than completed orders, so customers whose orders haven't reached a completed state are no longer undercounted.

Shopify bundles, product tags, and customer tags

Product tags, variant-level bundle components, and customer tags now flow through ingestion into the modeled data, making bundle products identifiable and customer tags usable at the user level in reporting.

Subscription field descriptions

Subscriber field descriptions were rewritten to state what each column means in business terms, including units and whether a flag is point-in-time or lifetime, improving both Analytics and the answers Ask Chord gives about subscriptions. Subscriptions documentation was refreshed to match.

Fixes

• Facebook Audience syncs created through Hub no longer fail continuously. A missing configuration field in sync creation has been fixed, and existing broken syncs were repaired.

• Adding an Amazon Selling Partner connection no longer fails immediately with a Merchant ID error before the connection flow starts.

• Google Ads reporting no longer shows blank campaign and ad names, and spend can now be split into brand versus non-brand.

• Meta now receives consistent value units across purchase funnel events; product and cart events previously reported values in cents while completed orders reported dollars, distorting downstream conversion values.

• Meta paid traffic is no longer misclassified as Organic Social, and channel mapping rules now match regardless of capitalization in query and referrer values.

• Month name fields no longer carry a stray suffix in their text values when pulled into reports.