July 2026

2026-07-30

The MCP server no longer advertises the legacy Transactions catalogs MCP
The legacy Transactions dataset was withdrawn earlier this month: its reference reads (/api/v2/analyses/reference/transactions/merchants, /spend and /frequency) return 404, audience creates reject the Transactions type, and GET .../reference/common/dataset-types no longer lists it. Audiences built before the withdrawal are unaffected and still activate. lookup_reference with dataset: "transactions" now returns a tool error naming the supported replacement instead of a route-not-found failure. The dataset the console labels Transactions is reached with dataset: "affinity-transactions", and its audience-create type is AffinityTransactions - see Transactions reference.
The MCP create_audience tool names every dataset type MCP
Its description now names every dataset type the endpoint accepts and spells out the AffinityTransactions block’s fields. It previously listed only a subset, so agents could not discover the rest. No endpoint behavior changed.

2026-07-29

The ProfileAttributes delivered window extends through Q3 2026 API
GET .../reference/profile-attributes/recency-limits returns end_limit: 2026-09-30, and audience creates accept start_date / end_date values through that date.

The Affinity Transactions dataset is now displayed as Transactions Console
The new name appears across the console and these docs. API identifiers are unchanged: the dataset type is still AffinityTransactions and the reference reads stay at /api/v2/analyses/reference/affinity-transactions/*. No client changes are needed.