Export Customer Journey Analytics reports to the cloud

You can export Workspace full tables from Customer Journey Analytics and send exports to designated cloud destinations.

Other methods of exporting Customer Journey Analytics reports are also available, as described in Export overview.

Understand full table export

You can export full tables from Analysis Workspace to cloud providers like Google, Azure, Amazon, and Adobe.

Advantages of exporting full tables to the cloud include the ability to export millions of rows, include calculated metrics, structure data output in concatenated values, and more.

When exporting full tables, consider the following:

• Before you export to the cloud, make sure that your tables, your environment, and your permissions meet the export requirements.

• Some features and components are not supported when exporting full tables to the cloud.

Use the following process when exporting full tables to the cloud:

1. Configure a cloud account

2. Configure a location on the account

3. Export a full table from Workspace

4. Access data in the cloud and Manage exports in Adobe

Export full tables from Analysis Workspace

To export full tables from Analysis Workspace:

1. If you haven’t already, configure an export account and location, as described in Configure cloud export accounts.

2. In Analysis Workspace, right-click the Freeform table that contains the data that you want to export.

3. Select Export full table.

   

4. In the New full table export dialog box, specify the following information:

   Field name	Function
   Name	Specify a name for the export. This name displays in the list of exports.
   Tags	You can apply an existing tag to the export or you can create a new tag and apply it. To apply an existing tag to the export, select any tags from the drop-down menu. Any tags in your company are available to apply. To create a new tag, type the name of the new tag, then press Enter. Consider the following when applying tags to an export: Tags that you apply can be filtered on or searched for in the exports table. Tags applied to a project are not automatically applied when exporting a full table, as described in “Configure columns on the exports page” in Manage exports. (Alternatively, when scheduling a full project for export, any tags applied to the project are automatically applied to the export.)
   Description	Add a description to the export. You can choose to view descriptions as a column in the Exports page when viewing exports.
   Data view	Select the data view that contains the components that you want to include in the export. The Data view drop-down menu is located in the upper-left corner of the dialog and can be identified by the data view icon. Note: If you choose a data view that is missing components that are already included in your data table, then you are prompted to clear the data table and re-create it using components that are included in the selected data view.
   Lookback window	Select the reporting time-frame to include in each export file. Options include Today, Yesterday, Last 7 days, Last 30 days, This week, and This month. This option is not displayed when the Export frequency is set to Send now (one-time).
   Data table	Displays the Freeform table that you are exporting. You can modify the data table by dragging components from the left panel to the table. The table dynamically updates as you add components to the canvas. Any segments that were applied to the full table in the project appear at the top of each individual column in the table.
   Clear	Clears the contents of the data table. This allows you to start building a new table directly within the New full table export dialog.
   Export frequency	Set the schedule for how often the export should occur. You can choose Send now (one-time) to send the export only once. When you select this option, the export is initiated immediately. Or, you can choose to send the export on a defined schedule. When sending on a schedule, options include Daily, Weekly, Monthly by day of the week, Monthly by day of the month, Yearly by day of the month, and Yearly by specific date. When selecting an export frequency, consider the following: The options in the Lookback window field change depending on what you select here. Additional configuration fields display depending on the option you choose.
   Starting on	The day and time that the scheduled export should begin. This option is available only when choosing a scheduled export frequency.
   Ending on	The day and time that the scheduled export expires. The scheduled export no longer runs after the date and time that you set. This option is available only when choosing a scheduled export frequency.
   File format	Choose whether the exported data should be in .csv or .json format.
   Account	Select the cloud export account where you want the data to be sent. Or, if you haven’t already configured a cloud account that you want to use, you can configure a new account: Select Add account, then specify the following information: Location account name: Specify a name for the location account. This name appears when creating a location Location account description: Provide a short description of the account to help differentiate it from other accounts of the same account type. Account type: Select the type of cloud account you are exporting to. Available account types are Amazon S3 Role ARN, Google Cloud Platform, Azure SAS, Azure RBAC, Snowflake, and AEP Data Landing Zone. To finish configuring your account, continue with the link below that corresponds to the Account type you selected: AEP Data Landing Zone Amazon S3 Role ARN Google Cloud Platform Azure SAS Azure RBAC Snowflake
   Location name	Select the location on the account where you want the export data to be sent. Or, if you haven’t already configured the location that you want to use on the account that you selected, you can configure a new location: Select Add location, then specify the following information: Name: The name of the location. Description: Provide a short description of the location to help differentiate it from other locations on the account. Location account: Select the account where you want to create the location. To finish configuring your location, continue with the link below that corresponds to the account type that you selected in the Location account field: AEP Data Landing Zone. Amazon S3 Role ARN Google Cloud Platform Azure SAS Azure RBAC Snowflake

5. Select Save to save the export.

   Data is sent to the cloud account that you specified at the frequency that you specified.

6. (Optional) After you create the export, whether you chose to send it now or on a defined schedule, you can view and manage it on the Exports page and view it in the Export logs.

Manage exports

After data is exported from Analysis Workspace, you can edit, re-export, duplicate, tag, or delete existing exports, as described in Manage exports.

View exported data and manifest file

Exported data

Exported data is available as a compressed file in the cloud destination that you configured, as described in Configure cloud export accounts and Configure cloud export locations.

The filename of the compressed file is as follows, depending on whether you chose CSV or JSON as the file format:

• cja-export-{reportInstanceId}-{idx}.csv.gz

• cja-export-{reportInstanceId}-{idx}.json.gz

Manifest file

A manifest file with a filename of cja-export-{reportInstanceId}-{idx}.json.gz is included with any successful export delivery that contains at least one file. The manifest file enables you to confirm that all files were delivered successfully. It includes the following information:

• A list of all files that were delivered

• The MD5 checksum of each file

Advantages of exporting to the cloud

Exporting Customer Journey Analytics data to the cloud allows you to:

• Export to a shared location, such as Adobe Experience Platform Data Landing Zone, Google Cloud Platform, Microsoft Azure, Amazon S3, or Snowflake.

• Store large amounts of historical data.

  This type of data can be used to detect long-term trends in order to gain business intelligence, and ultimately lead to better business decision-making.

• Export full tables that contain thousands or millions of rows (3 million, 30 million, 150 million, or 300 million rows, depending on license type). Other export methods allow a maximum of 50,000 rows.

• Include calculated metrics in the exported Customer Journey Analytics data.

• Structure data output as concatenated values.

• Export one-time or on a schedule. (Also available with other export options.)

• Export files in CSV or JSON format. (Also available with other export options.)

• Export tables that include multiple dimensions.

Export requirements

Minimum requirements

Make sure that your tables, your environment, and your permissions meet the following requirements:

• Tables: All tables must include at least one dimension in the row and one metric in each column in order to be supported with a full-table export.

• Environment: Ensure that the IP addresses and Domains used by Customer Journey Analytics are allowed through their organization’s firewall.

• Permissions: In the Adobe Admin Console, users must be assigned a product profile that has the Full Table Export permission assigned to it in order to export full tables. For information about assigning a permission to a product profile in the Admin Console, see Customer Journey Analytics permission in Admin Console.

  NOTE

  Users who are assigned the Product Admin role always have access to export full tables; these users do not need to be assigned the Full Table Export permission.

Unsupported features

The following features are not supported and are automatically removed from full-table exports:

• Percentages

• Totals

• Search filtering

• Static rows

• Date aligning

• Dynamic dimensions

  For more information, see Dynamic vs static dimension items in freeform tables.

• Dimensions in the first breakdown are converted and added as a secondary dimension in the row of the exported table; any other breakdowns are not included in the table

• Sorting is not supported for most data sets; data might be sorted for small data sets

Unsupported components

The following components are not supported, and Analysis Workspace prompts you to remove them from your table when performing a full-table export:

• Calculated metrics that use basic or advanced functions in the metric definition (see Basic functions and Advanced functions for more information)
• Components that have been restricted by an administrator from being exported (see the Filter on Data Governance policies in data views section in Labels and policies for more information)
• Any dimension that meets all of the following criteria:
  • Was created from a field that is part of an array of objects (similar to multi-value variables in Adobe Analytics)
  • Has persistence enabled
  • Is not using a binding dimension
• More than 5 dimensions and 5 metrics per report (up to 5 dimensions and 5 metrics are supported)
• In table columns:
  • Date ranges
  • Dimensions
• In table rows:
  • Calculated metrics
  • Metrics
  • Date ranges
  • Filters

Attribution behavior

Full table export supports calculated metrics that use a non-default attribution model (as described in the Use non-default attribution model section in Column settings).

If a non-default attribution model is being used in a report, the allocation model being used in the report is either ignored or retained, depending on whether the report has a single dimension or multiple dimensions:

• For reports that include metric attribution in a single dimension: Metric attribution overrides the allocation model as is normally done when using metric attribution.

  For example, a “first touch” metric attribution overrides a “most recent” dimension allocation.

• For reports that include metric attribution on multiple dimensions at the same time: Metric attribution is applied in addition to the dimension allocation model.

  For example, a “first touch” metric attribution is applied in addition to a “most recent” dimension allocation. Additionally, metric attribution will be applied to post-allocated dimension item pairs as if they were single dimension items, rather than to each dimension item independently as is normally done in a Freeform table.

  NOTE

  Multi-dimensional reports are supported only when exporting data to the cloud, as described in this article.

Comparison of Full Table Export (in Customer Journey Analytics) to Data Warehouse (in Adobe Analytics)

If you previously used Data Warehouse to export Adobe Analytics data, the following table can help you understand the differences between exporting full tables in Customer Journey Analytics versus exporting data with Data Warehouse in Adobe Analytics.