Before you can export Customer Journey Analytics reports to a cloud destination as described in Export Customer Journey Analytics reports to the cloud, you need to add and configure the location where you want the data to be sent.
This process consists of adding and configuring the account (such as Amazon S3, Google Cloud Platform, and so forth) as described in Configure cloud export accounts, and then adding and configuring the location within that account (such as a folder within the account) as described in this article.
For information about how to manage existing locations, including viewing, editing, and deleting locations, see Manage cloud export locations and accounts.
You need to add an account before you can add a location. If you haven’t already, add an account as described in Configure cloud export accounts.
In Customer Journey Analytics, select Components > Exports.
Select the Locations tab, then select Add location.
Or
Select the Location accounts tab, select the 3-dot icon on an existing account where you want to add a location, then select Add location.
The Location dialog displays.
Specify the following information:
Field | Function |
---|---|
Name | The name of the location. |
Description | Provide a short description of the location to help differentiate it from other locations on the account. |
Make location available to all users in your organization | Enable this option to allow other users in your organization to use the location. Consider the following when sharing locations:
|
Location account | Select the account where you want to create the location. For information about how to create an account, see Configure cloud export accounts. |
In the Location properties section, specify information specific to the account type of your location account.
Continue with the section below that corresponds to the account type that you selected in the Location account field.
When exporting Customer Journey Analytics reports to Adobe Experience Platform Data Landing Zone, make sure that you download the data within 7 days, then delete it from AEP Data Landing Zone. After 7 days, the data is automatically deleted from AEP Data Landing Zone.
Begin creating a cloud export location in either of the following ways:
From the Exports page as described above, in Begin creating a cloud export location
In the Location properties section of the Add location dialog box, specify the following information to configure an Adobe Experience Platform Data Landing Zone location:
Field | Function |
---|---|
Prefix | The folder within the container where you want to put the data. Specify a folder name, then add a slash after the name to create the folder. For example, folder_name/ |
Select Save.
You can now export data from Analysis Workspace to the account and location that you configured. For information about how to export data to the cloud, see Export project data to the cloud.
The easiest way to access your data in AEP Data Landing Zone is to use the Microsoft Azure Storage Explorer. This is the same tool that is used in the instructions to configure the AEP Data Landing Zone account.
Open the Microsoft Azure Storage Explorer.
Go to Storage Accounts > (Attached Containers) > Blob Containers > cjaexport-number > your_container_name.
The folder name cjaexport-number is the default name provided by Azure Storage Explorer. If you have only a single connection associated with your SAS URI (which is normal), then the name of this folder will be cjaexport-1.
Select the export that you want to download, then select Download to download.
Begin creating a cloud export location in either of the following ways:
From the Exports page as described above, in Begin creating a cloud export location
In the Location properties section of the Add location dialog box, specify the following information to configure an Amazon S3 Role ARN location:
Field | Function |
---|---|
Bucket | The bucket within your Amazon S3 account where you want Customer Journey Analytics data to be sent. Ensure that the User ARN that was provided by Adobe has the Bucket names must meet specific naming rules. For example, they must be between 3 to 63 characters long, can consist only of lowercase letters, numbers, dots (.), and hyphens (-), and must begin and end with a letter or number. A complete list of naming rules are available in the AWS documentation. |
Prefix | The folder within the bucket where you want to put the data. Specify a folder name, then add a slash after the name to create the folder. For example, folder_name/ |
Select Save.
You can now export data from Analysis Workspace to the account and location that you configured. For information about how to export data to the cloud, see Export project data to the cloud.
Begin creating a cloud export location in either of the following ways:
From the Exports page as described above, in Begin creating a cloud export location
In the Location properties section of the Add location dialog box, specify the following information to configure a Google Cloud Platform location:
Field | Function |
---|---|
Bucket | The bucket within your GCP account where you want Customer Journey Analytics data to be sent. Ensure that you have granted the For information about granting permissions, see Add a principal to a bucket-level policy in the Google Cloud documentation. If your organization is using Organization policy constraints to allow only the Google Cloud Platform account in your allow list, you need the following Adobe-owned Google Cloud Platform organization ID:
|
Prefix | The folder within the bucket where you want to put the data. Specify a folder name, then add a slash after the name to create the folder. For example, folder_name/ |
Select Save.
You can now export data from Analysis Workspace to the account and location that you configured. For information about how to export data to the cloud, see Export project data to the cloud.
Begin creating a cloud export location in either of the following ways:
From the Exports page as described above, in Begin creating a cloud export location
In the Location properties section of the Add location dialog box, specify the following information to configure an Azure SAS location:
Field | Function |
---|---|
Container name | The container within the account you specified where you want Customer Journey Analytics data to be sent. |
Prefix | The folder within the container where you want to put the data. Specify a folder name, then add a slash after the name to create the folder. For example, folder_name/ Make sure that the SAS token store that you specified in the Key Vault secret name field when configuring the Azure SAS account has the If you want the SAS token to also overwrite files, make sure that the SAS token store has the For more information, see Blob storage resources in the Azure Blob Storage documentation. |
Select Save.
You can now export data from Analysis Workspace to the account and location that you configured. For information about how to export data to the cloud, see Export project data to the cloud.
Begin creating a cloud export location in either of the following ways:
From the Exports page as described above, in Begin creating a cloud export location
In the Location properties section of the Add location dialog box, specify the following information to configure an Azure RBAC location:
Field | Function |
---|---|
Container | The container within the account you specified where you want Customer Journey Analytics data to be sent. Ensure that you grant permissions to upload files to the Azure application that you created earlier. |
Prefix | The folder within the container where you want to put the data. Specify a folder name, then add a slash after the name to create the folder. For example, folder_name/ Make sure the Application ID that you specified when configuring the Azure RBAC account has been granted the For more information, see Azure built-in roles. |
Account | The Azure storage account. |
Select Save.
You can now export data from Analysis Workspace to the account and location that you configured. For information about how to export data to the cloud, see Export project data to the cloud.
Begin creating a cloud export location in either of the following ways:
From the Exports page as described above, in Begin creating a cloud export location
In the Location properties section of the Add location dialog box, specify the following information to configure a Snowflake location:
Field | Function |
---|---|
DB | The specified database should be an existing database. The role you created needs to have privileges to access this database. This is the database associated with the stage name. You can grant this role privileges to the database in Snowflake using the following command: For more information, see the Database, Schema, and Share Commands page in the Snowflake documentation. |
Schema | The specified schema should be an existing schema. The role you created needs to have privileges to access this schema. This is the schema associated with the stage name. You can grant the role that you created privileges to the schema in Snowflake using the following command: For more information, see the Database, Schema, and Share Commands page in the Snowflake documentation. |
Stage name | The name of the internal stage where data files are stored in Snowflake. Make sure that the role you specified on the account has Read and Write access to this stage name. (Because you are granting Read and Write access, we recommend using a stage that is used only by Adobe.) You can grant Read and Write access to the stage name in Snowflake using the following command: For information about granting privileges to a role, see Grant privileges in the Snowflake documentation. For more information about the stage name, see the Choosing an Internal Stage for Local Files page in the Snowflake documentation. |
Stage path | The path to the location where data files are stored in Snowflake. For more information, see the Choosing an Internal Stage for Local Files page in the Snowflake documentation. |
Select Save.
You can now export data from Analysis Workspace to the account and location that you configured. For information about how to export data to the cloud, see Export project data to the cloud.