PR and press campaign tracking
Press coverage and wire-distributed releases can send meaningful traffic, but it is hard to separate the link in your own release from links journalists add in their own coverage. UTM parameters on the URLs you place in press releases, media kits, and pitches let you attribute the traffic you directly drove, distinct from earned coverage you do not control. This page covers tagging PR links without overclaiming attribution.
What you can and cannot attribute
You can tag the links in your own press release body, boilerplate, media kit, and pitch emails. You cannot control whether a journalist links to you, and if they do, their link will not carry your UTM — that traffic stays as earned referral.
So PR UTMs measure the floor: traffic from the exact links you distributed. Treat any uptick in untagged referral around a launch as likely earned coverage, reported separately.
- utm_medium=pr (or press)
- utm_source = wire service or named outlet
- utm_campaign = the release or announcement
Wire syndication and link survival
Wire services syndicate a release to many sites, often rewriting or stripping links. Confirm which outlets preserve your tagged link, because a stripped query string drops the UTM and the visit reverts to referral or direct.
A tagged shortlink in the release can be more robust than a long UTM URL that some republishers truncate.
How it appears in analytics and logs
A visit with utm_medium=pr (or press) and a utm_source naming the wire or outlet means a reader followed a link you placed in PR material. Links journalists write themselves will not carry your UTM, so this measures only your owned placements.
Diagnostic use case
Measure traffic from press releases, media kits, and wire distribution so you can see which releases and which placements you control actually drove visits.
What WebmasterID can help detect
WebmasterID files PR-tagged sessions under a named source server-side, so press-driven traffic from your owned links appears as a channel, separate from general referral and direct.
Common mistakes
- Claiming all post-launch referral traffic as PR when only tagged links are yours.
- Ignoring that wire syndication can strip query strings and drop UTMs.
- Using utm_medium=referral for PR, mixing it with uncontrolled mentions.
- Forgetting to tag links inside the boilerplate and media kit, not just the lede.
Privacy and accuracy notes
PR UTMs describe the release and placement, not the reader or the journalist. You see that your tagged link was followed — never any reader identity or newsroom data.
Related pages
- Guest post campaign tracking with UTM
When you publish a guest article or contributed piece on another site, the byline and in-body links send referral traffic. Those clicks usually arrive with the host's referrer, but a UTM lets you separate intentional campaign links from incidental ones and compare which guest placements actually convert. This page covers tagging guest-post links so each host and article is measurable.
- Referral program UTM tracking
Referral programs need their own UTM medium so referred traffic is not confused with organic referrers. This page shows how to label the referral channel and explains why you must not encode individual user IDs in UTM — it leaks personal data and invites abuse.
- UTM shortlinks and link shorteners
A long UTM-tagged URL is ugly to share in print, social, or chat. A shortlink hides that behind a clean short URL that redirects to the full tagged destination, so attribution is preserved while the visible link stays tidy. The key requirement is that the redirect lands on a URL that still carries the utm_ parameters. This page covers how shortlinks preserve UTMs and the redirect pitfalls to avoid.
- Attribution analytics
Separate owned PR links from earned press coverage.
Sources and verification notes
- Google Analytics Help — Collect campaign data with custom URLsUTM reference applied to press-release and media-kit links.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.