Data Extract Activity

Considerations

• Before you create an extract, work with your Account Executive to provision the extract types for your account.

• Before you create a data extract, configure a File Transfer Location in Account Settings.

• To place extracted data in a file location you choose, use the File Transfer activity. Data extract files are supplied in ZIP format.

• If you use the data extract activity in an automation, include the file transfer activity in a separate step. This step prevents the file transfer activity from looking for the data extract file before the data extract is complete.

• The Extract Type determines the fields included in a data extract file.

• For some types of extracts, you can specify an extract range. The extracted data is limited to the period that you specify. The extract range always ends at the time that the data extract activity starts. For example, if you choose an extract range of 7 days, the activity extracts tracking information for the last 7 days up to the minute the activity runs.

• If you select Extract Multiple Data Extension List Data when you create a standard tracking extract, run the extract at the Enterprise level.

• If you select the Include option for a data extract, the activity produces a compressed file that contains the data you included.

• Click and open tracking data is rounded to the nearest second.

• Don’t use %%Minute%% or %%Second%% variables in the file name for an extract. If you use these patterns, the file transfer activity may not find your data extract file.

• When you select a time zone for a tracking extract output file, select Use Local TZ in Query. When this option isn’t selected, the output file defaults to Central Standard Time and doesn’t observe Daylight Savings Time. This option isn’t available for data extension extracts.

• If you create an extract that includes Extract Clicks, and then you select Include Unique Clicks, the unique clicks data appears in the Clicks file. The activity doesn’t produce a separate file for unique clicks.

• If a single Member ID (MID) has a queue that contains 250 or more data extracts, subsequent data extract requests are rejected until the number of extracts in the queue is less than 250.

• To avoid performance issues, keep data extracts under 25 GB.

• In Hyperforce, columns with the varchar data type can include up to 4,000 characters. Columns with the nvarchar data type can have up to 250 characters.