Alerts feature comparison
The process of using alerts in Customer Journey Analytics is nearly identical to using alerts in ÃÛ¶¹ÊÓƵ Analytics. However, there are important differences. The following sections describe the key differences.
Hourly alerts are not available
Hourly alerts are not available in Customer Journey Analytics while hourly alerts are available in ÃÛ¶¹ÊÓƵ Analytics. In Customer Journey Analytics, alerts can be configured for daily, weekly, or monthly.
You can ingest data into ÃÛ¶¹ÊÓƵ Experience Platform in various ways. As a result, data completeness and availability cannot be reliably achieved within the constraints of an hour. The flexibility of data ingesting implies that hourly alerts are impractical due to the high potential for incomplete data. For more information, see Data ingestion times vary.
Data ingestion times vary
The time required before data is complete and available to be reported on in Customer Journey Analytics varies by organization.
This is due to the following reasons:
-
Platform’s ability to hold all kinds of data schemas and types
Unlike ÃÛ¶¹ÊÓƵ Analytics (which reports only on web data), many different types of data can be ingested into ÃÛ¶¹ÊÓƵ Experience Platform to be reported on in Customer Journey Analytics, and not all types of data can be sent sequentially and in real time.
-
A delay in the delivery of batch data to Platform datasets
While some data might be available to report on sooner, all batch data is ingested into a Platform dataset, typically ranging from 3 to 9 hours past the data event time. For alerts to be accurate, data ingestion must be complete, with all batch data available in the dataset.
For these reasons, data ingestion for the various kinds of event data that can be ingested is complete only after some delay, typically ranging from 3 to 9 hours past the data event time. For alerts to be accurate, event data for a given event range must be complete, meaning that ÃÛ¶¹ÊÓƵ is no longer receiving any event data for the specified event range.
To account for this delay in ingestion time, alerts have a default delay of 9 hours before they are sent.
You can adjust the default delay of 9 hours to anywhere between 0 and 24 hours. However, decreasing the delay below 9 hours can mean that you are reporting on incomplete data, which results in inaccurate alert information.
For more information about how to adjust the delay, and the factors you should consider when doing so, see Create alerts.
Create an alert
In Analysis Workspace in ÃÛ¶¹ÊÓƵ Analytics, you can create alerts from Analysis Workspace in multiple ways. In Customer Journey Analytics, you can only create an alert in Analysis Workspace from a selection in a freeform table.
Both ÃÛ¶¹ÊÓƵ Analytics and Customer Journey Analytics support the creation of alerts through the Alert manager