Channel
@thenewsletterplugin
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
15subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002050935875 |
|---|---|
| Type | Channel |
| Username | @thenewsletterplugin |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/thenewsletterplugin |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 23:39 | 15 | -1 |
| 11 Aug 2026, 22:16 | 16 | no change |
| 7 Aug 2026, 23:52 | 16 | first reading |
20 posts held, back to 31 October 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 7 July 2026. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 1 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 31 October 2024 to 7 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
In version 9.3.0 there are new open and click tracking methods. They should help with site protection solutions, like cloudflare and similar, blocking the tracking image. You can experiment with them by changing the new "tracking links" option in the Newsletter main Settings.
With version 9.2.9 we included the AI features previously provided by our AI addon. Now the AI connectors provided by WP will be used, so you have control over which AI provider is used. If you don't need the AI features, don't worry; the plugin doesn't do anything by itself!
Just released an update for our SMTP2GO integration addon with a better error detection and reporting. To see the update, save the main settings of the Newsletter plugin and then update the addon from your site's plugins page.
New addon release: integration with resend.com for a reliable delivery of your newsletters!
The advanced blocks addon has been released with an updated RSS block. New options on the content inclusion and style.
Newsletter 9.1.5 solves a problem of HTML left in the email body by the composer. It does not affect the layout, it's not visible and does not contain data. Anyway, it should not be there.
Our latest newsletter has all the new features and improvements. https://www.thenewsletterplugin.com/?na=view&id=356
The new 9.1.4 release of the Newsletter plugin, adds more controls on the newsletter title/text/button general settings, the new button border radius control and a few small fixes.
The Automated addon has been updated to select specific months for the monthly schedule and adds a calendar overview with all the sending days.
A new experimental addon to fully automate yearly emails. You can find it on Newsletter/Addons page in your site.
The Black Friday sale is live right now! https://www.thenewsletterplugin.com/premium?utm_medium=post&utm_campaign=black-friday&utm_source=telegram
The integration with SMTP.com, a premium delivery service, has just been released. Bounces and complaints management included. https://www.thenewsletterplugin.com/documentation/addons/delivery-addons/smtpcom-extension/
Showing the 12 most recent of 20 posts we hold for @thenewsletterplugin. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 17 September 2026 — this entry's latest reading, not the date you are reading this.
“The Newsletter Plugin” (@thenewsletterplugin), 15 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/thenewsletterplugin.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.