Create the Analytics source connector and map fields
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 a custom schema to use with your Customer Journey Analytics Web SDK implementation, 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:
-
If you don’t already have an Analytics source connector, create the Analytics source connector and map fields to your custom Web SDK schema, as described below.
Or
If you already have an Analytics source connector, map fields from the source connector to your custom Web SDK schema.
-
Add the Analytics source connector dataset to the connection
Create the Analytics source connector and map fields
With your custom schema created, you need to create the ÃÛ¶¹ÊÓƵ Analytics source connector to use for historical data. (For more comprehensive, general guidelines on creating a source connector, see Create an ÃÛ¶¹ÊÓƵ Analytics source connection in the UI.)
To create an ÃÛ¶¹ÊÓƵ Analytics source connector to use for historical data:
-
In the Platform UI, In the Connections section in the left rail, select Sources.
-
Select ÃÛ¶¹ÊÓƵ applications from the list of CATEGORIES.
-
Select Add data in the ÃÛ¶¹ÊÓƵ Analytics tile.
-
Select Report suite, then from the list of report suites, select the report suite that contains the historical data that you want to use in Customer Journey Analytics.
-
Select Next in the upper-right corner of the screen.
-
Select Custom schema, then select the schema that you created in Create a custom schema that includes the ÃÛ¶¹ÊÓƵ Analytics field group.
-
Map each ÃÛ¶¹ÊÓƵ Analytics dimension to a custom schema dimension.
-
In the Map standard fields section, select the Custom tab.
-
Select Add new mapping.
-
In the Source field, select an ÃÛ¶¹ÊÓƵ Analytics field from the ÃÛ¶¹ÊÓƵ Analytics ExperienceEvent Template field group. Then, in the Target field, select the custom field in the XDM schema that you want to map it to.
Not all ÃÛ¶¹ÊÓƵ Analytics fields have a corresponding field in XDM due to the inherent architecture differences between AppMeasurement and XDM.
-
Repeat this process for each field in the ÃÛ¶¹ÊÓƵ Analytics ExperienceEvent Template field group that you are using to collect data in ÃÛ¶¹ÊÓƵ Analytics.
-
-
Select Next in the upper-right corner of the screen.
-
Name the data flow and (optionally) provide a description.
-
Select Next in the upper-right corner of the screen.
-
Review the connection, then select Finish.
After the connection is created, the dataflow is automatically created to populate a dataset with the ÃÛ¶¹ÊÓƵ Analytics data from your report suite. The dataflow ingests up to 13 months of historical data for production sandboxes. The backfill in non-production sandboxes is limited to three months.
If you are using the Analytics source connector to bring historical data into your Customer Journey Analytics Web SDK implementation, then you need to add this automatically created dataset to the connection that you created for your Web SDK implementation.
-
Continue following the recommended upgrade steps or the .