What the bot sends you
The exchange page shows you state, not history: there is no activity feed on it, no list of past placements, and no record of what happened last week. Every event that matters reaches you as a Telegram message from our bot instead, and decisions on your own ads also reach you by email and on the platform notifications page.
Two things exist on the website afterwards, and neither replaces the messages below. Approvals and declines of your own ads are listed on the notifications page. And a hosting record per channel — recent placements with their state, views, clicks and credits — sits on that channel's own dashboard. Neither carries the deadlines and stakes the bot's messages carry, and neither reaches you: you have to go and look.
This page lists every message the exchange sends, so you know what you are supposed to be receiving — and what a missing message means.
Before you start
- Your Telegram account must be linked to your Onflow Ads account. That is the same pairing the exchange requires anyway.
- You must not have blocked our bot. Blocking it silences every message on this page while the exchange keeps running.
- Times in every message are written in IST, in one format: "05 Aug 2026, 07:30 PM IST".
Messages you get as a host
| Message | When it arrives | What it tells you |
|---|---|---|
| An ad is waiting for your review | A matched ad is held because Review ads is on for that channel | The channel, the ad's level, and a Decide by time 24 hours out. It says an approved ad runs for 24h and comes down on its own, that your reliability is unchanged either way, and that an undecided hold is skipped and offered to another channel — never posted without your yes, and never held against you |
| An ad just went live in your channel | A placement posts automatically | The channel, the level, when it went up, when it comes down, and the stake in plain numbers: "leaving it up the full window adds +0.05; taking it down early costs -1.50." Plus "You do not need to remove it yourself" |
| The ad you approved is now live | A held ad you approved has posted | The same shape as above, for the placement you released |
| An ad review timed out | You left a hold undecided for 24 hours | The channel, the 24-hour window, that nothing was posted, that your reliability did not move, and that no credits were minted or lost |
| Hosted ad removed on schedule | A placement completed its full term | Views, clicks, that the placement served its full window so your hosting credits are added on onflowads.com within a few minutes, and that +0.05 was recorded for the clean run. This is the message that confirms an earning placement |
| A hosted ad came down early — no penalty this time | An early removal your plan's grace covered | That nothing was charged against you, that no credits were minted for the placement, and how many free early-removal passes are left this cycle |
| A hosted ad was removed early | An attributable early removal with no grace left | The reliability move that was recorded (−1.50) and that it is applied on onflowads.com — or, when it belongs to an episode already counted, that there was no further drop — whether a strike was recorded, that no credits were minted, on a plan with free passes that they are all used this cycle, and — if the strike threshold was crossed — "Your channels are paused from the exchange until …" with the date it lifts on its own |
| The bot lost its rights while a hosted ad was live | The bot's admin rights were removed (or the bot was taken out of the channel) while a placement was inside its window | The same facts as the message above — a grace pass never covers this one — and a request to make the bot an admin again with permission to post and delete |
| We could not take a hosted ad down | The placement served its full term but the bot had been demoted and could not delete it | That no reliability was lost (the ad did serve its window), that a strike was recorded instead, and that credits were withheld (a swap host is told instead that a swap earns no credits either way — it is paid in kind). It asks you to restore the bot's delete right |
"Hosted ad removed on schedule" arrives once per placement that served its term, so your chat with the bot reconstructs which placements earned. The amount is minted by the website a few minutes later, so the message does not quote it. For a per-channel total, every channel's own dashboard carries a Credits earned figure on every plan. There is no screen for an account-wide total — every credit is minted by one channel — so ask support if you need one. See How credits work.
Messages you get as an advertiser
| Message | When it arrives | What it tells you |
|---|---|---|
| Your ad is approved | A reviewer approved your submission | The campaign's OFSE- id and that it now goes out across the exchange, spread across the cycle rather than all at once. A swap campaign carries a button to ask why it has not matched yet |
| Your ad was not approved | A reviewer declined it | The campaign id and the reviewer's exact reason, plus the reassurance that a decline never lowers your reliability, so resubmitting costs you nothing |
| Placement complete | One placement finished its 24 hours | The campaign id, when it went live and came down, views, clicks, the click rate, and that +0.05 was recorded for the clean run and is applied on onflowads.com |
| One placement of your ad ended early | A host took your ad down inside its window (a regular placement; a swap is covered by A swap ended early) | The campaign id and the window it should have run, that it affects only that one placement, that your reliability is unchanged and that no money moved. It never says which channel |
| A swap ended early | A swap was voided because one half came down early | Which side was at fault. The side that broke it is told the removal was recorded and that onflowads.com works out what it costs; the website's ruling follows as a host message above — no penalty this time when a grace pass covered it, A hosted ad was removed early when it did not. The other side is told it is not logged against them |
| A swap could not be closed cleanly | Both ads ran their full window, but one side had removed the bot's rights so its ad could not be taken down | Which side was at fault. Nobody's reliability drops for this — the window was served — and the side that behaved gets its clean-run +0.05; the website's ruling follows for the other side as We could not take a hosted ad down |
| An ad you approved will not be posted after all | You approved a held ad and the advertiser's campaign was paused before it went out | Which of your channels it was for, that nothing was posted, that your reliability is untouched and no credits were won or lost, and that you will be asked to review the ad afresh if the campaign starts again rather than have an old yes used |
| Your exchange ad is paused — the pool is short | An approved ad's eligible pool fell below the placements your plan schedules for it | The ad's OFSE- id, the quota and the count now, that nothing is charged while it waits and live placements finish their window, and that it resumes on its own. Sent by the website on every leg |
| Your exchange ad is running again | The pool recovered and the ad was resumed | The ad's id, the count now against the quota, and when the next placement goes out — in a few minutes if one was already due, otherwise at the time it was already booked for. Sent by the website on every leg |
| The exchange pool is ready for your ad | An ad of yours was refused because the pool could not carry it, and the pool has since grown to the size your plan needs | The level and topic of the ad you tried to submit, how many eligible channels there were then and how many there are now against the number your plan needs, and that nothing was charged the first time. Sent by the website, not the bot, so it reaches every device: Telegram, email, the notifications page and a browser push where you allowed one |
The rule is simple: everything the website decides reaches you by email as well, and everything the bot merely observed does not. So approvals and declines, the pool-ready notice, an ad paused or resumed for the pool, a voided review and the website's ruling on a hosting breach (the host messages above from no penalty this time to We could not take a hosted ad down) all arrive by email and as a row on the platform notifications page at https://onflowads.com/telegram/dashboard/notifications — as well as on Telegram. Everything else on this page is a Telegram message only.
The first three of those are also marked urgent, which means they skip the email digest: if you have email batching switched on, these still arrive immediately, because "your campaign stopped" and "you can submit it again now" are not worth reading a day late.
Exchange messages carry two standing lines: what was recorded about your reliability — always "recorded … applied on onflowads.com", never a new score, because the bot moves no score — and "Money: nothing charged and nothing paid — the exchange runs on hosting credits, not cash." The only exchange events that touch cash at all are a delivery boost you chose to buy and its refund, which the website moves and which appear in your wallet ledger rather than here.
What a subscriber sees when they tap your ad
Not a notification to you, but worth knowing. Every button and link in your ad takes one first-party hop — its own onflowads.com/rr/… short link — that counts the tap and sends the reader straight on: into your own connected channel through a campaign invite link, where Telegram counts the join; to any other Telegram address exactly as written; or to a website. Nothing opens a chat with the bot. Placements published before this design still answer a tap with "🔗 Here you go —" and one button until they come down.
If something goes wrong
| What you see | What it means | What to do |
|---|---|---|
| No messages at all, though ads are running | You have blocked the bot, or the Telegram pairing was lost | Unblock the bot and open a chat with it. If the exchange page shows the First, connect your Telegram card, redo the pairing |
| A "Hosted ad removed on schedule" message, but no credit on the channel's dashboard | The website mints credits on a sweep a few minutes after the takedown | Wait a few minutes and reload. If it is still missing, contact support with the channel's OFSC- reference |
| A removal message you do not recognise | Something removed a placement in one of your channels — an admin, a scheduled cleaner, another bot | Check who else can delete in that channel. The exchange attributes a removal to the host account, whoever pressed the button |
| "no further drop — this removal is part of an episode already counted" | Several placements broke in one event | This is the exchange pricing one episode once. Nothing extra was charged |
| An approval email but no Telegram message | The email path and the bot path are independent | Check that the bot is not blocked. The decision itself stands either way |
| No message when a hold expired | Reaching you failed, or the bot is blocked | Watch the Ads waiting for your review card on the hub instead, and consider switching that channel back to automatic |
Frequently asked
Can I turn these off?
Only all together. They are the exchange's only reporting surface, and several of them — a hold's decide-by deadline, an early-removal penalty — are things you need in order to act. They belong to the Marketplace row in Settings: switching its Telegram toggle off silences all of them (and the website's own exchange messages on Telegram with them); so does switching all four Telegram toggles off, which the bot reads as "do not reach me on Telegram at all" (see Bot notifications); blocking the bot does the same. Either way the exchange keeps running, but you only learn what it did from the site: the Ads waiting for your review card on the hub, the notifications page, and each channel's dashboard.
Is there a history I can scroll back through?
Your Telegram chat with the bot is the fullest history, and the only one that covers your own campaigns placement by placement. On the site there are two partial ones: approvals and declines on the notifications page, and each channel's recent hosted placements on that channel's own dashboard.
Why is everything in IST?
One house format across the whole platform, so timestamps in a bot message and a website page can be compared without conversion. The exchange's own scheduling — an ad's day-parting window — is in UTC, which is stated on that control.
Do hosts and advertisers ever learn each other's identity from these messages?
No. A host's message names their own channel and never the advertiser; an advertiser's message names their own campaign and never the channel. The one exception is a swap, which is disclosed by design.
Related
- Hosting ads — the events behind the host-side messages.
- Running ads — the campaign lifecycle behind the advertiser-side messages.
- Earning credits by hosting — what the credits line in a takedown message is worth.
- Rules and fair play — what an early-removal message actually costs you.