Search…
⌃K

Exporting an Audience

Exporting audience identity clusters
Audiences can be exported to a configured destination. You can configure an audience export from the Audience > Exports tab in the DCN UI, or using the CLI. The exported data are either lists of identifiers belonging to the identity clusters making up the audience, or the JSON identity cluster records themselves.
To learn how to enqueue an export of a given audience to a specified destination, navigate to the specific destinations page and follow the "Exporting Audience to" section. There you will find instructions on how to export using the UI as well as the CLI

Optional CLI Export Flags

The --identifiers-filter=<ID Type> option enables you to limit the types of IDs included in the export. If you do do not specify ID types, all ID types will be exported by default.
The available ID types are:
email, idfa, gaid, cid, vid, ipv4, ipv6, tifa, rida, afai, phone, netid, cid1, cid2, cid3, cid4, cid5, cid6, cid7, cid8, cid9.email, idfa, gaid, cid, vid, ipv4, ipv6, tifa, rida, afai, phone, netid, cid1-10

CLI Export Flags for File Type Exports (GCS & S3)

The <format> argument allows you configure which type of data you are interested in exporting. The default "cluster_json" option exports JSON-encoded identity clusters, whereas the "id_csv" and "id_tsv" options export only IDs (without links and traits) in either CSV or TSV format, respectively.

Optional CLI Export Flags for File Type Exports (GCS & S3)

  • The --filename=STRING flag allows you to specify the name of the file to create in the specified destination bucket
  • The --[no]override-existing flag allows you to override an existing file of the same name. This defaults to True.
  • The --export-metadata flag allows you to export an additional Metadata file.
  • When exporting CSV or TSV ID values (i.e., "id_csv" or "id_tsv"), the first column contains the type-prefixed ID value and the second column contains the type of ID. The first row is a header indicating the names of the columns. You can control this behavior with the --[no-]id-include-header, --[no-]id-type-column and --[no-]id-type-prefix options.
  • When exporting JSON identity clusters (i.e., --format="cluster_json"), the options --[no-]cluster-include-sources and --[no-]cluster-include-traits allow you to control whether source information and traits data are included in the exported cluster data. The default is to include them.
A list of previously scheduled exports and their status can be obtained from the UI or the CLI with the optable-cli export list command.