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

# Report push metrics

`POST /api/v1/push/events`

> **Deprecated.**

While this endpoint still works, you should take advantage of our [universal metrics endpoint](/integrations/api/track/tag/track-events/metrics/). It supports channels besides push and lets you provide additional information with some metrics.

Use this endpoint to report device-side push metrics—opened, converted, and delivered—back to Customer.io, so you can track the effectiveness of your push notifications. Customer.io has no way of knowing about these metrics, or associating metrics with a specific message, unless you report them back to us.

When Customer.io delivers a push notification, we include `CIO-Delivery-ID` and `CIO-Delivery-Token` parameters. Reference these in your payload as the `delivery_id` and `device_id` respectively with the type of device-side `event` metric that you want to associate with your push notification and the person represented by the `device_id`.

## Request body

- object
  - `delivery_id` string — The CIO-Delivery-ID from the notification that you want to associate the `event` with.
  - `event` 'opened' | 'converted' | 'delivered' — The type of device-side event you want to report back to Customer.io.
  - `device_id` string — The CIO-Delivery-Token representing the device that received the original notification.
  - `timestamp` integer — The unix timestamp when the event occurred.

## 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)