March 31st, 2026
New controls for managing export output, error visibility, and destination configuration.
You can now set a record_limit parameter when downloading audiences or creating exports to cap the number of records returned. The limit can also be cleared on existing exports by setting it to null in the update payload.
When exporting an audience to DelivrDSP, the audience name is now automatically carried through as the DSP list name. You can also provide a custom list name via the optional list_name field on export creation.
Export run responses now include per-record error details. The object_type_results field on export run objects breaks down success and failure counts by CRM object type, with individual error messages available for failed records.
Improvements to how data is prepared and validated before CRM export.
CRM exports now enforce per-field character limits, apply automatic normalization, and support configurable default values. Multi-value fields that exceed destination limits return a MULTI_VALUE_TOO_LONG error code instead of silently truncating.
HubSpot exports now automatically create or attach company records when writing contacts. Pixel activity is also written to the contact's HubSpot timeline so on-site behavior shows up natively in HubSpot. No additional configuration is required for existing HubSpot integrations.
New filtering and bulk operations for list management.
A new bulk delete endpoint allows you to remove multiple list uploads in a single request by passing an array of list IDs.
The list uploads endpoint now accepts type and source query parameters to filter results by upload type and originating source.
The audience preview endpoint now accepts a limit query parameter to control the maximum number of preview rows returned.
New data available for programmatic campaign analysis.
DelivrDSP campaign responses now include match rate data, showing how many exported contacts were matched by the DSP. This data is available through the campaign performance endpoints.
DelivrDSP campaign performance is now persisted with per-day granularity, so daily delivery, spend, and CPM trends are available through the campaign performance endpoints.
A new webhook endpoint accepts UID2 opt-out notifications. When a user opts out through the UID2 framework, their record is added to a unified privacy opt-out registry with a full audit log. Both GET and POST are supported to accommodate different UID2 operator configurations.
New options for controlling pixel behavior.
Organizations can now enable cookieless pixel collection through the organization settings API. When cookies_enabled is set to false, pixels deployed for that organization will not set or read browser cookies. Existing pixels are regenerated automatically to reflect the new mode.
Pixel event payloads now include source-level custom fields in the event_data object, allowing richer context to flow through from pixel sources into downstream processing.
record_count field being returned as the wrong type in event ingestion responsesRUNNING state when the dashboard tab disconnected mid-syncFor full endpoint details, parameters, and examples, see our developer documentation.