Exporting segments to destinations

What it does

An export pushes a segment's members out to an external service — an ad platform, an email tool, a data lake — over a connection an admin has already set up. The export is a separate object from the segment, with its own schedule, permissions and failure modes.

Key facts

Exports live under Data > Exports, not under Segments, and are created with Add export by first choosing a connection.
Connections and exports are deliberately split by role. Administrators reach every connection and can create one mid-export-setup; contributors only get the specific connections an admin has shared with them, and can edit or view depending on how the admin configured it; viewers can look at existing exports and nothing more.
By default an export runs during every scheduled system refresh. A custom schedule is set per export via Schedule, with Schedule run On or Off and a Recurrence.
Selecting several exports at once gives the same Keep individual schedules versus Define new schedule for all selected exports choice as segments — the second overwrites.
Run all on the exports page only runs active exports. Individual exports run from their own Run command.
If a dependency is still updating when a scheduled export is due, the system finishes the dependency first and then runs the export. The Refreshed column shows the last successful run.
Exports on a custom schedule can display a misleading Skipped status on the main exports page while actually running to their own cadence. That's documented behaviour, not a bug.
Microsoft's performance guidance is to spread segment tables across multiple exports rather than pile them into one, and to leave 30 minutes to an hour between scheduled exports rather than firing them together.
Run history and errors are under Settings > System > Status, in the Export destinations section. Selecting a status opens Progress details, which shows processing time, errors and warnings, and offers Cancel job.
Detach connection deactivates an export without deleting it; the Connection used column then reads "No Connection". Remove deletes it outright.
There is no indicator showing which tasks are on custom schedules in the status history, so reading that history takes local knowledge.

When to use / skip

If a segment is going to be actioned anywhere outside Customer Insights, it needs an export — there's no realistic alternative for ad platforms and email tools. The judgment call is which route: a per-platform connector, or a data lake export that the client's own integration layer picks up.

Reach for the specific connector when the destination is on the supported list and the client's marketing team wants to self-serve. Reach for a lake export when there are several downstream consumers, when the client already has an integration platform, or when the field mapping needs transformation that the connector can't do. The lake route costs more up front and is much less painful at the fifth destination.

Skip exports entirely for Customer Insights - Journeys — segments flow there through the product integration rather than through an export destination, and building an export to get them there is work for nothing.

Configuration decisions

Connector per destination versus one lake export plus a client-side integration. Decide this once, early; retro-fitting a lake pattern after six connectors are live is a project of its own.
Who owns connections. Making every marketer an admin so they can create connections is the usual shortcut and the usual audit finding.
Which fields each destination gets. Most platforms need a matching key and very little else, and sending more personal data than the destination needs is a compliance problem, not a convenience.
Export schedule per destination, and how those schedules are spaced across the refresh window given the 30-to-60-minute spacing guidance.
How consent and suppression are handled — as conditions inside the segment, or as filtering at the destination. Inside the segment is safer, because it survives someone re-pointing the export.
How many segments a single export carries, balancing manageability against the guidance to spread tables across exports.

Gotchas

The Skipped status on custom-scheduled exports sends people investigating a problem that doesn't exist, and conditions them to ignore genuine skips.
Scheduling every export at the same time is the most common cause of a refresh window blowing out. The spacing advice exists for a reason.
An export is only ever as fresh as the segment behind it. An hourly export of a weekly segment sends the same list six times.
Detach and remove look similar in the UI and do very different things. Detaching leaves an export that appears configured but has no connection.
Credentials behind a connection expire. The export then fails on schedule, quietly, and nobody looks at Settings > System > Status until the campaign team complains about an empty audience.
Contributor access to exports depends on which connections an admin shared. A contributor can see a segment they cannot export, which reads like a product fault and isn't.

Consultant notes

Walk the client's admin through Settings > System > Status and the Progress details pane during handover. Export failures are the most common post-go-live support call, and this is the page that answers them.
Agree the data minimisation position with whoever owns privacy before mapping fields to an ad platform. Sending a full profile because the connector allows it is an easy finding at audit.
Put connection ownership and credential renewal in the run book with named owners and dates. Expiry-driven failures are the ones that catch everyone.
Demo one export end to end, including the destination side, before the client signs off. "It ran successfully" in CI Data and "the audience appeared" in the ad platform are not the same statement.
Check the export schedule spread against the refresh window as part of go-live checks, not afterwards.

Worth another look if the connector list changes materially, or if Microsoft surfaces custom-schedule indicators in the status history.