# See what the carrier saw.

Every send produces a carrier delivery receipt. Bird turns those receipts into delivery, failure, and latency metrics, broken down by country, carrier, and sender, in the dashboard and through a stats API you can query from your own code.

## The reporting side of the same API.

## Nothing new to instrument.

Analytics is the reporting side of the Bird SMS API. You already send through it and already receive a delivery webhook on every state change; analytics is Bird keeping the count for you, so you can ask how a campaign delivered without standing up a warehouse to hold the events first.

## What a delivery receipt tells you.

Measured from the carrier, not inferred.

## Query the numbers from your own code.

The stats API takes a time range and a groupBy, and returns the rolled-up counts. Group by country and carrier to find the route that's underperforming, by sender to see which of your IDs a carrier trusts. The same aggregation backs the dashboard charts, so a number you screenshot matches a number you can pull on a schedule.

## Pull the timeline for one message.

Aggregates answer how a campaign did; a support ticket asks about one text. Pass a single message ID to the events endpoint and you get its whole life in order — queued, sent, the carrier delivery receipt or the failure, each stamped with a time and, when it failed, the carrier's own reason code.

## Go deeper in the docs.

Build your own store from the delivery webhooks, read the deliverability guide for what the failure codes mean, and reconcile counts against billing and usage.

## The receipts come from the routing layer.

A delivery receipt is only as good as the path that produced it: routing chooses the carrier link each message takes and hands back the DLR these metrics are built from. If you run two-way numbers, inbound messages are counted here too, so a reply volume sits next to the delivery rate that earned it.

## The metrics ship with the API that produces them.

Analytics isn't a separate product to buy. Send through the Bird SMS API and the delivery, failure, and latency reporting is already there, on infrastructure that carries about 40% of the world's commercial SMS.