Tracking referred readers and useful enquiries

Tag the link used in published coverage, review the resulting sessions in Google Analytics 4 (GA4), and carry the link’s campaign values into enquiry records where your form setup allows. Apply an agreed rule to decide which enquiries count as useful.

Report sessions attributed to the tagged link and qualified enquiries separately. Sessions are not unique readers, and attribution does not prove that coverage caused an enquiry or a later decision.

Attribution Limitations vs. Real-World Outcomes

Prepare a route readers can use

Choose a destination page that answers the question raised by the story. Use the Google Analytics URL Builder to add the UTM parameters utm_source, utm_medium and utm_campaign, with consistent values agreed before sharing the link.

A tagged URL follows this pattern: example.com. Use lowercase values consistently, and give each placement a campaign value the team can recognise.

The publisher controls its editorial links; tagging is a request, not a condition of coverage. Record the URL that actually appeared and its destination, check any redirects, and confirm the parameters reached the landing page.

Steps to Track Referred Readers and Qualify Enquiries

Interpret traffic as attributed activity

In a configured GA4 property, open the Traffic acquisition report and review sessions by session source and medium for the publication period. Check the landing page and use consistent dates and definitions when reviewing the relevant traffic source.

If a publisher link has no tags, visits may be grouped as organic, referral or direct. Direct traffic can include visits where referral information was not passed, so those rows may not identify visits from a particular placement.

Redirects, missing campaign information and blockers can affect recorded traffic sources. Consent settings can also affect what is collected, so do not describe a total as wholly observed without checking the property’s reporting.

Sessions are not unique readers of an article. Some readers never click; others arrive later through search, a shared link or a direct visit. A visit increase near publication is a reason to investigate, not proof of impact.

Pre-Review Checklist for Campaign Attribution

Qualify enquiries in the contact record

Where your form setup allows it, preserve utm_source, utm_medium and utm_campaign in hidden form fields and pass them to the contact or CRM record when the form is submitted. InsightSquared CRM is one example of a CRM that can receive UTM data.

Use the saved values to associate an enquiry with the tagged campaign. They identify the campaign values carried with the enquiry, not a unique reader, and they do not prove the coverage caused the enquiry.

Agree on a rule before reviewing enquiries. For example, count a trade enquiry as useful only if it concerns the relevant service and comes from an organisation the team can serve.

Record each request as submitted, reviewed or meeting the agreed rule. Keep unrelated requests, duplicates and spam in separate categories, and apply the same rule consistently.

State the result’s boundary

A compact report can show the placement, dates, sessions attributed to the source, submitted requests and requests judged useful under the stated rule. Note missing data and other active channels.

If the item has no link, referred visits through that route cannot be measured. Zero recorded referrals does not mean zero interested readers.

Key Metrics from GA4 and Enquiry Tracking