Provider release notes

Effective this month (October), received counts will begin to be deprecated and replaced with hit counts in the Segments Dashboard UI and targetingDataInsights field. Here's what you need to know:

• Received counts are the methodology for counting unique, deduplicated IDs in a segment.
• Hit counts report the number of IDs ingested in a segment during each time period (for example, one or seven days), without deduplication.
• You can use hit counts to see how many IDs you send rather than how many are stored. This enables you to verify uploads and troubleshoot ingestion or segment issues. For details on hit counts, see ID counting methodologies.

Active counts are not affected by this change. Hit counts have been available in the Segments Dashboard since July 2026.

Depending on how you retrieve ID counts, complete the following actions:

• If you view ID counts in the Segments Dashboard or the targetingDataInsights field in GraphQL, use hit counts instead of received counts going forward.
• If your integrations use GraphQL queries, such as data insights, that retrieve the receivedCounts field, update them to use the hitCounts field.
• If your integrations use the POST /v3/thirdpartydata/query endpoint, continue retrieving received counts until hit counts are available in the REST API.

• JSON API error responses with ErrorCode and Message fields
• Corrected HTTP status codes
• Consistent error messages across endpoints
• Per-item serialization errors surfacing in FailedLines instead of the entire request failing
• New FailedLines error codes

For more consistent data modeling, we've replaced the TargetingDataStatus field (queried through the TargetingData entity) with the new TargetingDataInsights field, now queried through the TargetingDataSegment entity. Unlike TargetingDataStatus, the new field does not have a state subfield with enum values.
For details and an updated query example, see Third-party data insights.

None.

If you're a location data provider who tracks store visits and foot traffic, you can now support both daily and weekly visit tracking through a single tag while providing advertisers with more granular, location-level measurement. To help you get started, we've published a guide that explains how to structure your category and location taxonomies and configure location-based events.
For details, see Product catalog for location data providers.

None.

We've added a new page describing how we classify and communicate API changes, covering our four change categories (additions, behavior changes, new requirements, removals and replacements) and our standard notice periods. For details, see API Changes.

None. This isn't tied to a specific product release. It's new reference content to help you plan around future API changes.

• AudienceUnlimitedTier
• SupplyVendorId
• SupplyVendorPublisherId
• SampledViewedImpressions
• SampledTrackedImpressions
• PlayerCompletedViews
• PlayerCompletedStarts
• AudioFeedTypeId
• AudioFeedTypeName
• VideoPlacementType

As part of this update, the following fields have also been updated in this new version:

• The Clicks column is now included by default.
• The DMA column has been renamed to Nielsen DMA. Effective August 31, 2026, the DMA column will no longer be supported.

The Trade Desk has published a new guide for the real-time ID tag, which initiates cookie mapping between websites and TDIDs used by the Real-Time Conversion Events API. If you use real-time conversions, this is the recommended cookie mapping option because it supports real-time targeting and measurement while requiring less infrastructure than the match tag solution.

None. To enable this feature, contact your Account Manager or Technical Account Manager. For details, see Real-Time ID Tag.

• Onboarding of the following types of data to The Trade Desk: conversions, first-party segments, and third-party segments. You can also manage optouts and deletions.
• Built-in conversion to UID2s or EUIDs
• Built-in secure authentication

As The Trade Desk introduces new features and capabilities, Curated REDS fields are updated to provide richer data and insights. An updated version of the schema will be provided alongside your existing schema. Both versions will be available concurrently until the legacy schema is deprecated.
NOTE: All changes listed below require migration. However, migration requirements depend on your current schema. Not all providers are affected.

Review the changes above to determine whether your integration requires schema updates due to added, renamed, or removed fields. Your current schema and the upgraded version will both remain available until a deprecation date is announced.
For next steps, contact your Data Partnership Manager.

• Existing data elements assigned to charge-max groups now use the charge-all group logic. You do not need to manually reassign data elements to your charge-all group.
• You must still assign new data elements to your charge-all group.

Effective April 2, 2026, the User Management Platform (UMP) supports Data API token generation for authentication with new data providers. For details, see User Management Platform and API token authentication.

To provide true shared access without transferring ownership or control, we've updated the User Management Platform (UMP) organization model and shared administrative access, which helps clarify the relationship between brands and agencies within the UMP. For details, see User Management Platform.