How to Measure Referral Traffic From a Press Release Without Overclaiming Sales

You measure referral traffic from a press release by tagging every distributed link with consistent UTM parameters before it goes out, then reading those tagged sessions in your analytics platform's acquisition report — not by watching your overall traffic graph and assuming the bump came from the release. If you skip the tagging step, most of what a press release generates will show up as unattributed direct traffic or vanish into a pickup site's own referral noise, and you'll have no honest way to connect it to a sale.

I've spent close to two decades in search strategy, content marketing, and digital PR, and press release measurement is one of the areas where I see the same mistake over and over, from clients and from agencies that should know better: treating “traffic went up after we sent the release” as proof the release worked. That's not measurement. That's coincidence dressed up as an attribution model. Below is the actual measurement map I use, what it can and can't tell you, and where the limits of that data are.

Step 1: Tag Every Link Before Distribution, Not After

UTM parameters (utm_source, utm_medium, utm_campaign, and utm_content when you have more than one link) are the most reliable way to separate “traffic from this specific release” from “traffic from everything else happening on your site that week.” They have to be applied to the release URL before it's submitted to your distribution service, because most newswire platforms and pickup sites will not let you retag a link after it's live.

A workable tagging convention looks like this:

• utm_source — the distribution channel (for example, the specific newswire, not just “press release”)
• utm_medium — something consistent like “pr” or “press-release” so you can filter this traffic type across every campaign
• utm_campaign — a name unique to this release so you can isolate it later
• utm_content — only needed if the release includes more than one link (for example, a headline link and a boilerplate link) and you want to know which one people actually clicked

Keep the naming convention identical across every release you run. If you change your tagging scheme every time, you lose the ability to compare one release to the next, which is most of the point of measuring in the first place.

Step 2: Build a Measurement Map Before You Look at Any Numbers

Before the release goes out, write down every URL that will carry your tracked link: the primary press release page on the distribution service, and any pickup or syndication destinations you already know about in advance (some services tell you this ahead of time; most don't, which matters for what comes next). For each one, record:

• The exact tagged URL that was submitted or is expected to appear
• Whether that placement is paid distribution (you paid a newswire to publish it) or potential earned pickup (an outlet chose to run it on its own)
• The date it went live or was expected to go live
• A blank column for sessions, a blank column for engaged sessions, and a blank column for whatever conversion event actually matters to your business — a form fill, a call, a purchase

You fill in the last three columns after the release runs, using your analytics platform's acquisition report filtered to your utm_campaign value. This map is what turns “we did a press release” into a specific, falsifiable claim you can check later: did tagged sessions arrive, did any of them engage, did any of them convert. If the answer to any of those is no, the map tells you which stage broke down instead of leaving you guessing.

Step 3: Read the Report as Referral Traffic, Not as an SEO Signal

This is where the overclaiming usually starts, so I want to be direct about it. A press release link almost always carries a rel=”nofollow” or rel=”sponsored” attribute, and it's supposed to. Google's own spam policies are explicit that paid placements and advertorials with links that “pass ranking credit” are treated as link schemes unless those links are properly qualified with nofollow or sponsored tags. That means a compliant press release link is not designed to move your rankings, and reporting it as an SEO win misrepresents what it is. What it can legitimately do is send a human being to your site, and that's what you're measuring: referral traffic and whatever that traffic does once it lands, not search authority.

In your analytics platform, tagged press release sessions will typically show up under a “referral” or campaign-based channel grouping rather than “organic search,” and that's correct. Don't reclassify it in your head as SEO performance just because it touches your domain. If you also want to know how your organic search performance is trending separately, that's a different report and a different set of metrics — I've written about which ones actually matter in SEO Reporting: What Matters, and how GA4 specifically handles that split in Google Analytics 4 for SEO.

Step 4: Know What This Data Cannot Tell You

Here's the part most press release guidance skips, and it's the part that actually protects you from making decisions on bad data.

• Pickup you don't control breaks your tagging. When a real outlet picks up a wire release and republishes it, they frequently strip query parameters, rewrite the link, or drop it entirely in favor of a plain brand mention. You may get real earned referral traffic from that pickup and never see it in your utm_campaign filter, because it arrives as unattributed referral or direct traffic instead.
• “Direct” traffic is often not actually direct. Mobile apps, secure-to-non-secure redirects, and some email or social clients strip referrer data entirely, so a real click on your release can land in your analytics as direct traffic with no source at all. If your direct traffic ticks up the same week your release goes live, that's a plausible connection, not a confirmed one.
• Last-click attribution undercounts influence. If someone sees your release, doesn't click, then searches your brand name and converts three days later, most standard reports will credit that conversion to organic or direct search, not to the release that actually started the journey.
• Sessions are not sales. A tagged session that never converts isn't a failure of the release by itself — it can just as easily mean the landing page didn't match what the headline promised, or the offer wasn't right for that audience. Don't collapse “traffic” and “revenue” into one number, and don't let anyone else do it in a report handed to you.

None of this means the data is useless. It means the data answers a narrower question than most people want it to answer: did tagged traffic arrive, and what did it do. It does not answer “did this release make us money” on its own, and any report that claims otherwise is smoothing over gaps it didn't measure.

Step 5: Decide What to Do Next Based on Where the Map Breaks

Once your measurement map has a few weeks of real numbers in it, the next decision usually falls into one of three places:

• No tagged sessions at all. That's a distribution reach question — how many outlets actually carried the release, and whether the outlets involved reach an audience that would ever click through in the first place.
• Sessions arrived but didn't engage. That's usually a landing page or message-match problem: the page the link pointed to didn't deliver what the release promised.
• Sessions engaged but didn't convert. That's a funnel and offer question, and it's worth separating from the release entirely — the release did its job of sending a real visitor; what happens after that is on the page, the offer, and the follow-up, not on the newswire.

I'll say the boundary plainly, because it's the one part of this that's easy to blur when you're the one who bought the release: distribution is the thing you're paying for — getting a compliant release onto a wire and, where applicable, in front of outlets that might pick it up on their own. What I sell at MBK is search-led release planning, purposeful content production, managed distribution, and the kind of observable reporting described above — published URLs, pickup links where they exist, and route-level analytics. Our own service terms are explicit that “downstream pickup, permanence, indexing, search position, readership, clicks, journalist interest, leads, and sales vary and are not guaranteed,” and that's not a hedge, it's an accurate description of what a press release can and can't promise once it leaves paid distribution and becomes something an outlet either does or doesn't choose to run on its own.

If you're building this measurement map yourself, whether or not you ever run a release through us, the discipline is the same: tag before you distribute, log every placement before you check a single number, and report referral traffic as referral traffic — not as proof of a sale it never touched.