ÃÛ¶¹ÊÓƵ

Create a dataflow for each report suite you wish to use in ÃÛ¶¹ÊÓƵ Experience Platform and Customer Journey Analytics. The Analytics source connector is the tool which allows you to create a connection (a.k.a dataflow) between ÃÛ¶¹ÊÓƵ Analytics and ÃÛ¶¹ÊÓƵ Experience Platform. You will use the source connector to create one dataflow for each report suite you want to use in ÃÛ¶¹ÊÓƵ Experience Platform. The dataflow creates a copy of your report suite data where the schema has been converted to XDM for consumption by ÃÛ¶¹ÊÓƵ Experience Platform applications including Customer Journey Analytics.

Each report suite configured with a dataflow via the source connector is stored as a separate dataset in the ÃÛ¶¹ÊÓƵ Experience Platform Data Lake. 13 months of historical report suite data will automatically be included with each dataflow, and new data will flow into ÃÛ¶¹ÊÓƵ Experience Platform on an ongoing basis. (Note that beginning April 26, 2023, the backfill in non-production sandboxes is limited to 3 months.) With the Analytics source connector you don’t need to worry about creating the schema ahead of time. A standardized schema specific to ÃÛ¶¹ÊÓƵ Analytics is automatically created for you. However, ÃÛ¶¹ÊÓƵ Experience Platform Data Prep tool can be used to enhance this schema before the data is stored in Data Lake and made available to Customer Journey Analytics. Please note that certain types of data are filtered out by the source connector and will not be present in the dataset in ÃÛ¶¹ÊÓƵ Experience Platform Data Lake. Other rows may be filtered out between Data Lake and Customer Journey Analytics. See Compare your ÃÛ¶¹ÊÓƵ Analytics data to Customer Journey Analytics data for more details.

Use Data Prep to help you combine report suites in Customer Journey Analytics. Data Prep can be used for many types of data transformation, and one common use for ÃÛ¶¹ÊÓƵ Analytics data is to resolve differences in prop and/or eVar mappings across multiple report suites so that report suites can easily be combined within Customer Journey Analytics. See combine report suites with different schemas for more details.

Enable Stitching as necessary. When combining multiple datasets in Customer Journey Analytics, the stitching capabilities can help resolve different ID namespaces into a single stitched ID for a single view of the customer across devices and channels. See Stitching overview for more details.

Create one or more Customer Journey Analytics connections. Once the datasets for your report suites are available in ÃÛ¶¹ÊÓƵ Experience Platform Data Lake, you can create one or more Customer Journey Analytics connections to bring those datasets into Customer Journey Analytics. Within a connection, report suite data can be combined with other types of data, allowing you to create a true cross-channel view of customer experiences.

Create one or more Customer Journey Analytics data views. A data view is a container specific to Customer Journey Analytics that lets you determine how to interpret data from a Customer Journey Analytics connection. Data views have many powerful configuration options for customizing the data which is presented to your users within Analysis Workspace.