Some of the Data Warehouse features described in this article (and other Data Warehouse articles in this section) are available only in the Limited Testing phase of release and might not be available yet in your environment.
For information about which features are not yet available for all customers, as well as for information about the release timeline of these features, see the release notes.
This note will be removed when the functionality is generally available. For information about the Analytics release process, see Adobe Analytics feature releases.
There are various configuration options available when creating a Data Warehouse request. The following information describes how to configure a report destination for the request.
For information about how to begin creating a request, as well as links to other important configuration options, see Create a Data Warehouse request.
Consider the following when configuring a report destination:
We recommend using a cloud account or email for your report destination. Legacy FTP and SFTP accounts are available but are not recommended.
Cloud accounts are associated with your Adobe Analytics user account. Other users cannot use or view cloud accounts that you configure.
Any cloud accounts that you previously configured for Data Feeds are available to use for Data Warehouse.
Cloud accounts that are configured for importing Adobe Analytics classification data from a cloud destination can be used when configuring a report destination. However, any locations that are configured for importing classification data cannot be used.
To configure the destination where Data Warehouse reports are sent:
Begin creating a request in Adobe Analytics by selecting Tools > Data Warehouse > Add.
For additional details, see Create a Data Warehouse request.
On the New Data Warehouse request page, select the Report destination tab.
(Conditional) If you previously configured an account (and a destination on that account) that you want to use as your report destination:
Select the account from the Select account drop-down menu.
Any cloud accounts that you configured for importing Adobe Analytics classification data from a cloud destination are shown here and can be used. However, any locations that are configured for importing classification data cannot be used. Instead, add a new destination as described below.
Select the destination associated with the account from the Select destination drop-down menu.
(Conditional) If you have not previously configured an account:
Select Add account, then specify the following information:
Field | Function |
---|---|
Account type | Select your cloud account type. We recommend having a single account for each account type, with multiple locations as needed within that account. After choosing an account type, fields specific to that account type appear. |
Account name | Specify a name for the account. This name appears when creating a location. |
Account description | Provide a short description of the account to help differentiate it from other accounts of the same account type. |
For configuration instructions, expand the section below that corresponds to the Account type that you selected.
Use any of the following account types when configuring a report destination. For configuration instructions, expand the account type. (Additional legacy destinations are also available, but are not recommended.)
Specify the following information to configure an Amazon S3 Role ARN account:
Field | Function |
---|---|
Role ARN | You must provide a Role ARN (Amazon Resource Name) that Adobe can use to gain access to the Amazon S3 account. To do this, you create an IAM permission policy for the source account, attach the policy to a user, and then create a role for the destination account. For specific information, see this AWS documentation. |
User ARN | The User ARN (Amazon Resource Name) is provided by Adobe. You must attach this user to the policy you created. |
Specify the following information to configure a Google Cloud Platform account:
Field | Function |
---|---|
Project ID | Your Google Cloud project ID. See the Google Cloud documentation about getting a project ID. |
Specify the following information to configure an Azure SAS account:
Field | Function |
---|---|
Application ID | Copy this ID from the Azure application that you created. In Microsoft Azure, this information is located on the Overview tab within your application. For more information, see the Microsoft Azure documentation about how to register an application with the Microsoft identity platform. |
Tenant ID | Copy this ID from the Azure application that you created. In Microsoft Azure, this information is located on the Overview tab within your application. For more information, see the Microsoft Azure documentation about how to register an application with the Microsoft identity platform. |
Key vault URI | The path to the SAS token in Azure Key Vault. To configure Azure SAS, you need to store an SAS token as a secret using Azure Key Vault. For information, see the Microsoft Azure documentation about how to set and retrieve a secret from Azure Key Vault. After the key vault URI is created, add an access policy on the Key Vault in order to grant permission to the Azure application that you created. For information, see the Microsoft Azure documentation about how to assign a Key Vault access policy. |
Key vault secret name | The secret name you created when adding the secret to Azure Key Vault. In Microsoft Azure, this information is located in the Key Vault you created, on the Key Vault settings pages. For information, see the Microsoft Azure documentation about how to set and retrieve a secret from Azure Key Vault. |
Secret | Copy the secret from the Azure application that you created. In Microsoft Azure, this information is located on the Certificates & secrets tab within your application. For more information, see the Microsoft Azure documentation about how to register an application with the Microsoft identity platform. |
Specify the following information to configure an Azure RBAC account:
Field | Function |
---|---|
Application ID | Copy this ID from the Azure application that you created. In Microsoft Azure, this information is located on the Overview tab within your application. For more information, see the Microsoft Azure documentation about how to register an application with the Microsoft identity platform. |
Tenant ID | Copy this ID from the Azure application that you created. In Microsoft Azure, this information is located on the Overview tab within your application. For more information, see the Microsoft Azure documentation about how to register an application with the Microsoft identity platform. |
Secret | Copy the secret from the Azure application that you created. In Microsoft Azure, this information is located on the Certificates & secrets tab within your application. For more information, see the Microsoft Azure documentation about how to register an application with the Microsoft identity platform. |
Specify the following information to configure an email account:
Field | Function |
---|---|
Recipients | Email notifications can be sent to specific users when the report is sent. Specify a single email address or a comma-separated list of email addresses. |
Select Add location, then specify the following information:
Field | Function |
---|---|
Name | The name of the location. |
Description | Provide a short description of the account to help differentiate it from other accounts of the same account type. |
Location account | Select the location account that you created in Add an account. |
In the Location properties section, specify information specific to the account type of your location account.
For configuration instructions, expand the section below that corresponds to the Account type that you selected previously.
Specify the following information to configure an Amazon S3 location:
Field | Function |
---|---|
Bucket name | The bucket within your Amazon S3 account where you want Adobe Analytics data to be sent. Ensure that the User ARN that was provided by Adobe has access to upload files to this bucket. |
Key prefix | The folder within the bucket where you want to put the data. Specify a folder name, then add a backslash after the name to create the folder. For example, folder_name/ |
Specify the following information to configure a Google Cloud Platform location:
Field | Function |
---|---|
Bucket name | The bucket within your GCP account where you want Adobe Analytics data to be sent. Ensure that you have granted permission to the Principal provided by Adobe to upload files to this bucket. For information about granting permissions, see Add a principal to a bucket-level policy in the Google Cloud documentation. |
Key prefix | The folder within the bucket where you want to put the data. Specify a folder name, then add a backslash after the name to create the folder. For example, folder_name/ |
Specify the following information to configure an Azure SAS location:
Field | Function |
---|---|
Container name | The container within the account you specified where you want Adobe Analytics data to be sent. |
Key prefix | The folder within the container where you want to put the data. Specify a folder name, then add a backslash after the name to create the folder. For example, folder_name/ |
Specify the following information to configure an Azure RBAC location:
Field | Function |
---|---|
Container name | The container within the account you specified where you want Adobe Analytics data to be sent. Ensure that you grant permissions to upload files to the Azure application that you created earlier. |
Key prefix | The folder within the container where you want to put the data. Specify a folder name, then add a backslash after the name to create the folder. For example, folder_name/ |
Account name | The Azure storage account. |
Select Save.
You can now import data to the account and location that you configured.
Continue configuring your Data Warehouse request on the Report options tab. For more information, see Configure report options for a Data Warehouse request.
The destinations described in this section are legacy, and are not recommended. Instead, use one of the following destinations when creating a data warehouse destination: Amazon S3, Google Cloud Platform, Azure RBAC, Azure SAS, or Email. See the information above for details about each of these recommended destinations.
The following information provides configuration information for each of the legacy destinations:
Data warehouse data can be delivered to an Adobe or customer-hosted FTP location. Requires an FTP host, username, and password. Use the path field to place feed files in a folder. Folders must already exist; feeds throw an error if the specified path does not exist.
Use the following information when completing the available fields:
ftp://ftp.omniture.com
.SFTP support for data warehouse is available. Requires an SFTP host, username, and the destination site to contain a valid RSA or DSA public key. You can download the appropriate public key when creating the data warehouse destination.
You can send warehouse data directly to Amazon S3 buckets. This destination type requires a Bucket name, an Access Key ID, and a Secret Key. See Amazon S3 bucket naming requirements within the Amazon S3 docs for more information.
The user you provide for uploading data warehouse data must have the following permissions:
The following 16 standard AWS regions are supported (using the appropriate signature algorithm where necessary):
The cn-north-1 region is not supported.
Data warehouse support Azure Blob destinations. Requires a container, account, and a key. Amazon automatically encrypts the data at rest. When you download the data, it gets decrypted automatically. See Create a storage account within the Microsoft Azure docs for more information.
You must implement your own process to manage disk space on the data warehouse destination. Adobe does not delete any data from the server.