---
title: "Get automation journey metrics"
method: GET
path: "/v1/campaigns/{campaign_id}/journey_metrics"
tags: ["Automations"]
---

# Get automation journey metrics

`GET /v1/campaigns/{campaign_id}/journey_metrics`

## Request

- Base URL: `https://api.customer.io`
- URL: `https://api.customer.io/v1/campaigns/{campaign_id}/journey_metrics`
- Auth: HTTP bearer

Returns a list of Journey Metrics for your automation. These metrics show how many people triggered your automation, were messaged, etc for the time period and "resolution" you set. You must provide the `start`, `end`, and `resolution` parameters or your request will return `400`.

Metrics in the response are arrays, and each index in the array corresponds to the `resolution` in your request. If you request metrics in `days`, the first result in each metric array is the first day of results and each successive increment represents another day.

Each increment represents the number of journeys that started within a time period and eventually achieved a particular metric. For example, array index 0 for the `converted` metric represents the number of journeys that started on the first day/month of results that achieved a conversion.

## Response `200`

Each `journey_metric` item in the response is an array. Each item in a metric array represents the number of journeys that started within the time increment ("resolution"—day or month) and eventually achieved that metric.

- object
  - `journey_metric` object
    - `started` integer[]: The total number of people who meet the trigger criteria for a journey. This count occurs before filters are applied.
    - `activated` integer[]: People who started a journey and were not filtered out before they experienced an action.
    - `exited_early` integer[]: People who started a journey but stopped meeting the automation trigger/filter criteria.
    - `finished` integer[]: People who finished the journey.
    - `converted` integer[]: People who matched the conversion criteria for the automation.
    - `never_activated` integer[]: People who started a journey but were filtered out before they could experience any of the actions in the journey.
    - `messaged` integer[]: People who experienced at least one non-delay action in the journey. This metric typically represents journeys in progress.

## Other responses

- `400`: You may have omitted query parameters or the `start` time occurred after the `end` time. The `campaignID` or `actionID` may also be invalid.
- `404`: The automation and/or action do not exist.
- `429`: Your request is over the 10-per-second limit. `Retry-After` tells you how many seconds you must wait before you send the next request.

## Changes

- **2026-09-02** `5da2740beeb5`: 1 info
  - added the media type `application/json` for the response with the status `429`

[Operation history](https://skmtc.dev/customer/apis/customer-io-journeys-api-reference/changes/v1/campaigns/:campaign_id/journey_metrics/get.md)

---

[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.dev/customer/apis/customer-io-journeys-api-reference/revisions/ac0b282053fe?raw)