How to Track Press Release Traffic in GA4 with UTM Links

A distribution report tells you where a press release appeared. It does not tell you what readers did after visiting your website. To connect an announcement with visits, enquiries and sales, you need a tracking plan before the release goes out.

This guide explains how to track press release traffic in Google Analytics 4 using UTM links, how to read the results, and where those numbers stop telling the full story. It is written for business owners, marketing teams and agencies that need a useful campaign report rather than a long list of published URLs.

Start with the action you want readers to take

Choose one primary outcome before writing the call to action. A product announcement might send readers to a product page. An industry report might invite them to download the research. An expansion announcement could direct prospective customers to a local enquiry form.

The destination should match the news. Sending every reader to a general homepage makes the next step harder to find and gives you less useful evidence about whether the announcement worked.

Record the landing page, the intended action, the distribution date and the campaign owner. Decide what you will count as success: qualified enquiries, completed registrations, product purchases or another clearly defined action. Visits are useful, but they are not interchangeable with business results.

What UTM links actually measure

A UTM link is a normal website address with campaign information added after the address. When a reader follows that link and Analytics collects the visit, the parameters help identify its source, medium and campaign.

Google recommends including utm_source, utm_medium and utm_campaign whenever you tag a campaign URL. Its documentation also strongly recommends relevant campaign ID and source-platform fields to avoid missing values in reporting. Read the Google Analytics URL-tagging guidance when setting your team's naming standard.

• utm_source: the named source of the traffic, such as the distribution service.
• utm_medium: the marketing method. This guide uses press_release as a consistent custom label.
• utm_campaign: the particular announcement, such as warehouse_opening_2026_10.
• utm_content: an optional label for distinguishing links within the same campaign.

These labels are your reporting convention, not a guarantee about who read the release. If the same tagged link appears on several republishing websites, its source value still identifies the label you supplied. It does not automatically change to the name of each outlet.

Build a press release tracking link

Imagine a company announcing a new warehouse and inviting retailers to request a delivery quote. The example below uses a reserved example domain; replace it with your real destination before distribution.

https://example.com/retailer-delivery?utm_source=anewswire&utm_medium=press_release&utm_campaign=warehouse_opening_2026_10&utm_content=main_cta

Here, anewswire identifies the distribution source, press_release identifies the method, and warehouse_opening_2026_10 identifies the announcement. The content label distinguishes the main call-to-action link from another link in the same release.

1. Choose the final landing page, not an address that will be replaced after launch.
2. Enter the destination and campaign values in Google's Campaign URL Builder, linked from its URL-tagging guidance, or construct the address manually.
3. Use lowercase values and a consistent separator, such as underscores. Google treats parameter values as case-sensitive, so ANewswire and anewswire can split reporting.
4. Add the finished URL as the hyperlink behind descriptive text, such as “request a retailer delivery quote.” Keep the visible release readable.
5. Save the exact URL in the campaign record so everyone uses the same version.

A URL's first query parameter begins with a question mark. Further parameters use ampersands. If the destination already contains a question mark, append the UTM fields with an ampersand rather than adding a second question mark.

Do not put customer names, email addresses or other personal information into campaign parameters. Keep labels descriptive without making them sensitive.

Test the complete journey before distribution

A link that opens a page is not necessarily a link that produces useful reporting. Test the journey from the release preview through the landing page to the intended action.

• Open the tagged link and confirm it reaches the correct page on both desktop and mobile.
• Check whether any redirect preserves the campaign parameters.
• Confirm the destination has the correct GA4 implementation and that collection follows the site's consent settings.
• Complete a test of the intended action, using a clearly identified test submission where appropriate.
• Ask the analytics owner to verify that the event is recorded and, where relevant, marked as a key event.
• Check that the distributor accepts the full hyperlink and review a published copy after distribution.

Keep test traffic separate from campaign evaluation. Use a clearly labelled test campaign and an approved testing method rather than repeatedly clicking the production link and treating those visits as genuine interest.

Find the campaign in Google Analytics 4

Use the Traffic acquisition report to examine traffic from new and returning visitors. The User acquisition report answers a different question about how users were first acquired, so the two reports need not show matching results.

1. Open the correct GA4 property and select Reports.
2. Go to Acquisition > Traffic acquisition. Navigation can vary with the property's report collection. If the report is missing, ask an Editor or Administrator to restore or locate it.
3. Set a date range that includes the distribution date and your agreed reporting window.
4. Change the table dimension to Session source / medium and search for your source, such as anewswire / press_release.
5. Use Session campaign to isolate the specific announcement. Where the report supports it, add this as a secondary dimension or apply a suitable filter.
6. Review sessions, engaged sessions, engagement rate and the relevant key events. Record the selected dates and dimensions with the results.

These dimension names and the report's purpose are documented in Google's Traffic acquisition report guide. Avoid looking for campaign labels only in landing-page query-string reports: Google's tagging documentation notes that UTM parameters are omitted from certain page-path and landing-page query-string dimensions.

Why press release visits may appear as Unassigned

The custom medium press_release is useful for keeping announcements separate, but it is not a named standard medium in Google's default channel rules. If no other channel rule matches the traffic, it can appear as Unassigned.

That label alone does not mean your campaign parameters were lost. Check Session source / medium and Session campaign first. If your team wants a dedicated PR channel, an analytics administrator can consider a custom channel group. Google's default channel group documentation explains that Unassigned is used when no channel rule matches and that default channel definitions cannot be edited.

Measure enquiries, not just visits

UTM parameters do not create form tracking, purchase tracking or key events. Those need to be implemented and checked separately. A button click is also not the same as a completed enquiry; choose the event that represents the outcome you actually need.

For a lead-generation campaign, review the relevant key event alongside sessions. Then check lead quality in your sales records. Ten enquiries from unsuitable prospects can be less valuable than two from companies that meet your buying criteria.

If campaign information needs to pass into a customer relationship management system, ask the website owner to implement and test that process. Do not assume a form automatically stores UTM values or preserves them across later visits.

A worked reporting example

The following figures are illustrative, not ANewswire performance results. Suppose a campaign costs $600, generates 240 measured sessions, and produces 12 verified enquiries. Four of those enquiries meet your sales qualification criteria.

• Cost per measured session: $600 ÷ 240 = $2.50.
• Cost per enquiry: $600 ÷ 12 = $50.
• Cost per qualified enquiry: $600 ÷ 4 = $150.

This is a cost-efficiency calculation, not proof of revenue return. To estimate return, you also need a defensible connection to completed sales, an agreed attribution method and the appropriate costs. Do not turn a projected pipeline value into reported revenue.

Keep distribution, readership and website results separate

A placement is a publication location. A page view is a measured viewing event under a particular system's rules. A website session is a visit recorded by your analytics setup. An enquiry is a business action. These are different measures and should remain separate in the report.

Do not add the audiences of every publishing website and describe the total as people who read your announcement. Likewise, a distribution dashboard's click count need not equal GA4 sessions. They may use different measurement rules, and the website may not collect every visit.

Use a short report with distinct sections: verified placements, measured campaign traffic, relevant key events, qualified outcomes and limitations. This makes the results easier to interpret without overstating what distribution achieved.

What to check when the numbers look wrong

The campaign shows no traffic

First inspect the live hyperlink. Confirm the parameters survived publication and any redirects. Then check the GA4 property, date range, data collection and consent configuration. Allow for reporting processing rather than assuming the standard acquisition table updates immediately.

The campaign appears in several rows

Compare the exact labels for capitalization, spaces, separators and spelling. Choose one naming convention for future links. Keep a note of earlier variants so the current report includes them rather than quietly dropping part of the campaign.

The release has placements but few visits

Publication does not require readers to click through. Review whether the release offers a useful next step, whether the destination fits the announcement, and whether the linked text clearly describes what readers will find.

Visits appear, but no enquiries are recorded

Test the form and its tracking before changing the campaign. If both work, review the page itself: relevance, loading problems, mobile usability and unnecessary form fields can all deserve investigation. Use the evidence to choose the next test rather than assuming distribution is the only explanation.

The limits of press release attribution

Tagged links measure a route into your website, not every effect of an announcement. A reader may later search for your company, type the address directly or contact sales without following the original link. Republishing sites may alter hyperlinks, and privacy controls or consent choices can limit collection.

Review related signals, such as relevant media enquiries and branded-search trends, separately. An increase after publication can be worth investigating, but timing alone does not prove the press release caused it.

A practical checklist for the next announcement

Before distribution, agree on the outcome, prepare the landing page, create consistent UTM links and test the action you want readers to complete. After publication, inspect the live links, review the same reporting window and document both the results and their limits.

If you are still deciding whether an announcement warrants a release, start with what a press release is and when to send one. For guidance on choosing the right content format, read press releases, news articles and blog posts compared.

The aim is a repeatable measurement process. When every announcement uses the same naming rules and a tested destination, your next campaign report becomes more useful than the last.