Manage connections

Once Admin users have created one or more connections, they can manage them in the Connections Manager. The latest update to the Connection experience adds two important capabilities within the Connection Details page, described further down on this page:

  • It lets you check the status of your connection’s datasets and of the ingestion process. This status check lets you know when your data is available so that you can go into Analysis Workspace and start analysis.

  • It lets you identify any data discrepancies due to misconfiguration. Are you missing any rows? If yes, what rows are missing and why? Did you misconfigure connections and cause missing data in CJA?

NOTE

This functionality will be generally available on September 20, 2021.

Connections Manager

The Connections Manager allows you to:

  • View all your connections at a glance, including the owner, the sandbox, and when they were created and modified.
  • View all datasets in a connection.
  • Check the status of a connection.
  • Delete a connection.
  • Rename a connection.
  • Create a data view from a connection.

Connection Manager settings

Setting Description
Name The connection’s friendly name. When you click the hyperlinked name, you get to the Connection details page described below.
Connection info Click the info icon next to the connection name to view the following information:View connection info
Edit a connection Click the ellipsis (…) next to the connection name, then click Edit.Edit connection For more information, see “Edit connection” below.
Delete a connection Click the ellipsis (…) next to the connection name, then click Delete. More information under the “Delete connections” heading below.
Create data view Click the ellipsis (…) next to the connection name, then click Create data view. This action creates a new data view based on this connection. Learn more
Datasets The datasets that are part of the connection. You can click the hyperlink to view all the datasets in the connection. Clicking on a dataset opens that dataset in Adobe Experience Platform, in a new tab.
Sandbox The Adobe Experience Platform sandbox from which this connection draws its datasets. This sandbox was selected when you first created the connection. It cannot be changed.
Owner The person who created the connection.
Import Data Sets Lets you enable or disable what used to be called “data streaming.”
Date Created The date when the connection was first created.
Last Modified The date when the connection was last updated.

Delete connections

Only Admins have permission to delete a connection. This action does not show up for non-admins.

  1. Click the ellipsis (…) next to the connection name.
  2. Click Delete.

When you delete a connection in Customer Journey Analytics, an error message will indicate that:

  • Any data views that were created based on the deleted connection no longer work.
  • Similarly, any Workspace projects that depend on data views in the deleted connection will cease working.

Learn more about deletion implications.

Search for a connection or dataset

You can search for connections using the Search bar at the top, underneath the Connections title.

Sort connections

You can sort connections by clicking each column header and sorting up or down.

Connection Details page

The new Connections Details page gives you a very detailed view of the status of a connection.

It lets you:

  • Check the status of your connection’s datasets and of the ingestion process.
  • Identify configuration problems that lead to skipped, or deleted records.
  • See when the data is available for reporting.
IMPORTANT

Any data ingested before August 13, 2021, is not reflected in this Connections dialog.

Here are the widgets and settings explained:

Connection Details settings

Widget/Setting Description
Dataset selector Lets you pick one or all datasets in the connection. You cannot multi-select datasets. Defaults to All datasets.
Calendar/Date Ranges The date range indicates when you added data to the connection. All standard calendar presets are included. You can customize the date range, but no custom date ranges show up in the dropdown.
Records of event data available widget Represents the total number of event dataset rows available for reporting, for the entire connection. This count is independent of any calendar settings. It changes if you select a dataset from the dataset selector or by selecting a dataset in the table. ( Note that there is a latency of 1-2 hours to get the data to appear in reporting, once it is added.)
Metrics widget Summarizes the event records added/skipped/deleted, and the number of batches added, for the dataset and date range you have selected.
Records added widget Indicates how many rows were added in the selected time period, for the dataset and date range you have selected. Updated every 10 minutes. Note: Data for Records added includes only event data at this time, not profile or lookup data.
Records skipped widget Indicates how many rows were skipped in the selected time period, for the dataset and date range you have selected. Reasons for skipping records include: Missing timestamps, missing or invalid person ID, etc. Updated every 10 minutes.

Invalid person IDs (such as “undefined”, or “00000000”, or any combination of numbers and letters in a Person ID that appears in an event more than 1 million times in a given month) cannot be attributed to any specific user or person. They cannot be ingested into the system and result in error-prone ingestion and reporting. To fix invalid person IDs, you have 3 options:

  • Use Cross-Channel Analytics to populate the undefined or all-zero user IDs with valid user IDs.
  • Blank out the user ID, which will them also be skipped during ingestion (preferable to invalid or all-zero user IDs).
  • Fix any invalid user IDs in your system before ingesting the data.

Note: Data for Records skipped includes only event data at this time, not profile or lookup data.

Records deleted widget Indicates how many rows were deleted in the selected time period, for the dataset and date range you have selected. Someone might have deleted a dataset in Experience Platform, for example. Updated every 10 minutes. Note: Data for Records deleted includes only event data at this time, not profile or lookup data.
Dataset search box You can search by dataset name or Dataset ID.
Datasets Shows the datasets that are part of the connection. You can click the hyperlink to view all the datasets in the connection.
Dataset ID This ID is automatically generated by Adobe Experience Platform.
Batches Indicates how many data batches have been added to this dataset.
Last added Shows the timestamp for the last added batch to this dataset.
Dataset type The dataset type for this dataset can be Event, Lookup, or Profile. Learn more
Schema The Adobe Experience Platform schema that the datasets in this connection are based on.

Right-hand rail settings at connection level

Setting Description
Refresh Refresh the connection to allow recently added records to be reflected.
Delete Delete this connection.
Create data view Create a new data view based on this connection. Learn more
Connection name Shows the friendly name of the connection.
Connection description Shows a more detailed description that ideally describes the purpose of this connection.
Sandbox The Adobe Experience Platform sandbox from which this connection draws its dataset/s. This sandbox was selected when you first created the connection. It cannot be changed.
Connection ID This ID is system generated in Adobe Experience Platform.
Data views using connection Lists all the data views that use this connection.
Import new data (On/Off) Indicates whether new batches of data should or should not be added to the historical (backfill) data.
Backfill data Backfill (historical) data is tracked in 3 states: In queue, In progress (with progress percentage indicated), and Complete.
Created by Shows the name of the person who create the connection.
Last modified Shows the date and time of last change to the connection.
Last modified by Shows the person who last modified the connection.

Right-hand rail settings at dataset level

Setting Description
Person ID Shows an identity that was defined in the dataset schema in the Experience Platform. This is the Person ID you chose during the creation of the connection. 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 across datasets.
Records available Represents the total number of rows ingested for this dataset, for the particular time period selected through the calendar. There is no latency in terms of getting the data to appear in reporting, once it is added. (The exception is that when you create a brand-new connection, there will be latency.
Records added Indicates how many rows were added in the selected time period. Note: Data for Records added includes only event data at this time, not profile or lookup data.
Records deleted Indicates how many records were deleted during the selected time period. Note: Data for Records deleted includes only event data at this time, not profile or lookup data.
Batches added Indicates how many data batches were added into this dataset.
Records skipped Indicates how many rows were skipped during ingestion in the selected time period.

Reasons for skipping records include: Missing timestamps, missing or invalid person ID, etc. Updated every 10 minutes.

Invalid person IDs (such as “undefined”, or “00000000”, or any combination of numbers and letters in a Person ID that appears in an event more than 1 million times in a given month) cannot be attributed to any specific user or person. They cannot be ingested into the system and result in error-prone ingestion and reporting. To fix invalid person IDs, you have 3 options:

  • Use Cross-Channel Analytics to populate the undefined or all-zero user IDs with valid user IDs.
  • Blank out the user ID, which will them also be skipped during ingestion (preferable to invalid or all-zero user IDs).
  • Fix any invalid user IDs in your system before ingesting the data.

Note: Data for Records skipped includes only event data at this time, not profile or lookup data.

Last added Indicates when the last batch was added.
Dataset type Either Event, Lookup, or Profile. Learn more
Schema Shows the Adobe Experience Platform schema that this dataset is based on.
Dataset ID This ID is system generated in Adobe Experience Platform.

Edit connection

Allows Admins to edit the connection. Select a connection, then click Edit Connection to get to this dialog. Here, you can do the following:

  • Start and stop importing new data. This process was formerly known as “data streaming”.
  • Rename a connection.
  • Refresh the dataset/s.
  • Remove dataset/s from the connections.

Set rolling window for Connection data retention

IMPORTANT

Please contact Customer Care or your Adobe account manager to have this setting implemented. It is not yet available via the CJA UI.

This setting lets you define CJA data retention as a rolling window in months (3 months, 6 months, etc.), at a connection level (not at a dataset level). Data retention is based on event dataset timestamps and applies to event datasets only. No data retention setting exists for profile or lookup datasets since there are no applicable timestamps. 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.

On this page