Monitor custom channels monitor-custom-channel

On this page: Learn how to manage the lifecycle of your custom channels and monitor delivery performance through Adobe Journey Optimizer’s out-of-the-box reporting, including metrics such as successful deliveries, errors, and link clicks.

Once a custom channel is created and activated, you can manage its lifecycle and monitor delivery performance through the Journey Optimizer interface.

Leverage campaign and journey reports reporting

Journey Optimizer provides out-of-the-box reporting for custom channels.

The Custom channel campaign report is detailed in this section.

The following metrics are available for custom channels in both live (24h) and global (CJA) reports.

Metric
Description
Attempted deliveries
Total number of messages sent to the external endpoint.
Successful deliveries
Messages for which the endpoint returned an HTTP 2xx response.
Profiles targeted
Number of unique profiles reached.
Clicks
Number of link clicks tracked in the payload. Requires a subdomain delegated for custom channels.
Errors / Failures
Number of failed delivery attempts, with breakdown by error reason.

Learn more about live reports and global reports. For details on reporting functionalities, refer to this documentation.

Monitor delivery performance monitoring

In addition to campaign and journey reports, Journey Optimizer provides a dedicated custom channel monitoring dashboard. Access it from Administration > Channels > Channel Builder > Custom channels monitoring.

Custom channel monitoring dashboard {width="100%"}

This dashboard lets you monitor the reliability and performance of the API calls Journey Optimizer makes to your external endpoints when delivering custom channel messages. Use it to quickly spot integration issues, latency, and throttling limits.

The Custom channels monitoring dashboard functions like other all-time reports in Journey Optimizer. You can select a time range, filter by channel or endpoint, and drill down to see the campaigns and journeys that rely on each custom channel. Learn more

Custom channel metrics monitoring-kpis

The Custom channel metrics section provides a consolidated view of the operational health and reliability of your custom channel calls.

Custom channel metrics {width="100%"}

Learn more about custom channel metrics
  • Successful calls: Total number of HTTP calls that returned a valid response without error.

  • 4xx/5xx errors: Number of failed calls due to client-side (4xx) or server-side (5xx) 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. There are three categories:

    table 0-row-2 1-row-2 2-row-2 3-row-2
    Category Description
    Authentication failures (AUTH_*) Journey Optimizer could not obtain or refresh the OAuth token or credentials needed to call the endpoint. Check that the API credentials linked to the channel configuration are valid and have not expired.
    Request generation errors (REQUEST_GENERATION_ERROR) Journey Optimizer could not construct a valid HTTP request — for example, because a URL template could not be resolved or a required personalization field was missing.
    HTTP parse errors (HTTP_PARSE_ERROR) Journey Optimizer received a response from the endpoint but could not parse it into a usable structure.
    note tip
    TIP
    Pre-call failures indicate a problem on the Journey Optimizer side or in the channel configuration, rather than an issue with your external endpoint. Start troubleshooting by reviewing your API credentials and required payload fields.
  • Average latency: Average end-to-end response time (in milliseconds) for all HTTP calls, including successful calls, errors, and timeouts.

Custom channels outcomes over time outcomes-overtime

Custom channel outcomes over time {width="100%"}

The Custom channels outcomes over time graph shows the HTTP call KPI trend over the selected time period. The granularity of the time series depends on the selected time range:

  • For a 7-day report, each data point shows the KPIs for one day.
  • For a 1-day time range, the graph shows the KPIs per hour.
  • For a 1-hour time range, the graph shows the KPIs per minute.

Latency over time latency-overtime

Custom channel latency over time {width="100%"}

The Latency over time graph visualizes the trend of latency metrics over the selected time period. This time-series view allows you to track performance patterns, identify peak latency periods, and monitor the impact of optimizations or system changes over time.

Custom channel outcome breakdown outcome-breakdown

Custom channel outcome breakdown {width="100%"}

The Custom channel outcome breakdown table provides a hierarchical breakdown of 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.

Latency breakdown latency-breakdown

The Latency breakdown table provides a detailed breakdown of latency metrics across your custom channels. This view helps you identify which specific endpoints or channels are experiencing performance issues, enabling you to pinpoint and address latency bottlenecks effectively.

Insight Builder insight-builder

Use the Insight Builder to create custom visualizations and dashboards based on the custom channel metrics. This tool allows you to combine multiple KPIs, apply filters, and create tailored views that align with your monitoring and reporting needs. Learn more

Troubleshooting troubleshooting

If you encounter issues with your custom channel, the following table lists common symptoms, possible causes, and recommended resolutions.

Symptom
Possible cause
Resolution
HTTP 401 / 403 errors
Authentication failure — credentials expired or incorrect.
Update the credentials in Administration > Channels > API credentials.
HTTP 429 errors
External endpoint is throttling requests from Journey Optimizer.
Review your endpoint’s rate limits. Reduce the throttling setting in the Channel Builder policy configuration.
HTTP 5xx errors
External system is down or returning server errors.
Check your external system’s health dashboard. Configure error paths on the journey action activity to handle transient failures gracefully.
Unresolved personalization tokens
Expression references an attribute not present on the profile.
Verify the XDM attribute path is correct. Add a default value fallback: {{profile.person.name.firstName | default("Valued Customer")}}.
Required field validation error
A required payload field has no value at authoring time.
Ensure all required fields are populated in the content editor. Alternatively, remove the required constraint in the Channel Builder if the field is truly optional.
recommendation-more-help
journey-optimizer-help