Data in the export

Guests in a segment are the basis of an export

Audience exports are based on data from guests in a segment. From a Scheduled or Live segment, you can export an audience and include any guest data, for example, order, event, and extension data, that is sent to Sitecore CDP using the Stream API, Batch API, or REST APIs, and is available in the guest profile.

Important

You can instantly create and use a segment in an audience export. However, the guests contained in the segment are based on a snapshot of data up to midnight (UTC) the previous night. For example, if you want to export an audience of guests who have purchased within the past week, any guests that purchased after midnight (UTC) the previous night won't be included in the snapshot of data used to build the segment until the following day.

Segment subgroups

When creating a full audience export, you can apply filters to the segment of your choice. This helps you choose the right audience to export. Filters are based on conditions that developers create.

For example, if you have a segment of all your loyalty members, you can use filters to select only those guests for the export who are associated with a specific country or region. Or consider a segment of guests that have completed an order on your website in the past year. Using filters, you can select only those guests who have searched for a product on your website in the past two weeks, and include only this subgroup in the export.

Full exports and delta exports

When creating an audience export, you choose whether to export full datasets or deltas only.

A full export contains the full audience that you specify in a later step. You can run full exports instantly or at scheduled intervals, for example, daily, weekly, or on a custom schedule.

In contrast, delta exports run once a day. The first export is identical to a full export: it contains the full audience that you specify in a later step. But subsequent exports will only contain data for guests in the audience who have been added to the segment since the previous run, and guests who have been removed from the segment since the previous run. The output contains separate files for added guests from removed guests so you can distinguish between them.

Example

Consider a segment of guests that have visited your website in the past seven days. This segment changes daily, with some guests added and some removed every day.

If you export this audience using a full export, when the export runs, every export will contain every guest that is part of the segment at the time.

If you export this audience using a delta export, the first export will run like a full export. But the next time the delta export runs, it will contain guests who:

Were not visitors at the time of the previous run but have become visitors since (added guests).
Were visitors at the time of the previous run but haven't visited since (removed guests).

The export will not contain guests who were visitors at the time of both the previous and the current run.

Choosing the right export type

When choosing between full and delta exports, consider the requirements of the external system that you'll activate your audience in. The system might work better with, or might only accept, deltas.

Including data in the output

In an audience export, on the Output structure tab, you choose what data to include in the output and in what structure. When you click Add column, a String field displays with a Header field and an Attribute value field.

In the Header field, you can enter any unique text, for example, email. The header will appear in the first row in the CSV output if you choose to include headers in the output, or as the key name in every JSON object in the JSON output.

In the Attribute value field of a string field, you can include the following data:

Hardcoded texts wrapped in double quotes, for example, "20EuroOff".
References to dynamic data in the guest profile, for example, ${guest.email} and ${guest.lastSeen}.
References to dynamic custom data computed with JavaScript, for example, ${jsResult.pageViewCount}.
JavaScript utility function calls, for example, ${getDataExtension(guest.dataExtensions, "ext1", "MemberCardCategory", "not-available")}.

Note

To reference dynamic data, use the FreeMarker variable notation ${}. Dynamic data will be computed when the audience export runs.

You can also reference dynamic data in the guest profile by clicking the Data tab, then copying the path from the Guest data model.

You can change the field type to a Number field. The number field is useful when you want the output to contain the numeric versions of hardcoded or computed integers or floats (10, 9.99) instead of their stringified alternatives ("10", "9.99"). In number fields, you can specify:

Max number of digits - the maximum number of digits in the number. Results are rounded to this number of digits. The default is 10. This value must be higher than the maximum number of decimal points.
Max number of decimal points - the maximum number of digits to the right of the decimal point. The default is 2. This value must be lower than the maximum number of digits.

String fields and number fields in the output structure of an audience export.

After saving your changes, we recommend that you test the audience export to make sure that the attribute values are correct.