Metrics and analytics

You launched the outreach — you see the numbers

Telegram outreach analytics for every campaign: how much was sent, how much was read, how many replied and how many reached the goal. Plus an honest breakdown of the ones never reached — with a reason for each.

Try it for $9.99 Which metrics we count

7-day trial for $9.99, then from $90/mo. We never charge automatically and never store your card.

The whole campaign funnel

Five numbers that answer the question “does this work at all”. Each is counted from an event that actually happened in the conversation.

Initiated

How many contacts the campaign actually took on. Every conversion rate starts here — not from the size of a list where half is unusable.

Sent

The opening message really went out to Telegram. Queued and scheduled sends do not count towards this number.

Read

The person opened the conversation. Every contact carries an exact read time.

Replied

A real reply came in. This is the first metric that shows whether you picked the right audience.

Blocked

The earliest signal: this number climbs first when the message or the audience is off target. Seeing it on a hundred contacts costs less than on ten thousand.

You define the goal yourself

Reads and replies look the same for everyone. What counts as a result — agreeing to a call, a price list sent, a jump into the bot, a meeting booked — is yours to decide, and the platform counts exactly that.

Conversions are placed right inside the dialogue script: the conversation reaches the right point and the mark is set. From there they land on the same daily chart as the rest of the metrics, so you see not just how many target actions there were but when they happen.

Qualified Asked for pricing Agreed to a call Meeting booked Moved into the bot Declined, with a reason …and any other you care to define

You can see why it did not land

The gap between ten thousand in the list and six thousand sent breaks down into specific reasons. Every contact in the report carries its own status explaining what happened.

Filtered outDid not match the campaign’s selection criteria

Not foundNo such account exists in Telegram any more

Nothing to address them byNo username and no public message

DuplicateThis person is already in the campaign or in the group

Premium requiredThe person’s settings require the sender to have Premium

Paid messagesThe person switched on paid incoming messages

Blocked usThe person closed the conversation from their side

QueuedThe contact is in the pipeline and has not been reached yet

There are twenty-one such statuses in total — they cover the road to the first message and the whole life of the conversation after it.

The numbers are not painted on

A metric is easy to inflate: count everything queued as sent and everything sent as read. Here every number rests on an event that actually happened.

Sent means confirmed delivery to Telegram, not a task placed in a queue.

Read and blocked are real events with an exact timestamp per contact.

Contacts that were never reached do not dissolve into the report: each has its own reason, and you can see it.

That is why you can lean on these numbers when deciding what to change in a campaign.

Launch history is kept

A campaign is rarely launched just once. Every run is its own row with a start date, a limit and how much was actually sent under it.

You can see what changed between runs

Changed the opener or narrowed the audience — you compare two launches by the very same metrics.
A daily chart, not one lump sum

Every metric and conversion is laid out by date. A dip shows up the same day, not at the end of the month.
A report on every contact

Two tabs: the whole audience and the conversations. You can filter down to those who read but did not reply and see where the conversation stalled.

What to do with these numbers

Analytics is not for looking at, it is for changing things. One working cycle takes a few days.

Run a small batch

A hundred contacts is enough to see reads, replies and the first blocks.

Find the bottleneck

Few reads — that is a question about the audience. They read but do not reply — about the opener. They reply but do not arrive — about the script.

Change one thing

The opener, the audience or a branch of the conversation. Change two at once and you will not know which one worked.

Compare with the previous run

The run history is right there, so the comparison is fair — same metrics, same way of counting.

Launch and see the numbers Channel benchmarks

Common questions about analytics

The conversation is run by a regular Telegram account, and it sees the same read receipts any person sees in a chat. That is why a read has an exact time.

Any that make sense in your sales process. A conversion is simply a mark the script sets at the right point in the conversation; the names and the number of them are up to you.

Some contacts are filtered out before sending: the account is gone, the person is already in another campaign, their settings refuse messages from strangers. Every one carries its own status in the report, so the gap is always broken down by reason.

Yes. The campaign report has a row for each: status, read time, whether they blocked, and the full conversation itself.

Yes, the run history is kept: each launch has its own date, its own limit and its own sent count. The metrics are counted the same way, so the comparison holds.

Yes. An API key has a separate permission for reading campaigns: daily statistics, run history and the per-contact report are all fetched by request. You can drop the numbers into your CRM or BI alongside your other channels.

Look at your own numbers

Seven days of full access for $9.99: a working account and every tool on the platform.

Try it for $9.99 Schedule a demo

We never charge automatically and never store your card.