A connection lets you integrate datasets from Adobe Experience Platform into Workspace. In order to report on Experience Platform datasets, you first have to establish a connection between datasets in Experience Platform and Workspace.
Click here for a video overview.
To create a CJA Connection, you need the following permissions in Adobe Admin Console:
Adobe Experience Platform:
Customer Journey Analytics
You can combine multiple Experience Platform datasets into a single connection.
Go to https://analytics.adobe.com and sign in with your Adobe ID.
Click the Customer Journey Analytics icon.
Click the Connections tab.
Click Create new connection on the top right.
Choose a sandbox in Experience Platform that contains the dataset/s 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 data sets. Sandboxes are used to control access to data sets. Once you have selected the sandbox, the left rail shows all the datasets in that sandbox that you can pull from.
You cannot access data across sandboxes, i.e., you can only combine datasets that are located within the same sandbox.
Select one or more dataset(s) you want to pull into Customer Journey Analytics and click Add.
(If you have a lot of datasets to choose from, you can search for the right one(s) using the Search datasets search bar above the list of datasets.)
On the right-hand side, you can now configure the dataset/s you have added.
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.
|Dataset Type||Description||Timestamp||Schema||Person ID|
|Event||Data that represents events in time (e.g., web visits, interactions, transactions, POS data, survey data, ad impression data, etc.). For example, this could be typical clickstream data, with a customer ID or a cookie ID, and a timestamp. With Event data, you have flexibility as to which ID is used as the Person ID.||Is automatically set to the default timestamp field from event-based schemas in Experience Platform.||Any built-in or custom schema that is based on an XDM class with the “Time Series” behavior. Examples include “XDM Experience Event” or “XDM Decision Event.”||You can pick which Person ID you want to include. Each dataset schema defined in the Experience Platform can have its own set of one or more identities defined and associated with an Identity Namespace. Any of these can be used as the Person ID. Examples include Cookie ID, Stitched ID, User ID, Tracking Code, etc.|
|Lookup||This data is used to look up values or keys found in your Event or Profile data. For example, you might upload lookup data that maps numeric IDs in your event data to product names. See this use case for an example.||N/A||Any built-in or custom schema that is based on an XDM class with the “Record” behavior, except for the “XDM Individual Profile” class.||N/A|
|Profile||Data that is applied to your visitors, users, or customers in the Event data. For example, allows you to upload CRM data about your customers.||N/A||Any built-in or custom schema that is based on the “XDM Individual Profile” class.||You can pick which Person ID you want to include. Each dataset defined in the Experience Platform has its own set of one or more Person IDs defined, such as Cookie ID, Stitched ID, User ID, Tracking Code, etc.
Note: If you create a connection that includes datasets with different IDs, the reporting will reflect that. To really merge datasets, you need use the same Person ID.
Dataset ID: This ID is automatically generated.
Time stamp: For event datasets only, this setting is automatically set to the default timestamp field from event-based schemas in Experience Platform.
Schema: This is the schema based on which the dataset was created in Adobe Experience Platform.
Person ID: Select a person ID from the dropdown list of available identities. These identities were defined in the dataset schema in the Experience Platform. See below 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. View this video on how to define an identity in Experience Platform.
Click Next to go to the Enable Connection dialog.
Customer Journey Analytics now supports the ability to use the Identity Map for its Person ID. Identity Map is a map data structure that allows someone to upload key -> value pairs. The keys are identity namespaces and the value is a structure that holds the identity value. The Identity Map exists on each row/event uploaded and is populated for each row accordingly.
The Identity Map is available for any dataset that uses a schema based on the ExperienceEvent XDM class. When you select such a dataset to be included in a CJA Connection, you have the option of selecting either a field as the primary ID or the Identity Map:
If you select Identity Map, you get two additional configuration options:
|Use Primary ID Namespace||This instructs CJA, per row, to find the identity in the Identity Map that is marked with a primary=true attribute and use that as the Person ID for that row. This means that this is the primary key that will be used in Experience Platform for partitioning. It is also the prime candidate for usage as CJA’s visitor ID (depending on how the dataset is configured in a CJA Connection).|
|Namespace||(This option is only available if you do not use the Primary ID Namespace.) Identity namespaces are a component of Adobe Experience Platform Identity Service that serve as indicators of the context to which an identity relates. If you specify a namespace, CJA will search each row’s Identity Map for this namespace key and use the identity under that namespace as the person ID for that row. Note that since CJA cannot do a full dataset scan of all rows to determine which namespaces are actually present, all possible namespaces are listed in the dropdown. You need to know which namespaces are specified in the data; this cannot be auto-detected.|
This table shows the two configuration options when edge cases are present and how they are handled:
|Option||No IDs are present in Identity Map||No IDs are marked as primary||Multiple IDs are marked as primary||Single ID is marked as primary||Invalid namespace with an ID marked as primary|
|“Use Primary ID Namespace” checked||The row is dropped by CJA.||The row is dropped by CJA, as no primary ID is specified.||All IDs marked as primary, under all namespaces, are extracted into a list. They are then alphabetically sorted; with this new sorting, the first namespace with its first ID is used as the Person ID.||The single ID marked as primary is used as the Person ID.||Even though the namespace may be invalid (not present in AEP), CJA will use the primary ID under that namespace as the Person ID.|
|Specific Identity Map namespace selected||The row is dropped by CJA.||All IDs under the selected namespace are extracted into a list and the first is used as the Person ID.||All IDs under the selected namespace are extracted into a list and the first is used as the Person ID.||All IDs under the selected namespace are extracted into a list and the first is used as the Person ID.||All IDs under the selected namespace are extracted into a list and the first is used as the Person ID. (Only a valid namespace can be selected at Connection creation time, so it is not possible for an invalid namespace/ID to be used as Person ID)|
To enable a connection, define these settings for the entire connection, i.e. all the datasets in the connection:
|Name Connection||Give the connection a descriptive name. The connection cannot be saved without a name.|
|Description||Add more detail to distinguish this connection from others.|
|Datasets||The datasets that are included in this connection.|
|Automatically import all new datasets in this connection, beginning today.||Select this option if you want to establish an ongoing connection, so that any new data batches that get added to the datasets in this connection automatically flow into Workspace.|
|Import all existing data||When you select this option and save the connection, all of the existing (historical) data from Experience Platform for all datasets in this connection will be imported or backfilled. In the future, all existing historical data for any new dataset(s) added to this saved connection will also be automatically imported. See also Backfill historical data below.
Note that, once this connection is saved, this setting cannot be changed.
|Average number of daily events||You are required to specify the average number of daily events to be imported (new data and backfill data) for all the datasets in the connection. Select one option from the drop-down menu. This is so that Adobe can allocate sufficient space for this data.
If you do not know the average number of daily events your company is going to import, you can do a simple SQL query in Adobe Experience Platform Query Services to find out.
See “Calculate the average number of daily events” below.
Click Save and create data view. For documentation, see create a data view.
Import all existing data lets you backfill historical data. Keep this in mind:
This calculation has to be done for every dataset in the connection.
Go to Adobe Experience Platform Query Services and create a new query.
The query would look like this:
Select AVG(A.total_events) from (Select DISTINCT COUNT (*) as total_events, date(TIMESTAMP) from analytics_demo_data GROUP BY 2 Having total_events>0) A;
Show Tablesquery to show all the datasets that exist in AEP.