On this page: Learn how to read the Custom channel campaign report in Adobe Journey Optimizer to review KPIs, outcomes, latency, and outcome breakdown for your custom channel calls.
You can access your Custom channel campaign report by clicking the Reports button from your campaign, then selecting View all time report. Learn more
KPIs kpis-custom
The KPIs section provides a consolidated view of the operational health and reliability of your custom channel calls.
-
Successful calls: Total number of HTTP calls that returned a valid response without error.
-
4xx errors: Number of failed calls due to client-side errors, highlighting configuration issues or endpoint failures.
-
5xx errors: Number of failed calls due to server-side errors, highlighting configuration issues or endpoint failures.
-
Timeout calls: Number of calls that failed because they exceeded the maximum response time. This helps surface latency or performance issues with external endpoints.
-
Pre-call failures: Number of custom channel sends that failed before the HTTP call was ever made to the external endpoint. These failures occur in Journey Optimizer’s own infrastructure layer, not in your external system, and include authentication failures, request generation errors, and HTTP parse errors.
-
Average latency: Average end-to-end response time (in milliseconds) for all HTTP calls, including successful calls, errors, and timeouts.
Custom channel outcomes outcomes-custom
The Outcomes graph shows the HTTP call KPI trend over the selected time period, with a granularity that depends on the selected time range (per day for a 7-day report, per hour for a 1-day time range, or per minute for a 1-hour time range), while the Outcome breakdown table provides a hierarchical breakdown of these HTTP call metrics, from overall metrics per endpoint at the top level, to metrics per custom channel using that endpoint, down to the campaigns and journeys that rely on them at the bottom level.
-
Custom channel successful: Total number of HTTP calls that returned a valid response without error.
-
4xx errors: Number of failed calls due to client-side errors, highlighting configuration issues or endpoint failures.
-
5xx errors: Number of failed calls due to server-side errors, highlighting configuration issues or endpoint failures.
-
Timeout calls: Number of calls that failed because they exceeded the maximum response time. This helps surface latency or performance issues with external endpoints.
-
Pre-call failures: Number of custom channel sends that failed before the HTTP call was ever made to the external endpoint. These failures occur in Journey Optimizer’s own infrastructure layer, not in your external system, and include authentication failures, request generation errors, and HTTP parse errors.
-
Calls: Total number of HTTP calls, including successful calls, errors, and timeouts.
Latency latency-custom
The Latency graph and tables visualize the trend of latency metrics. These views allow you to track performance patterns, identify peak latency periods, and monitor the impact of optimizations or system changes over time.
-
Average latency: Average end-to-end response time (in milliseconds) for all HTTP calls, including successful calls, errors, and timeouts.
-
Average successful latency: Average end-to-end response time (in milliseconds) for HTTP calls that returned a valid response without error.