Data Export

Creating data export requests

Before you start creating data export requests, ensure that:

  • The Data Export feature is provisioned for your tenant.

  • A member of the CDP Professional Services team sets up an Amazon S3 connector for your tenant by using your S3 credentials.

Important

If you are already using Snowflake, Acquia recommends that you leverage the Data Sharing feature instead of the Data Export feature. For more information about sharing data through Snowflake, see Sharing data.

To create a data export request:

  1. Sign in to the CDP user interface.

  2. In the navigation pane, click Data Export.

    The system displays the Data Export page listing all the requests that are set up for your tenant.

    You can create multiple data export requests for each tenant, export data to multiple destinations, and export content types.

  3. Click New Data Export.

  4. In Name, specify a name for your data export request.

  5. In Description, specify a description for your data export request.

  6. Click Next.

  7. In Content, click the + icon corresponding to all the attributes whose values you want to export.

    Exported files contain the attributes selected for each entity.

    Note

    • To remove any selected attribute, click the corresponding - icon.

    • You can add attributes from multiple entities to the same data export request.

    • For more information on the available entities and attributes, see Available entities for Data Export and Available attributes for Data Export.

    • Apart from the standard entities and attributes, you can export various custom entities or attributes.

  8. Click Next.

  9. Select one of the following delivery options:

    • Export all records: Exports all records.

    • Modified since previous export: Exports incrementally.

    • Export records that are modified after: Exports records after a specific date.

    • Export records that are modified between: Exports records that are between two specific dates.

    A few entities such as customersummary and mastercustomer are always fully exported with every execution because all rows in such entities are updated everyday through CDP’s daily processing.

  10. In Destination, select one of the available output connectors that you already configured.

  11. In List, select the list or table of attributes that you want to export to the destination.

    A few destination connectors might not have a list. To create a list for your destination connectors, contact your account manager.

  12. To start the Data Export process immediately, click Send Now.

    Alternatively, to schedule the data export process, enable the Schedule option, define the date, time, and frequency of the process, and click Save.

Checking the export history

To check the export history:

  1. Sign in to the CDP user interface.

  2. In the navigation pane, click Data Export.

    The system displays the Data Export page listing all the requests that are set up for your tenant.

  3. Locate the data export request for which you want to check the history.

  4. Click the Kebab menu icon and select History.

    The system displays the export history for the specific export. You can view the timestamp of the execution of the export process and the count of the number of records exported on each entity.

Important usage notes

  • The MasterCustomerID of a customer record is dependent on de-duping rules and is calculated everyday. Therefore, it is subject to change. As we continually process new information for customer records, Customer Data Platform (CDP)’s unique identifier for master customers may change over time. The most consistent way to identify a specific customer record over a period is to use the “SourceCustomerNumber” attribute instead.

  • The order of columns within an exported flat file might change if new columns are added to the Data Export or if existing columns are removed. Therefore, Acquia recommends that any downstream integrations must not depend on the order of columns within the exported files for data ingestion purposes. The column headers will always be included in the first row.