---
title: "Report metrics"
method: POST
path: "/api/v1/metrics"
tags: ["Track Events"]
---

# Report metrics

`POST /api/v1/metrics`

This endpoint helps you report metrics from channels that aren't native to Customer.io or don't rely on our SDKs. When we deliver a message, we include a CIO-Delivery-ID header. This is the `delivery_id` in the payload. You can use it as a UTL and you can pass it as a UTM parameter in links, etc to track metrics when people click, convert, etc.

## Request body

- union
  - object — The base properties shared across multiple metric types.
    - `delivery_id` string, required — The CIO-Delivery-ID from the notification that you want to associate the `event` with.
    - `timestamp` integer — The unix timestamp when the event occurred.
    - `metric` 'bounced' | 'clicked' | 'converted' | 'deferred' | 'delivered' | 'dropped' | 'opened' | 'spammed', required — The email metric you want to report back to Customer.io.
    - `recipient` string — The email of the person who received the message.
    - `reason` string — For metrics indicating a failure (like `bounced`), this field provides the reason for the failure.
    - `href` string — For `clicked` metrics, this is the link the recipient clicked.
  - object — The base properties shared across multiple metric types.
    - `delivery_id` string, required — The CIO-Delivery-ID from the notification that you want to associate the `event` with.
    - `timestamp` integer — The unix timestamp when the event occurred.
    - `metric` 'clicked' | 'converted' | 'opened', required — The type of device-side event you want to report back to Customer.io.
    - `recipient` string — The email address or ID of the recipient (depending on the value you use to target in-app messages).
    - `href` string — For `clicked` metrics, this is the link the recipient clicked.
  - object — The base properties shared across multiple metric types.
    - `delivery_id` string, required — The CIO-Delivery-ID from the notification that you want to associate the `event` with.
    - `timestamp` integer — The unix timestamp when the event occurred.
    - `metric` 'converted' | 'delivered' | 'opened', required — The type of device-side event you want to report back to Customer.io.
    - `recipient` string — The device ID that the message was sent to.
  - object — The base properties shared across multiple metric types.
    - `delivery_id` string, required — The CIO-Delivery-ID from the notification that you want to associate the `event` with.
    - `timestamp` integer — The unix timestamp when the event occurred.
    - `metric` 'clicked' | 'converted' | 'delivered' | 'opened', required — The metric you want to report back to Customer.io.
    - `href` string — For `clicked` metrics, this is the link the recipient clicked.
  - object — The base properties shared across multiple metric types.
    - `delivery_id` string, required — The CIO-Delivery-ID from the notification that you want to associate the `event` with.
    - `timestamp` integer — The unix timestamp when the event occurred.
    - `metric` 'bounced' | 'clicked' | 'delivered' | 'opened', required — The SMS metric you want to report back to Customer.io.
    - `recipient` integer — The phone number of the person who received the message.
    - `reason` string — For metrics indicating a failure (like `bounced`), this field provides the reason for the failure.
    - `href` string — For `clicked` metrics, this is the link the recipient clicked.
  - object — The base properties shared across multiple metric types.
    - `delivery_id` string, required — The CIO-Delivery-ID from the notification that you want to associate the `event` with.
    - `timestamp` integer — The unix timestamp when the event occurred.
    - `metric` 'bounced' | 'clicked' | 'converted' | 'deferred' | 'delivered' | 'dropped' | 'opened' | 'spammed', required — The type of device-side event you want to report back to Customer.io.
    - `reason` string — For metrics indicating a failure (like `bounced`), this field provides the reason for the failure.
    - `href` string — For `clicked` metrics, this is the link the recipient clicked.

## Response `200`

The request was received.

---

[API](https://skmtc.dev/customer/apis/customer-io-journeys-api-reference.md) · [All operations](https://skmtc.dev/customer/apis/customer-io-journeys-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/customer/customer-io-journeys-api-reference/revisions/4b391af7cb06/schema)