Audience Export

Audience export is how ResultFly turns a saved CDP segment into a downloadable dataset for downstream use.

In plain terms, export is the handoff step. The CDP has already collected customer data, resolved profiles, and evaluated segment rules. Export takes one saved segment and produces a concrete dataset that another team, tool, or process can use.

Export is not a new query builder. You do not configure the audience from scratch during export. First, create and save the segment. Then launch an export job for that existing segment.

Typical destinations include:

• analytics workflows
• messaging tools
• CRM operations
• ad-hoc customer operations
• partner systems

Segment vs Export

A segment is the reusable audience rule.

An export is one run of that rule that produces a dataset.

For example, a segment may be “Gold loyalty customers with email consent granted.” That segment can be previewed, edited, reused, and exported many times. Each export is a separate job created from that saved segment.

This difference matters:

• changing the segment changes the rule for future work
• launching an export creates a dataset for one run
• an existing export artifact does not update when the segment or customer data changes later
• to get a newer audience, run another export from the segment

What the User Gets

After an export is launched, ResultFly creates an export job.

The user can see:

• job status, such as pending, running, succeeded, or failed
• the segment used for the export
• row count when the backend reports it
• execution context and freshness metadata when available
• expiration time for the export artifact when available
• a temporary download link after the job succeeds

The downloaded artifact is the audience dataset for that run. Depending on the export contract, it may include:

• profile-level fields
• selected identifiers
• channel availability and consent-safe contact data
• profile attributes
• segment membership as of export time

How Export Works

ResultFly treats export as an asynchronous job.

This means the user starts the export and ResultFly prepares the dataset in the background. The page can show progress and the final download link when the job is ready.

This is important because audience generation can involve many profiles, segment rules, freshness checks, and downstream artifact preparation. By running export in the background, the platform can:

• keep the UI responsive
• handle large result sets safely
• show job status clearly
• avoid partial downloads from long-running queries

Export Is a Snapshot

An export is not a live link to the segment.

When an export job is launched, it creates a fixed run based on the segment rule and the customer data available for that run. If the customer data changes later, the existing export artifact does not change.

This is useful because downstream teams need a stable handoff. The file or dataset they receive should not silently change while they are using it for analytics, operations, or activation.

Why Export Is Tied to Segments

ResultFly does not treat export as a loose query tool for arbitrary hidden data.

Instead, export is anchored in the same saved audience model used by the CDP. That means the exported result stays explainable:

• why this customer is in the audience
• which rule produced the audience
• which customer facts were available at export time

Typical Flow

1. Create or choose a saved segment.
2. Preview the segment when audience size or rule correctness matters.
3. Open exports and select that segment.
4. Create an export job.
5. Wait for the job to finish.
6. Download the temporary artifact after the job succeeds.

If the same audience needs to be refreshed later, run a new export from the same segment.

Operational Benefit

For marketers, export provides a practical handoff from audience design to execution.

For developers and operators, async jobs provide a predictable contract for status polling, download handoff, and failure handling.