Documentation

Enable identity stitching in Customer Journey Analytics connections (self‑serve)

Last update: Fri Mar 06 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

If you want to enable identity stitching for a dataset in Customer Journey Analytics and previously requested a stitched dataset through Adobe Support, use the Connections UI instead; enable identity stitching on the event dataset in your CJA connection, because Adobe no longer creates separate stitched datasets in Experience Platform on request.

Description description

Environment

  • Product: Customer Journey Analytics

  • Versions: Not version-specific

  • Constraints:

    • Legacy AEP-side stitched datasets created by Adobe Engineering on request are deprecated.
    • You must configure identity stitching directly in Customer Journey Analytics connections.

Issue/Symptoms

  • You want to enable identity stitching (field-based or graph-based) on an event dataset within a Customer Journey Analytics connection.
  • You previously used, or expected to use, a duplicated stitched dataset in Adobe Experience Platform created via a support request.
  • You need to understand the new self-serve stitching process in the Connections UI and its impact on existing stitched datasets.

Resolution resolution

Use the self-serve identity stitching feature in the Customer Journey Analytics Connections interface to enable stitching on your event datasets. The detailed fields and configuration options for identity stitching are documented in Enable stitching.

  • Use the Connections UI as the only supported method.

    • Follow the Enable stitching documentation to configure identity stitching (field-based or graph-based) on your event datasets within a connection.
    • Do not open new tickets requesting Adobe Engineering to create duplicated stitched datasets in Adobe Experience Platform.

  • Be aware of process changes and deprecation.

    • The legacy request-based workflow described in Request stitching is deprecated in favor of the Connections UI.
    • Any stitched datasets that were created through the legacy process will be migrated to the new model and then removed.
    • Identity stitching is intended for use within Customer Journey Analytics only, so duplicated stitched datasets in Adobe Experience Platform are no longer a supported pattern.

  • Understand benefits of the new self-serve process.

    • Faster turnaround: You can configure stitching immediately in the UI. Backfill typically completes within several hours (for example, 8–12 hours depending on volume), instead of waiting days for an engineering request.
    • Less maintenance: You no longer maintain duplicated datasets and schemas. When you enable stitching within the connection, you avoid manually keeping a stitched schema in sync with the source schema.
    • More control: You can adjust stitching configuration (for example, lookback window and replay frequency) directly in the UI, without involving Adobe Engineering.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f