Attempted does not mean published. A post your tool sent to a platform is not a post until the platform confirms it exists, and a tool that counts the attempt is telling you what it did rather than what happened. That sounds like a technicality. It is the difference between figures you can act on and figures that flatter the software.
How a failed post ends up looking published
Tools rarely lie on purpose. They take a shortcut that is right most of the time and wrong in exactly the cases that matter.
- They record the request, not the response. The tool writes "published" when it sends the post, and only changes it if an error comes back. A slow or missing answer leaves the optimistic record in place.
- They read what you selected. The post's list of platforms is the list you ticked. A dashboard that counts from that list counts your intentions.
- They hide failures in a total. Forty posts sent, five failed, "40 posts this month" on the dashboard. Nobody looks at the five.
- They fill gaps with zero. A destination that never published has no engagement. Written as 0 it looks like a post nobody liked, not a post that never existed.
Each shortcut saves the tool a little work. Each one moves the cost onto you, and because the shortcut is right most of the time, the cost arrives quietly: not as an error you can see, but as a figure that is slightly too good, month after month, until the day it matters.
What it costs you
Reports that are wrong in your favour
A report that counts attempts overstates what you did. For a business owner that is a false sense of consistency. For an agency it is a report to a client that will not survive the client opening the platform and counting.
Comparisons that do not compare
If this month's count includes five failures and last month's included one, the month-on-month change is describing your connection problems, not your output. Every trend built on the number inherits the error. Building a history of performance only works when the history is of things that happened.
Decisions about posts nobody saw
"That post did badly" is a useful thing to know if the post went out. If it never did, the lesson you draw from its zero engagement is about the wrong thing entirely.
Problems you find late
A connection that expired three weeks ago, quietly counted as published the whole time, is found when a customer asks why you have gone silent. A tool that showed the failures would have told you on day one, and the fix would have taken a minute instead of costing three weeks of posts.
The rule: evidence, not intent
There is one test that settles it. A destination is published when the platform has returned its own record of the post: an id, a link, something you could open. Not when the button was pressed. Not when the request was sent. Not when no error came back. When the platform said so.
Everything else follows from applying that rule everywhere the number appears.
- The post itself shows a per-destination outcome: published, failed, or unconfirmed.
- The period count includes published deliveries only.
- Failures are shown as failures, with the platform's reason where there is one.
- A destination with no definite answer is unconfirmed, not rounded either way.
- A number that was not measured is unavailable, never 0.
How WyreIt applies it
WyreIt counts a post as published only when the platform hands back its own record. The counters, the tiles, the 7, 30 and 90 day figures and the reports are built from that record and from nothing else.
WyreIt learnt this the way most tools do, by getting it wrong once. One publish attempt went to seven destinations. Four published; three failed for reasons of their own. The screen at the time read the list of selected platforms and showed all seven as published, an empty tile for a post that did not exist, and none of the successes it should have celebrated. The fix was not a patch to the screen. It was the rule above, applied everywhere a publication is counted, and a test that keeps that exact incident from ever passing again. It is why WyreIt Analytics leads with "if WyreIt says it published, it has evidence it published."
What you see now
- Per-destination truth. If a post went to five accounts and two failed, you see five outcomes. What happens when one platform publishes and another fails walks through it.
- Failures that stay visible. In the post list, the period figures and the reports. A problem with one account cannot hide inside a total.
- Unconfirmed as its own state. Shown, not counted as published, not counted as failed.
- Unavailable, never zero. A figure that could not be read is marked as such, with the reason where there is one.
How to check your own tool
You do not have to take a tool's word for it. Three checks take ten minutes.
- Find a post that failed somewhere. Most accounts have one. Look at how the tool shows it. Is the failed destination visible, or has the post got one tick?
- Count a week by hand. Open each platform, count the posts that actually appear, and compare with the tool's figure for the same week.
- Disconnect an account for a day. Schedule a post to it. See whether the tool shows a failure, a success, or nothing at all.
If your tool passes all three, keep it. If it does not, every figure it has ever shown you needs a mental asterisk, and every comparison built on those figures needs re-reading with the failures put back in.
Common questions
Is a scheduled post "published" once it is scheduled?
No. Scheduled means queued for a future time. It becomes published when it goes out and the platform confirms it. A tool that counts scheduled posts as published is counting the future.
My tool showed a post as published but it is not on the platform. What happened?
Most likely the tool recorded the attempt and never checked the answer, or the platform removed the post afterwards. Either way, the platform is the authority. Check the reason on the failed destination in your tool if it shows one, and reconnect the account if the connection expired.
Why does WyreIt show "unconfirmed" instead of just retrying?
Because a retry of a post that might already exist creates a duplicate. Unconfirmed tells you to check the platform before doing anything, which is the safe answer when the platform has not given a definite one.
Does this affect small businesses or only agencies?
Both, but a small business owner has less time to notice. Social media analytics for small business is written for the owner who checks once a week and needs the figures to be right when they do.
If WyreIt says it published, it has evidence it published. Attempted is not published. The platform decides, and the figures should agree with it. Analytics is included on every plan and in the 14-day free trial, with no card needed. See how WyreIt Analytics works or see pricing.
WyreIt is a social media management tool for small business owners and sole traders. Post to Facebook, Instagram, X, TikTok, and more from one dashboard — at a fraction of the price of Hootsuite.