May 1st, 2026
Platform
A heavy month for exports, with new ways to schedule, name, slice, and format the files we deliver to your destinations.
You can now define a filename template when creating or editing a file export destination. Build the pattern in a pill-based template builder and see a live preview of how output files will be named before you save.
One-time exports now support date ranges up to 365 days. Larger historical pulls run as a series of windows so they complete reliably, with progress visible while the run is in flight.
Pick the exact start and end date you want when running a one-time export instead of relying on a fixed lookback. Both the create and edit screens accept the user-provided range, with validation on the backend.
Daily and weekly recurring exports can now be anchored to a specific run time and a specific day of week. The scheduler enforces those anchors so runs land when you expect them.
A new "Unique contacts only" toggle on file exports deduplicates rows by hashed email so each contact appears once per output file.
A new combineOutput toggle on file destinations writes a single combined artifact for multi-window exports instead of one file per window.
S3 export destinations now accept JSONL alongside the existing file formats, making it easier to feed export output directly into JSON-native downstream systems.
A new export type pulls raw DSP event logs straight from campaign reporting. Choose the Raw Logs format when creating an export to deliver the underlying event records to your destination.
File destinations can now receive an empty file when an export produces zero records, so downstream automations that watch for a delivered file no longer stall. The behavior is controlled by an emitEmptyFile toggle on the destination.
Completed one-time exports are now periodically archived, and the exports list gained an "Include archived" filter so you can show or hide them.
After an export exhausts its automatic retries, manual re-triggers are gated behind a cool-off window so a single export can't be re-launched repeatedly while it is still in a failure state.
The Resolved Only toggle is now available on the export edit screen, not just on create, so you can flip it on for an existing export without recreating it.
The export overview now displays the data watermark for the export so you can see how recent the underlying data is. Scheduled exports also use this watermark when computing the date range for the next run.
Export filenames and project folder paths now preserve the original case from your destination configuration.
The subject template you configure on email exports is now interpolated across batched, streamed, and multi-file send paths, not just single-file sends.
DSP-related flows in the dashboard were renamed, scoped, and expanded.
The DSP source is now labeled DelivrDSP across the audience and export flows.
Projects are now limited to a single DelivrDSP connector and a unique account ID. Attempting to add a duplicate surfaces a clear uniqueness error instead of failing silently.
The export create flow now shows a two-level data source selector when DSP is chosen: pick the DSP and then pick the specific campaign to export from.
DSP queries can now run against all projects in scope and include inactive campaigns in the result set.
The export field selector now exposes DSP-specific event fields when the source is DSP, including HEM and client IP, so you can pull additional event-level attributes into the output.
Audience configuration gained finer controls and clearer feedback.
Audience create, edit, and detail screens now expose an intent window slider so you can choose how many days of intent signal feed into the audience.
The audiences list now shows when each audience's size was last computed, so you can tell at a glance whether the displayed size reflects a recent refresh.
Multi-value text filters in the audience, persona, and account condition builders now render as chips, making it visually clear when multiple values are targeted in a single condition.