SMM report for Telegram channels and communities

SMM report for Telegram and communities: what goes into it

An SMM specialist running a client’s Telegram channel, VK community broadcasts and a chatbot opens three different dashboards every month and merges the numbers by hand. In Reportkey these platforms connect to one project, and the client gets a recurring document compared with the previous period:

• TGStat: subscribers, views, average post reach, engagement, citation index and the channel’s top posts;
• Senler: subscriptions, unsubscriptions and net growth of broadcasts, tagged sources and messages sent;
• Salebot: new bot subscribers by messenger, conversations and deals in the built-in CRM.

The report opens by link or goes out as a PDF file. Agency branding and automatic scheduled sending are not on every plan.

Telegram channel statistics for a client

A channel owner cares about three things: is the audience growing, do people read the posts, and what landed best. The TGStat section answers each one. Subscriber dynamics are built by day, week or month, and Reportkey calculates period growth itself. Views come together with average post reach and daily reach. The engagement block collects ERR, ER, the citation index, mentions and forwards, which show whether content spreads beyond the channel. The section ends with the period’s top posts with views, reactions, comments and shares.

VK broadcasts and the Senler subscription funnel

Senler works inside VK communities: a user subscribes to a broadcast and the community sends them messages. For a report this is a subscription funnel. The section shows subscriptions and unsubscriptions for the period and net growth, separately for each subscriber group. The tagged sources block tells which link or campaign brings people into the broadcast, using Senler’s own tags and standard UTM parameters. The last block shows how many messages each broadcast sent. The API returns one total for the period, so Reportkey builds daily dynamics with separate calls per day.

Salebot chatbot analytics

Salebot is a bot builder for several messengers with its own CRM. In the report it covers the path from subscription to deal. New bot subscribers are split by messenger and by project bot. The conversations block counts messages for the period, undelivered messages and manager replies. CRM deals are split into active, won and lost. Note that deals arrive with their current status, and the API keeps no history of moves between stages. Client sources come from the tags and variables the bot stores.

VK community, ads and the website next to the channel

Messengers rarely live apart from the rest of the promotion. The same project can hold VK community statistics: reach, visitors, subscriptions and post reactions next to Senler broadcasts. If subscribers are bought through ads, VK Ads goes alongside with spend and clicks, and other accounts come from the advertising systems group. When the channel and bot send people to a website, Yandex Metrica and other web analytics sources show what visitors did next.

What to keep in mind before showing numbers to a client

Each source in the group counts in its own way, and it is better to say so upfront. TGStat sees the channel from outside, like any external observer, so its views and reach can differ from the admin panel. Senler does not pass broadcast opens and clicks. Salebot shows a deal amount only where the bot scenario records it. Labels in the report name exactly what was measured, so the client does not compare things that are not comparable.

How to connect a channel, broadcast or bot

1. Sign up for Reportkey: 14 days free, 30+ integrations.
2. In the integrations section add access: a channel or chat for TGStat, an API key from the API settings and the community ID for Senler, a project API key with read rights for clients and CRM for Salebot.
3. In the project pick the channel, community or bot, add VK and ads, and set up sending.

See a multi-channel document in the in-house team demo report, terms on the pricing page, and the other groups in the integration catalog.