---
title: "Personalization fallback usage for one automation"
method: GET
path: "/personalization/automations/{automation_id}/fallback-stats"
tags: ["Personalization"]
---

# Personalization fallback usage for one automation

`GET /personalization/automations/{automation_id}/fallback-stats`

How many of an automation's personalized outreach messages used the brand fallback (creator had too little signal to personalize) versus were fully personalized. A lifetime aggregate across every send run of the automation, plus the `fallback_rate` convenience ratio. Counts are recorded when the send engine locks the copy for delivery (immediately before the DM goes out), so a delivery that fails at the last step may still be counted. An automation with no personalized sends yet returns zeros; an automation not in this shop returns 404. Requires a single shop.

## Path parameters

- `automation_id` integer, required

## Response `200`

Successful Response

- PersonalizationFallbackStatsResponse — Send-report stat: how often an automation's personalized sends fell back.
  - `automation_id` integer, required
  - `messages_sent` integer, required — Personalized outreach messages this automation has sent (lifetime, all runs).
  - `fallback_used` integer, required — How many of those used the brand fallback (creator had too little signal).
  - `fallback_rate` number, required — fallback_used / messages_sent (0.0 when nothing has been sent).

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/reacherapp/apis/reacher-data-api.md) · [All operations](https://skmtc.dev/reacherapp/apis/reacher-data-api/llms.txt) · [OpenAPI document](https://skmtc.dev/reacherapp/apis/reacher-data-api/revisions/881910053958?raw)