ÃÛ¶¹ÊÓƵ

DocumentationCustomer Journey AnalyticsCustomer Journey Analytics Guide

Add the Analytics source connector dataset to the connection

Last update: Thu Nov 21 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Admin
NOTE
Follow the steps on this page only after you complete all previous upgrade steps. You can follow the recommended upgrade steps, or you can follow the upgrade steps that were dynamically generated for your organization with the .
After you complete the steps on this page, continue following the recommended upgrade steps or the dynamically generated upgrade steps.

Understand how the Analytics source connector can bring historical data into Customer Journey Analytics

You can use the Analytics source connector to bring ÃÛ¶¹ÊÓƵ Analytics report suite data into ÃÛ¶¹ÊÓƵ Experience Platform. This data can then be used as historical data in Customer Journey Analytics.

This process assumes that you want to create an XDM schema when upgrading to Customer Journey Analytics, because you want a streamlined schema that is tailored to the needs of your organization and the specific Platform applications that you use.

To use the Analytics source connector to bring historical data into Customer Journey Analytics, you need to:

  1. Create an XDM schema for the Analytics source connector

  2. If you don’t already have an Analytics source connector, create the Analytics source connector and map fields to your XDM schema.

    Or

    If you already have an Analytics source connector, map fields from the source connector to your XDM schema.

  3. Add the Analytics source connector dataset to the connection, as described below.

Add the Analytics source connector dataset to the connection

After you create an Analytics source connector for historical data, a dataset is automatically created for the Analytics data.

You need to add this automatically created dataset to the same connection that you created for your Web SDK implementation. Doing so brings the Analytics data into the same data view in Customer Journey Analytics as your Web SDK data.

To add the automatically created dataset to the same connection that you created for your Web SDK implementation:

  1. In Customer Journey Analytics, select the Connections tab.

  2. Select the connection that you created for your Web SDK implementation.

  3. Select Edit.

    Edit connection

  4. Select Add datasets in the upper-right.

    Edit connection

  5. Scroll to or search for the dataset that was automatically created when you created the Analytics source connector.

    The name of this dataset is the name of your report suite, followed by midValues. For example: My report suite midValues

  6. Select the checkbox next to the dataset name, then select Next.

    Edit connection

  7. Specify the following information:

    table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 layout-auto
    Setting Description
    Person ID

    Only available for event and profile datasets. Select a Person ID from the drop-down 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. See Define identity fields in the UI for more information.

    The value for the selected Person ID is considered to be case sensitive. For example, abc123 and ABC123 are two different values.
    Timestamp For event and summary datasets only, this setting is automatically set to the default timestamp field from event-based schemas in Experience Platform.
    Timezone Only available for summary data. Select the appropriate timezone for the time-series summary data.
    Data source type

    Select a type of data source.
    Types of data sources include:

    • Web data
    • Mobile App data
    • POS data
    • CRM data
    • Survey data
    • Call Center data
    • Product data
    • Accounts data
    • Transaction data
    • Customer Feedback data
    • Other

    This field is used to survey the types of data sources in use.

  8. In the Import new data section, leave the Import all new data option disabled.

    Because you are using the Analytics source connector dataset for historical data, you don’t want to bring over future data that is collected into this dataset.

  9. In the Dataset backfill section, select Request backfill.

  10. Define the period that you want the connection backfill into Customer Journey Analytics to include by entering the start and end dates or by selecting the the calendar icon Calendar .

    Be explicit when specifying the dates you request for backfill. Depending on several factors, you might want to do any of the following:

    • Choose an end date that is the same date as when you first started gathering data with your Web SDK implementation.

    • Choose an end date that is shortly after the date when you first started gathering data with your Web SDK implementation, then use data view segments to filter out the overlapping data.

    • Choose an end date that results in a greater overlap in data, then use data view segments to filter out the overlapping data.

      Note: This option would result in increased costs because there would be more rows in the connection.

  11. Select Queue backfill.

  12. Select Add datasets, then select Save to save the connection.

  13. (Conditional) If you are using lookup datasets, you must create the lookup dataset and add it to your connection. For more information, see Create lookup datasets to classify data in Customer Journey Analytics.

    This is required only if you did not already do it when configuring your Web SDK implementation.

  14. Continue following the recommended upgrade steps or the .

recommendation-more-help
080e5213-7aa2-40d6-9dba-18945e892f79