Pressfront / Trace / Media monitoring vs attention intelligence
Explainer · Updated September 2026
Monitoring answers “is anyone talking about us”. Attention intelligence answers “how fast is this moving and where did it first appear in public”. The second question is harder, answered less confidently, and usually the one you actually needed.
Media monitoring is a list. Attention intelligence is a timeline with a confidence number on it. Monitoring collects mentions and alerts you when the count moves, which tells you a story exists. Attention intelligence adds the two things that change what you do next: how fast it is moving against its own baseline, and the earliest public appearance it can verify, with the gaps in the evidence printed alongside.
Both are useful and they are not rivals. If you need clip coverage, compliance archives, broadcast, or a share-of-voice report for a board deck, buy a monitoring suite; they are mature products that do those jobs well and we do not do them at all. If the question is "this is spreading, where did it come from and how long have we got", that is the gap attention intelligence fills.
The difference on one real story
The Carney $6,000 rumour, traced 2026-09-15Full trace: the Carney story page.
The private-account rule. We never log in, follow anyone, request access to a locked account, or use scraped private data. A private account is invisible to us and stays that way. So what you see below is the earliest public appearance we could verify, never a proven origin. If a story started in a group chat, a DM or a locked profile, the first public post is the node we can see, and we say so rather than dressing it up as the source.
Run one yourself: Trace a story. How the sweep and the confidence number are built: the methodology card.
| Question | Media monitoring | Attention intelligence |
|---|---|---|
| Is anyone talking about us | Yes, this is the core job | Yes, as an input |
| How fast is it moving against its own baseline | Volume charts, sometimes an anomaly alert | Velocity against a baseline, with the arithmetic shown |
| Where did it first appear in public | Rarely; a feed is ordered by recency, not lineage | The earliest verifiable public post, with a confidence number |
| What did the sweep fail to reach | Usually not reported | Printed on every result |
| Broadcast, print clips, compliance archive | Yes, mature products | No |
| Share of voice reporting over a quarter | Yes | No |
| Private accounts and group chats | No | No, by hard rule |
The row that matters is the third one. Lineage is the expensive question, and it is the one a recency-ordered feed structurally cannot answer, because the loudest post is almost never the first.
This is not a criticism of monitoring products, it is a property of how they are built. A feed ranks by recency or by engagement, and an origin post has neither property: by definition it is the oldest item, and it is usually the quietest.
We hit this ourselves. On the gravity story, the seed post had three total engagements. An engagement-ranked pull over the whole window never surfaced it, and our own first deep sweep reported a post from 50 days later on the wrong platform. Finding it required searching the boundary on purpose rather than searching for the loudest thing, and then keeping the result instead of discarding it.
That is the architectural difference. A feed optimises for what is happening. Lineage requires optimising for what is earliest, which is a different search.
Broadcast and print. Compliance archiving with retention you can show an auditor. Share of voice and campaign reporting across a quarter. Journalist databases and outreach workflows attached to the same subscription. Coverage of languages and regional outlets at a depth a young product does not have.
If those are your requirements, buy the suite. We are not going to pretend a trace replaces a monitoring contract, and a comparison page that claimed otherwise would be the same rigged scorecard we complain about everywhere else on this site.
Monitoring notices. Attention intelligence explains. In practice the workflow is: an alert tells you something is moving, and then you need the earliest public post, the fuse length, and an honest statement of what could not be seen before you decide whether to respond, to whom, and how fast.
And then, sometimes, the answer is to say something yourself, in which case getting published is the next step rather than a competing one. Knowing there is a narrative forming is a better reason to publish than a calendar slot is.
Media monitoring collects mentions and tells you a story exists. Attention intelligence adds how fast the story is moving against its own baseline and where it first appeared in public, with a confidence number and a printed list of what the sweep could not reach. Monitoring answers whether anyone is talking. Attention intelligence answers how fast, from where, and how sure we are.
No, and we would not sell it that way. Monitoring suites do broadcast, print clips, compliance archiving, share of voice and journalist outreach, and they do those well. Trace does one thing they generally do not: it works backwards to the earliest public appearance of a story and tells you how confident it is. Plenty of teams would sensibly run both, for different questions.
Because a feed ranks by recency or by engagement, and an origin post is the oldest item and usually the quietest one. On a story we traced, the earliest post had three total engagements and never surfaced in any engagement-ranked pull, including our own first attempt. Finding it required searching the window boundary deliberately, which is a different search from the one a feed runs.
Ours does not, ever. No logging in, no following, no access requests, no scraped private data. That is a hard rule rather than a temporary limitation, and it is why every result is labeled earliest public appearance rather than origin. If a story started somewhere private, the first public appearance is what we show, and we say plainly that it may not be the beginning.
Free trace, no account for the first one. Earliest public appearance, fuse length, and the gaps.
Honest fine print. Trace reports the earliest public appearance we could verify inside the window we searched, which is not the same thing as a proven origin. We only read public posts and public metrics, so deleted posts, screenshots laundered out of private accounts, and anything that started in a DM or a locked group are invisible to us, and every result names the sources that came back empty. Confidence is a number we publish together with the gaps behind it, never on its own. Trace describes what has already happened and how fast it is moving right now; it does not predict what will go viral, and no honest tool does.