Train tracks, tracking.
Twitter
Facebook
LinkedIn

Tracking for Press Releases

Coverage tracking your clients can see, without building it yourself

Your clients distribute a release and then ask the obvious question: where did it land?
Opoint Tracking answers it. Upload what you distribute, and we return every article that picked it up, scored by how much of the original they used, delivered straight into your platform.

The feature clients want and nobody wants to build

Distribution is the easy half. The hard half is telling a client what happened next.

To do that yourself, you need to crawl a large share of the world’s news, in every language your clients publish in, and then match each crawled article against the release that may have produced it, allowing for editors who cut, quote, and rewrite. Then you need to keep doing it, at volume, without false positives.

Opoint already does all of it. You send us the releases you distribute. We send back the pickups.

How It Works

Upload the release

By FTP or API, as you distribute it.

We match it against what we crawl

Each article indexed by Opoint is compared with the uploaded release and scored for similarity. A full republication scores 100. A partial quote or a rewritten pickup scores lower, in proportion to how much of the original appears.

You set the threshold

The default flags match scoring above 20. Tighten it for near-verbatim pickups only, or loosen it to catch heavier rewrites. Your call, per client if you want.

Results come back via API

Pull matches through the StoredSearch endpoint straight into your platform, or push to FTP. Screenshots of matched content are available for verification.

Subscribe to our newsletter

Key Features

  • Global Coverage
    From major media hubs to niche blogs, we track thousands of online publications worldwide.

  • Pickup notifications
    Matches are delivered within minutes of publication, so your clients see coverage while it’s still live rather than in a report next week.

  • Built to integrate
    Upload by FTP or API, pull matches back through the StoredSearch endpoint. Full documentation is public, so your engineers can scope it before you commit.

  • Visual Dashboard
    With engaging charts, insightful tables, and easy-to-use filters, you can see performance at a glance and instantly identify what drives traffic and engagement.
     

Readership: attach real reach to every pickup

Knowing a release was picked up is half the answer. Your clients will ask the next question immediately: how many people saw it?

Readership answers that. It’s Opoint’s proprietary reach metric, and it attaches to every matched article, so a pickup arrives with an estimate of the audience behind it rather than just a link.

  • Show clients the reach behind each pickup, not just the count.
  • Compare outlets by audience size, so a mention in a small trade title isn’t reported the same way as a national one.
  • Report online coverage on the same basis as print readership and broadcast ratings, which is the language your clients’ boards already speak.

    Readership is only available from Opoint.

Want to see what your clients’ releases are actually picking up?

Technical Specifications 

For more in-depth information on how to set up and use the Tracking API, please refer to our Tracking API Documentation.

Frequently Asked Questions

Upload releases via FTP or API as you distribute them, and pull back matches via the StoredSearch API endpoint. Full documentation is at api-docs.opoint.com/references/tracking.

You decide. Each match is scored by how much of the original release appears in the article. A full republication scores 100; partial quotes and rewrites score lower. The default threshold flags anything above 20, and it can be adjusted.

Yes. The scoring reflects partial reuse, so a pickup that quotes a few paragraphs still registers, at a lower score than a full republication.

Toby Cook, CSO Opoint
Talk to a specialist
Toby Cook, CSO Opoint
Book a data walkthrough
Topics and entities document frontpage

Download