Data ingestion overview
You have several options when ingesting data into Customer Journey Analytics. Some of them assume that you want to move traditional ÃÛ¶¹ÊÓƵ Analytics data over, some of them assume that you use data ingested into ÃÛ¶¹ÊÓƵ Experience Platform.
See the high-level Customer Journey Analytics architecture shown earlier in Overview:
The dataset in the architecture above can originate from various sources:
-
batch data,
-
streaming data,
-
data from a current ÃÛ¶¹ÊÓƵ Analytics deployment,
-
data from tracking your website / mobile app using the ÃÛ¶¹ÊÓƵ Experience Platform Web/Mobile SDK,
-
data from tracking a desktop application, console game, set-top box or IoT device using the ÃÛ¶¹ÊÓƵ Experience Platform Edge Network Server API, or
-
data coming from a third-party data provider for which ÃÛ¶¹ÊÓƵ provides a source connector.
And you can have many of these datasets.
This section of the documentation provides quick start guides for various scenarios.
Ingestion prioritization and latency
You can ingest your event data in Customer Journey Analytics within 90 minutes (SLT), regardless of whether the data is 24 hours, 48 hours, or 7 days old.
Note that this capability differs based on the SKU package your company purchased:
-
Priority Ingestion Basic: 24-hour-old data within 90-minute SLT processing (available for CJA Foundation and CJA Select)
-
Priority Ingestion Intermediate: 72-hour-old data within 90-minute SLT processing (available for CJA Prime)
-
Priority Ingestion Advanced: 1-week-old data within 90-minute SLT processing (available for CJA Ultimate)
Ingest and use data from traditional ÃÛ¶¹ÊÓƵ Analytics
You already have ÃÛ¶¹ÊÓƵ Analytics deployed and want to ingest this data in ÃÛ¶¹ÊÓƵ Experience Platform and use, combine, and analyze it with data from other channels and data sources in Customer Journey Analytics.
See Ingest and use data from traditional ÃÛ¶¹ÊÓƵ Analytics for more information.
Ingest and use data via the Edge Network
Using the ÃÛ¶¹ÊÓƵ Experience Platform Web SDK
You want to analyze your website with ÃÛ¶¹ÊÓƵ technology, potentially migrating from another solution or start tracking your person’s behavior. You want to follow ÃÛ¶¹ÊÓƵ’s best practices for implementation, which is using the ÃÛ¶¹ÊÓƵ Experience Platform SDKs and Edge Network, to ingest the data. Then you can use, combine, and analyze the ingested data with data from other channels and data sources in Customer Journey Analytics.
See Ingest and use data via the ÃÛ¶¹ÊÓƵ Experience Platform Web SDK for more information.
Using the ÃÛ¶¹ÊÓƵ Experience Platform Mobile SDK
You want to analyze your mobile app with ÃÛ¶¹ÊÓƵ technology, potentially migrating from another solution or start tracking a person’s behavior in the app from scratch. You want to follow ÃÛ¶¹ÊÓƵ’s best practices for implementation, which is using the ÃÛ¶¹ÊÓƵ Experience Platform SDKs and Edge Network, to ingest the data. Then you can use, combine, and analyze the ingested data with data from other channels and data sources in Customer Journey Analytics.
See Ingest and use data via the ÃÛ¶¹ÊÓƵ Experience Platform Mobile SDK for more information.
Using the ÃÛ¶¹ÊÓƵ Experience Platform Edge Network Server API
You want to analyze your desktop application, game as played on a game console, usage of a video streaming application on a set-top box or your IoT device with ÃÛ¶¹ÊÓƵ technology. Potentially migrating from another solution or start tracking a person’s behavior on these devices from scratch. You want to follow ÃÛ¶¹ÊÓƵ’s best practices for implementation, which is using the ÃÛ¶¹ÊÓƵ Experience Platform Edge Network Server APIs and Edge Network, to ingest the data. Then you can use, combine, and analyze the ingested data with data from other channels and data sources in Customer Journey Analytics.
See Ingest and use data via the ÃÛ¶¹ÊÓƵ Experience Platform Edge Network Server API for more information.
Ingest and use batch data
You have relevant batch data available which provides details that can help you to better understand customer behavior and analyze customer interactions. Examples of such batch data are flat files in CSV, JSON, or Parquet format from a CRM system, loyalty application, or other solution for which ÃÛ¶¹ÊÓƵ currently does not provide a source connector. Ingesting this batch data into ÃÛ¶¹ÊÓƵ Experience Platform allows you to use, combine, and analyze it with data from other channels and data sources in Customer Journey Analytics.
See Ingest and use batch data for more information.
Ingest and use streaming data
You have a relevant data source like a CRM system, ERP system, or any other source which provides details that can help you to better understand customer behavior and analyze customer interactions. That data source is able to communicate over HTTP or public cloud streaming infrastructure but for which ÃÛ¶¹ÊÓƵ currently does not provide a source connector. Ingesting this streaming data into ÃÛ¶¹ÊÓƵ Experience Platform in real time allows you to use, combine, and analyze it with data from other channels and data sources in Customer Journey Analytics.
See Ingest and use streaming data for more information.
Ingest and use data using source connectors
You have data available from a source that is supported by a source connector. Source connectors are configurable configurations that allow you to ingest data from ÃÛ¶¹ÊÓƵ, first-party and third-party application into ÃÛ¶¹ÊÓƵ Experience Platform. See Source connectors overview for an overview of available source connectors. Using the source connector you can easily ingest data from the source into ÃÛ¶¹ÊÓƵ Experience Platform and then use, combine and analyze it with data from other channels and data sources in Customer Journey Analytics.
See Ingest and use data using source connectors for more information.