[Beta]{class="badge informative"}
Use stitching
You can enable stitching on one or more event datasets you have configured as part of your connection. The Customer Journey Analytics package that you have licensed determines the number of event datasets you can enable for stitching .
You can enable stitching as part of the dataset settings for an event dataset when you create a connection or when you edit a connection.
Prerequisites
To enable stitching on an event dataset within the Connections UI:
-
The schema on which the dataset is based should have:
- multiple fields that are configured as an identity, and which allows you to select different values for a persistent ID and a person ID.
- at least one field that is marked as primary identity with an associated namespace in case you want to use Identity Map and the primary identity namespace for persistent ID or person ID.
-
The event dataset must be enabled for the Identity service in case you want to use the Identity Graph and graph-based stitching.
Preflight checks
If you meet the prerequisites, you might want to perform some preflight checks on the data in the event dataset before you enable identity stitching:
-
Ensure that identities are marked properly in the schema for the event dataset. See Identity namespace overview.
-
Verify identity coverage for both persistent ID and person ID:
-
Persistent ID: Query 7 days of data where your persistent ID field is not null and divide by a query of 7 days of data for all events in your dataset. This percentage should be above 95%.
Example of a query you could use for verification:
code language-sql SELECT COUNT(*) AS total_events, COUNT({PERSISTENT_ID_FIELD}) AS events_with_persistentid, ROUND(COUNT({PERSISTENT_ID_FIELD}) / COUNT(*), 2) AS percent_with_persistentid_not_null FROM {DATASET_TABLE_NAME} WHERE TO_TIMESTAMP(timestamp, '{FORMAT_STRING}') >= TIMESTAMP '{START_DATE}' AND TO_TIMESTAMP(timestamp, 'FORMAT_STRING') < TIMESTAMP '{END_DATE}';Where:
{PERSISTENT_ID_FIELD}is the field for the persistent ID. For example:identityMap.ecid[0].{DATASET_TABLE_NAME}is the table name for the event dataset.{FORMAT_STRING}is the format string for the timestamp field. For example:MM/DD/YY HH12:MI AM.{START_DATE}is the start date. For example:2024-01-01 00:00:00.{END_DATE}is the end date in standard format. For example:2024-01-08 00:00:00.
-
Person ID - Query 7 days of data where your person ID field is not null and divide by a query of 7 days of data for all events in your dataset. This percentage should be above 5%.
Example of a query you could use for verification:
code language-sql SELECT COUNT(*) AS total_events, COUNT({PERSON_ID_FIELD}) AS events_with_personid, ROUND(COUNT({PERSON_ID_FIELD}) / COUNT(*), 2) AS percent_with_personid_not_null FROM {DATASET_TABLE_NAME} WHERE TO_TIMESTAMP(timestamp, '{FORMAT_STRING}') >= TIMESTAMP '{START_DATE}' AND TO_TIMESTAMP(timestamp, 'FORMAT_STRING') < TIMESTAMP '{END_DATE}';Where:
{PERSON_ID_FIELD}is the field for the person ID. For example:identityMap.crmId[0].{DATASET_TABLE_NAME}is the table name for the event dataset.{FORMAT_STRING}is the format string for the timestamp field. For example:MM/DD/YY HH12:MI AM.{START_DATE}is the start date. For example:2024-01-01 00:00:00.{END_DATE}is the end date in standard format. For example:2024-01-08 00:00:00.
-
Enable identity stitching
To enable stitching, in the event dataset section of the Add datasets or Edit dataset dialog:
-
Select Enable identity stitching.
If you enable stitching for an existing event dataset, the Change Person ID dialog displays the implications of a change of the person ID due to the use of stitching. Select Continue to continue.
The Enable identity stitching dialog summarizes the consequences of stitching identities. Select Continue to continue.
-
Select a persistent ID from the Persistent ID drop-down menu.
If you select Identity Map for the persistent ID, you have to select a namespace . You have two options:
- Enable Use primary identity namespace to use the primary identity namespace.
- Select a namespace from the Namespace drop-down menu.
-
Select a person ID from the Person ID drop-down menu.
If you select Identity Map for the person ID, you have to select a namespace. You have two options:
- Enable Use primary identity namespace to use the primary identity namespace.
- Select a namespace from the Namespace drop-down menu.
If you select Identity Graph for the person ID (to use graph-based stitching), you have to select a namespace.
note note NOTE Ensure that you are entitled to use the identity graph. Before that, a Change to identity graph dialog is displayed to ensure you have finished the setup of the identity graph for the dataset before you use the identity graph for stitching. Select Continue to continue.
- Select a namespace from the Namespace drop-down menu.
-
Select a lookback window from the Lookback window drop-down menu. The available options are dependent on the Customer Journey Analytics package that you are entitled to.
Once you save a connection that contains datasets that are enabled for identity stitching, the stitching process for each dataset begins when the ingestion of data for that dataset starts.
Limitations
On top of the field-based stitching limitations and graph-based stitching limitations, the following limitations apply when you enable stitching in the Connections interface:
- You can only stitch an event dataset once as part of a single connection. You cannot define the same event dataset more than once and use a separate stitching configuration for each instance. If you want to apply different stitching configurations on the same dataset, use a separate connection for each configuration.