Automation analytics

This page measures your flows. It answers "did the automation work?", not "did the post do well".

The other measurement (how your content performed) lives at Performance. Two different questions, two different screens, two different names, deliberately.

What it shows

The funnel from trigger to outcome: how many times an automation fired, how many messages were actually sent, how many were blocked before sending, and how many people opted out.

Blocked is the number to read

A high blocked count is not a bug: it is the compliance layer doing its job. The usual causes are the messaging window having closed, or the person never having contacted you in a way that permits a reply.

If blocks dominate, the fix is usually upstream: the automation is firing on the wrong trigger, or it is reaching people whose conversation has gone cold. See staying inside platform rules.

Opt-outs are the number to respect

An opt-out is someone telling you to stop. Rising opt-outs mean the message is landing as spam, and no amount of volume compensates for that: the platforms are measuring it too.

Per-run detail

Each automation carries its own recent run history, including dry runs, on the automation itself. Use analytics for the shape and the run history for the specific case that went wrong.