カスタムチャネルの監視 monitor-custom-channel

カスタムチャネル指標の詳細

• 成功した呼び出し：エラーなしで有効な応答を返した HTTP 呼び出しの合計数。

• 4xx／5xxエラー：クライアントサイド（4xx）またはサーバーサイド（5xx）のエラーにより失敗した呼び出しの数。設定の問題またはエンドポイントのエラーがハイライト表示されます。

• タイムアウト呼び出し：最大応答時間を超えたために失敗した呼び出しの数。 これは、外部エンドポイントの待ち時間やパフォーマンスの問題を明らかにするのに役立ちます。

• 事前呼び出しエラー:HTTP呼び出しが外部エンドポイントに行われるまでに失敗したカスタムチャネル送信の数。 これらのエラーは、外部システムではなく、Journey Optimizer独自のインフラストラクチャ層で発生します。 3つのカテゴリがあります。

  table 0-row-2 1-row-2 2-row-2 3-row-2
  カテゴリ	説明
  認証エラー （AUTH_*）	Journey Optimizerは、エンドポイントの呼び出しに必要なOAuth トークンまたは資格情報を取得または更新できませんでした。 チャネル設定にリンクされているAPI資格情報が有効で、有効期限が切れていないことを確認します。
  リクエスト生成エラー （REQUEST_GENERATION_ERROR）	Journey Optimizerは、有効なHTTP リクエストを作成できませんでした。例えば、URL テンプレートを解決できなかったか、必須のパーソナライゼーションフィールドが見つからなかったなどです。
  HTTP解析エラー （HTTP_PARSE_ERROR）	Journey Optimizerはエンドポイントから応答を受け取りましたが、それを使用可能な構造に解析できませんでした。

  note tip
  TIP
  事前呼び出しエラーは、外部エンドポイントの問題ではなく、Journey Optimizer側またはチャネル設定の問題を示します。 API資格情報と必須ペイロードフィールドを確認して、トラブルシューティングを開始します。

• 平均待ち時間：成功した呼び出し、エラー、タイムアウトを含む、すべての HTTP 呼び出しの平均エンドツーエンド応答時間（ミリ秒単位）。

AI Knowledge Reference

This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.

For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.

• TL;DR: This page explains how to monitor custom channel delivery performance in Journey Optimizer using out-of-the-box campaign and journey reports and the dedicated custom channel monitoring dashboard, and how to troubleshoot common delivery issues.

Intents:

• Monitor custom channel delivery performance through out-of-the-box campaign and journey reports
• Access and use the custom channel monitoring dashboard
• Interpret custom channel metrics such as successful calls, errors, timeouts, and pre-call failures
• Analyze outcomes and latency over time and break them down by endpoint, channel, campaign, and journey
• Troubleshoot common custom channel delivery symptoms and apply recommended resolutions

Glossary:

• Custom channels monitoring dashboard: A dedicated dashboard accessed from Administration > Channels > Channel Builder > Custom channels monitoring that monitors the reliability and performance of the API calls Journey Optimizer makes to external endpoints (product-specific)
• Pre-call failures: Custom channel sends that failed before the HTTP call was ever made to the external endpoint; these occur in Journey Optimizer’s own infrastructure layer and fall into three categories: authentication failures (AUTH_*), request generation errors (REQUEST_GENERATION_ERROR), and HTTP parse errors (HTTP_PARSE_ERROR) (product-specific)
• Timeout calls: Number of calls that failed because they exceeded the maximum response time (product-specific)
• Insight Builder: A tool used to create custom visualizations and dashboards based on custom channel metrics (product-specific)
• Successful deliveries: Messages for which the endpoint returned an HTTP 2xx response (product-specific)

Guardrails:

• Clicks metric tracking requires a subdomain delegated for custom channels.
• 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 API credentials and required payload fields.
• Average latency is the average end-to-end response time in milliseconds for all HTTP calls, including successful calls, errors, and timeouts.
• Report granularity depends on the selected time range: a 7-day report shows KPIs per day, a 1-day range shows KPIs per hour, and a 1-hour range shows KPIs per minute.
• HTTP 401/403 errors indicate an authentication failure; update the credentials in Administration > Channels > API credentials.
• HTTP 429 errors indicate the external endpoint is throttling requests; review your endpoint’s rate limits and reduce the throttling setting in the Channel Builder policy configuration.

Terminology:

• Canonical name: Custom channels monitoring dashboard — Acronym: n/a — variants: custom channel monitoring dashboard, Custom channel metrics
• Synonyms: “Attempted deliveries” = total number of messages sent to the external endpoint
• Do not confuse: “Successful deliveries” (report metric: messages for which the endpoint returned an HTTP 2xx response) ≠ “Successful calls” (monitoring metric: total HTTP calls that returned a valid response without error)
• Do not confuse: “4xx/5xx errors” (failed calls due to client-side or server-side errors) ≠ “Timeout calls” (calls that exceeded the maximum response time) ≠ “Pre-call failures” (sends that failed before the HTTP call was made)

FAQ:

• Q: Where can I monitor custom channel performance? — Through out-of-the-box campaign and journey reports and the dedicated custom channel monitoring dashboard, accessed from Administration > Channels > Channel Builder > Custom channels monitoring.
• Q: What does the Clicks metric require? — The Clicks metric counts link clicks tracked in the payload and requires a subdomain delegated for custom channels.
• Q: What are pre-call failures? — Custom channel sends that failed before the HTTP call was ever made to the external endpoint; they occur in Journey Optimizer’s own infrastructure layer and include authentication failures, request generation errors, and HTTP parse errors.
• Q: My calls return HTTP 429 errors. What should I do? — The external endpoint is throttling requests from Journey Optimizer; review your endpoint’s rate limits and reduce the throttling setting in the Channel Builder policy configuration.
• Q: How does the report time granularity change with the time range? — A 7-day report shows one data point per day, a 1-day range shows KPIs per hour, and a 1-hour range shows KPIs per minute.
• Q: How do I troubleshoot unresolved personalization tokens? — Verify the XDM attribute path is correct and add a default value fallback, for example {{profile.person.name.firstName \| default("Valued Customer")}}.