This page focuses on how to ingest your Google Analytics historical data into Adobe Experience Platform as a dataset, allowing you to reference that dataset in a Data View within Customer Journey Analytics. You can combine the steps on this page with Configuring a live Google Analytics implementation, which generates a recurring dataset. Combine this historical dataset with your current implementation’s dataset to get a seamless view of data in Customer Journey Analytics with both current and backfilled data.
In order to accomplish these tasks, you need the following access and permissions:
The data structure in Universal Analytics properties is different from the data structure in Google Analytics 4 properties. Set up a BigQuery Export based on the property type that you want to export data from:
This section only applies to Universal Analytics properties. If you are exporting from a GA4 property, you can proceed to Export data to Google Cloud Platform.
Universal Analytics properties store each record in their data as a user’s session instead of individual events. A SQL query to transform the Universal Analytics data into a format compatible with Adobe Experience Platform is required. Apply the
UNNEST function to the
hits field in the GA schema, and save it as a BigQuery table.
timestamp_seconds(`visitStartTime` + hit.time) AS `timestamp`
UNNEST(hits) AS hit
In Google Cloud Platform, navigate to Export > Export to GCS. Once the data is in Google Cloud Storage, it is ready to be pulled into Adobe Experience Platform.
If you plan to import both historical and live streaming Google Analytics data, make sure that you use the same schema for both datasets. You can merge the datasets in a Customer Journey Analytics using a Combined dataset.
You can map the GA event data into an existing dataset that you created previously, or create a dataset, using whichever XDM schema you choose. Once you have selected the schema, the Experience Platform applies machine learning to automatically pre-map each of the fields in the Google Analytics data to your XDM schema.
Once you are finished mapping the fields into your XDM schema, you can schedule this import on a recurring basis and apply error validation during the ingestion process. This validation ensures that there aren’t any issues with the data you have imported.
Certain XDM fields in Platform require the correct format in order for data to be correctly processed.
timestamp: Create a special calculated field in the Experience Platform schema UI. Click Add calculated field and wrap the
timestamp string in a
date(timestamp, "yyyy-MM-dd HH:mm:ssZ")
Save the calculated field to the timestamp data structure in the schema:
_id: This field must have a value in it - Customer Journey Analytics does not care what the value is. You can add a “1” to the field: