See
Prerequisites
The maximum number of datasets you can add to a connection is capped at 100. The mix depends on which Customer Journey Analytics package your company has purchased.
Contact your administrator if you’re unsure which Customer Journey Analytics package you have.
Select package | Foundation package |
---|---|
Any combination of event, profile, lookup, or summary datasets, adding up to 100 | One event dataset per connection |
Up to 99 profile, lookup, or summary datasets per connection |
Create a connection
To create a connection:
- In Customer Journey Analytics, select Connections, optionally from Data management, in the top menu.
- Select Create new connection.
You can now edit the details for your connection.
Edit a connection
How you edit the connection depends on the Customer Journey Analytics package you have licensed:
Customer Journey Analytics
In the Connections > Name of the connection screen:
-
Configure the connection settings.
Setting Description Connection name Enter a unique name for the connection. Connection description Describe the purpose of this connection. Tags Specify tags to add tags to your connection so you can use these tags to search for the connection at a later stage. Enable rolling data window This checkbox, if checked, lets you define Customer Journey Analytics data retention as a rolling window in months (1 month, 3 months, 6 months, and so on), at the connection level.
Data retention is based on event dataset timestamps and applies to event datasets only. No rolling data window setting exists for profile or lookup datasets, since there are no applicable timestamps. However, if your connection includes any profile or lookup datasets (besides one or more event datasets), that data is retained for the same time period.
The main benefit is that you store or report only on data that is applicable and useful and delete older data that is no longer useful. It helps you stay under your contract limits and reduces the risk of overage cost.
- If you leave the default (unchecked), the Adobe Experience Platform data retention setting supersedes the retention period. If you have 25 months’ worth of data in Experience Platform, Customer Journey Analytics gets 25 months of data through backfill. If you deleted 10 of those months in Experience Platform, Customer Journey Analytics would retain the remaining 15 months.
- If you enable a rolling data window, specify in Select number of months the number of months for which you enable the rolling data window.
Sandbox Choose a sandbox in Experience Platform that contains the datasets for which you want to create a connection.
Adobe Experience Platform provides sandboxes which partition a single Platform instance into separate virtual environments to help develop and evolve digital experience applications. You can think of sandboxes as “data silos” that contain datasets. Sandboxes are used to control access to datasets.
Once you have selected the sandbox, the left rail shows all the datasets in that sandbox that you can pull from.
Add datasets Select For the datasets you have configured, the table of datasets shows the following columns:
Column Description Dataset name Select one or more datasets that you want to pull into Customer Journey Analytics and select Add.
(If you have many datasets to choose from, you can search for the right one(s) using the Search datasets search bar above the list of datasets.)
Select
Last updated For event datasets only, this setting is automatically set to the default timestamp field from event-based schemas in Experience Platform. “N/A” means that this dataset contains no data. Number of records The total records in the previous month for the dataset in Experience Platform. Schema The schema based on which the dataset was created in Adobe Experience Platform. Dataset type For each dataset that you added to this connection, Customer Journey Analytics automatically sets the dataset type based on the data coming in. There are 3 different dataset types: Event data, Profile data, and Lookup data. See the table below for an explanation of dataset types. Granularity The granularity of the data in the dataset; only applicable for summary datasets. Data source type The data source type of the dataset. Not applicable for summary datasets. Person ID The Person ID that is used to support person-based reporting for the dataset. Key The key that is used for a lookup dataset. Matching Key The matching key that is used for a lookup dataset. Import new data The status of importing new data for the dataset:
Backfill data The status of backfill data for the dataset.
You can search for a specific dataset using the
Customer Journey Analytics B2B Edition
In the Connections > Name of the connection screen:
-
Configure the connection settings.
Setting Description Connection name Enter a unique name for the connection. Connection description Describe the purpose of this connection. Tags Specify tags to add tags to your connection so you can use these tags to search for the connection at a later stage. Primary ID Select the proper primary ID for your connection:
As soon as you add one or more datasets to your connection, you are no longer able to change the primary ID.
The selection of the primary ID defines whether the connection is person-based or account-based. The connection base determines the available settings for certain types of datasets.Optional containers If you have selected
- Global account: enables configuration of global accounts in a connection.
- Opportunity: enables configuration of opportunities in a connection.
- Buying group: enables configuration of buying groups in a connection.
Sandbox Choose a sandbox in Experience Platform that contains the datasets to which you want to create a connection.
Adobe Experience Platform provides sandboxes which partition a single Platform instance into separate virtual environments to help develop and evolve digital experience applications. You can think of sandboxes as “data silos” that contain datasets. Sandboxes are used to control access to datasets.
Once you have selected the sandbox, the left rail shows all the datasets in that sandbox that you can pull from.
Enable rolling data window This checkbox, if checked, lets you define Customer Journey Analytics data retention as a rolling window in months (1 month, 3 months, 6 months, and so on), at the connection level.
Data retention is based on event dataset timestamps and applies to event datasets only. No rolling data window setting exists for profile or lookup datasets, since there are no applicable timestamps. However, if your connection includes any profile or lookup datasets (besides one or more event datasets), that data is retained for the same time period.
The main benefit is that you store or report only on data that is applicable and useful and delete older data that is no longer useful. It helps you stay under your contract limits and reduces the risk of overage cost.
- If you leave the default (unchecked), the Adobe Experience Platform data retention setting supersedes the retention period. If you have 25 months’ worth of data in Experience Platform, Customer Journey Analytics gets 25 months of data through backfill. If you deleted 10 of those months in Platform, Customer Journey Analytics would retain the remaining 15 months.
- If you enable a rolling data window, specify in Select number of months the number of months for which you enable the rolling data window.
Add datasets Select For the datasets you have configured, the table of datasets shows the following columns:
Column Description Dataset name Select one or more datasets that you want to pull into Customer Journey Analytics and select Add.
(If you have many datasets to choose from, you can search for the right one(s) using the Search datasets search bar above the list of datasets.)
Select
Last updated For event datasets only, this setting is automatically set to the default timestamp field from event-based schemas in Experience Platform. “N/A” means that this dataset contains no data. Number of records The total records in the previous month for the dataset in Experience Platform. Schema The schema based on which the dataset was created in Adobe Experience Platform. Dataset type For each dataset that you added to this connection, Customer Journey Analytics automatically sets the dataset type based on the data coming in. There are 3 different dataset types: Event data, Profile data, and Lookup data. See the table below for an explanation of dataset types. Granularity The granularity of the data in the dataset; only applicable for summary datasets. Data source type The data source type of the dataset. Not applicable for summary datasets. Account ID (only displayed for account-based connections) The Account ID that is used to support account-based reporting for the dataset. Global Account ID (only displayed for account-based connections) The Global Account ID that is used to support account-based reporting for the dataset. Buying Group ID (only displayed for account-based connections) The Buying Group ID that is used to lookup buying group data. Opportunity ID (only displayed for account-based connections) The Opportunity ID that is used to lookup opportunity data. Person ID The Person ID that is used to support person-based reporting for the dataset. Key The key that is used for a lookup dataset. Matching Key The matching key that is used for a lookup dataset. Import new data The status of importing new data for the dataset:
Backfill data The status of backfill data for the dataset.
You can search for a specific dataset using the
-
Datasets
You add one or more datasets or edit existing datasets as part of connection workflow.
Add datasets
You can add one or more Experience Platform datasets when you create or edit a connection.
-
In Connection > Name of the connection interface, select
-
In the ➊ Select datasets step, you see a list of the Experience Platform datasets.
For each dataset, the list shows:
Column Description Dataset Name of the dataset. Select the name to direct you to the dataset in Experience Platform. Select Dataset type The type of dataset: Event, Profile, Lookup, or Summary. Number of records The total records in the previous month for the dataset in Experience Platform. Schema The schema for the dataset. Select the name to direct you to the schema in Experience Platform. Last batch The state of the last batch ingested in Experience Platform. See Batch states more information. Dataset ID The id of the dataset. Last updated The last updated timestamp of the dataset. - To change the columns displayed for the list of datasets, select
- To search for a specific dataset, use the
- To toggle between showing or hiding the selected datasets, select
- To remove a dataset from the list of selected datasets, use
- To display details of a dataset, select
- To change the columns displayed for the list of datasets, select
-
Select one or more datasets and select Next. At least one event or summary dataset must be part of the connection.
-
Configure the settings for each of the selected datasets, one by one, in the ➋ Datasets settings step of the Add datasets dialog.
-
Select Add datasets to add the configured datasets to the connection. You are notified when you have not provided all required settings for each of the datasets you want to add.
Alternatively, you can select Cancel to cancel the addition of datasets to the connection. Or select Back to step back to the ➊ Select datasets step.
Edit a dataset
To edit a dataset that is already configured for a connection, in the Connections > Name of the connection interface:
-
Select
-
Select
-
Configure the dataset settings in the Edit dataset: Dataset name dialog.
-
Select Apply to apply the dataset settings. Select Cancel to cancel.
Dataset settings
When you add datasets or edit an existing dataset, you configure the dataset settings for each dataset. The settings available depend on the type of dataset and, for some dataset types, on the type of connection (person-based or B2B Edition account-based.).
All datasets and dataset types have general settings and details, such as whether or not to import new data and request backfills.
Event dataset
The specific settings for an event dataset are dependent on the type of connection.
Person-based connection
For an event dataset in a person-based connection, you can specify:
Setting | Description |
---|---|
Person ID |
Select a Person ID from the drop-down menu of available identities. These identities were defined in the dataset schema in Experience Platform. See Use Identity Map as a Person ID for information on how to use Identity Map as a Person ID. If there are no Person IDs to choose from, that means no Person IDs are defined in the schema. See Define identity fields in the UI for more information. The value for the selected Person ID is considered to be case sensitive. For example, If a record doesn’t contain a value for the identity you have selected as the Person ID for the event dataset, the record is skipped. |
Timestamp | This setting is automatically set to the default timestamp field from event-based schemas in Experience Platform. |
Data source type |
Select a type of data source. Types of data sources include:
This field is used to survey the types of data sources in use. |
Data source description | A description of the data source when you have selected Other as the data source type. |
Account-based connection
For an event dataset in an account-based connection, you can specify:
Setting | Description |
---|---|
Account ID |
Select a Global Account ID (the unique identifier for an account) from the available identities defined in the dataset schema in the Experience Platform. Applicable when you have added Global Account as a container to your connection. If a record doesn’t contain a value for the identity you have selected as the Account ID for the event dataset, the record is skipped. |
Global Account ID | Select an Account ID (the unique identifier for an account) from the available identities defined in the dataset schema in the Experience Platform. Applicable when you have not added Global Account as a container to your connection. |
Opportunity ID | Select an Opportunity ID (the unique identifier for an opportunity) from the available identities defined in the dataset schema in the Experience Platform. |
Buying Group ID | Select a Buying Group ID (the unique identifier for a buying group) from the available identities defined in the dataset schema in the Experience Platform. |
Person ID |
Select a Person ID from the drop-down menu of available identities. These identities were defined in the dataset schema in the Experience Platform. See Use Identity Map as a Person ID for information on how to use Identity Map as a Person ID. If there are no Person IDs to choose from, that means one or more Person IDs have not been defined in the schema. See Define identity fields in the UI for more information. The value for the selected Person ID is considered to be case sensitive. For example, |
Timestamp | This setting is automatically set to the default timestamp field from event-based schemas in Experience Platform. |
Data source type |
Select a type of data source. Types of data sources include:
This field is used to survey the types of data sources in use. |
Data source description | A description of the data source when you have selected Other as the data source type. |
Profile dataset
The specific settings for a profile dataset are dependent on the type of connection.
Person-based connection
For a profile dataset in a person-based connection, you specify:
Setting | Description |
---|---|
Person ID |
Select a Person ID from the drop-down menu of available identities. These identities were defined in the dataset schema in Experience Platform. See Use Identity Map as a Person ID for information on how to use Identity Map as a Person ID. If there are no Person IDs to choose from, no Person IDs are defined in the schema. See Define identity fields in the UI for more information. The value for the selected Person ID is considered to be case sensitive. For example, If a record doesn’t contain a value for the identity you have selected as the Person ID for the profile dataset, the record is skipped. |
Data source type |
Select a type of data source. Types of data sources include:
This field is used to survey the types of data sources in use. |
Data source description | A description of the data source when you have selected Other as the data source type. |
Account-based connection
For a profile dataset in an account-based connection, you specify:
Setting | Description |
---|---|
Person ID |
Select a Person ID from the drop-down menu of available identities. These identities were defined in the dataset schema in Experience Platform. See Use Identity Map as a Person ID for information on how to use Identity Map as a Person ID. If there are no Person IDs to choose from, no Person IDs are defined in the schema. See Define identity fields in the UI for more information. The value for the selected Person ID is considered to be case sensitive. For example, If a record doesn’t contain a value for the identity you have selected as the Person ID for the profile dataset, the record is skipped. |
Global Account field | Select a global account field to support account-based reporting for the dataset from the drop-down menu of available identities. Applicable when you have added Global Account as a container to your connection. |
Account field | Select an account field to support account-based reporting for the dataset from the drop-down menu of available identities. Applicable when you have not added Global Account as a container to your connection. |
Data source type |
Select a type of data source. Types of data sources include:
This field is used to survey the types of data sources in use. |
Data source description | A description of the data source when you have selected Other as the data source type. |
Lookup dataset
The specific settings for a lookup dataset are dependent on the type of connection.
Person-based connection
For a lookup dataset in a person-based connection, you specify:
Settings | Description |
---|---|
Key |
The key to use for a Lookup dataset. If a record doesn’t contain a value for the key you have selected for the lookup dataset, the record is skipped. |
Matching key | The matching key to join on in one of the event datasets. If this list is empty, you probably haven’t added or configured an event dataset. |
Data source type |
Select a type of data source. Types of data sources include:
This field is used to survey the types of data sources in use. |
Data source description | A description of the data source when you have selected Other as the data source type. |
Transform dataset | For specific B2B lookup datasets, you can enable the transformation of a dataset for proper B2B person-based reporting scenarios. See Transform datasets for B2B lookups for more information. |
Account-based connection
For a lookup dataset in an account-based connection, you can specify:
Settings | Description |
---|---|
Key |
The key to use for a Lookup dataset. If a record doesn’t contain a value for the key you have selected for the lookup dataset, the record is skipped. |
Matching key type | Select how to join the datasets: based on a Match by field or Match by container. See Match by container of field for more information. |
Matching key |
The matching key to join on in one of the event datasets. If this list is empty, you probably haven’t added or configured an event dataset.
|
Global Account field | The global Account ID to use for account-based reporting. |
Summary dataset
The specific settings for a summary dataset are:
Setting | Description |
---|---|
Timestamp | This setting is automatically set to the default timestamp field from event-based schemas in Experience Platform. |
Timezone | Select the appropriate timezone for the time-series summary data. |
Granularity | Represents the time frame used to aggregate summary data by, currently either hour or day. Derived from the data in the dataset. |
General dataset settings and details
Each (type of dataset) has the following common settings:
Setting | Description |
---|---|
Import new data | Enable this option if you want to establish an ongoing connection. With an ongoing connection new data batches that are added to the datasets are available automatically in Workspace. |
Dataset backfill |
Enable Backfill all existing data to ensure that all existing data is backfilled.
For each entry, select
|
Batch status |
Possible status indicators are:
|
Dataset ID | This ID is automatically generated. |
Description | The description given to this dataset when the dataset was created. |
Number of records | The dataset’s size. |
Schema | The schema based on which the dataset was created in Adobe Experience Platform. |
Dataset | The name of the dataset. |
Preview: dataset name | Previews the dataset for first 10 rows and first 10 columns. |
| You can delete a dataset without deleting the whole connection. The deletion of a dataset from a connection reduces the costs involved in data ingestion and the cumbersome process of recreating the whole connection and associated data views. |