GA4 will tell you that your guide to choosing a plumber got 4,000 views last month. It will not tell you that two of those readers became customers, or which two. That gap is the whole difference between web analytics and content analytics for leads, and it is worth understanding before you decide what to write next.

TL;DR
  • GA4 measures audiences, not customers. It counts sessions, and sessions are anonymous by design.
  • A count is not enough at small volumes. Twelve conversions from organic does not tell you who enquired, or what they read first.
  • Popular is not the same as productive. Ranked by views one page wins; ranked by enquiries produced, a narrower page often wins instead.
  • Content attribution ties each enquiry to the named person and the pages they read on the way, so you can rank content by enquiries rather than views.
  • Keep both. GA4 for audience size and trends, lead-level attribution for which writing brings customers.

What GA4 actually does well

Web analytics measures audiences. GA4 is good at it: sessions, users, engagement time, traffic sources at the channel level, which pages get read and which get abandoned. If you want to know whether your traffic is growing, whether a page holds attention, or which channel sends the most visitors, it answers that competently and for free.

It also handles scale well. Aggregate numbers get more reliable as volume rises, which is why the tool feels sharper for a publisher with a million sessions than for a service business with four thousand.

The unit problem

The catch is what GA4 counts. Its natural unit is the session, and sessions are anonymous by design. You can configure a conversion event when someone hits a thank-you page, and that is genuinely worth doing, but the result is still a count. Twelve conversions from organic search. Three from email.

A count is enough when you are optimising a funnel with thousands of entrants. It is not enough when your month produced nine enquiries and you need to know which content was in the room for each of them. At small-business volumes, the question stops being “what percentage converted” and becomes “who enquired, and what did they read first?”

Every content library has two kinds of page. There is the one that pulls traffic: broad topic, good headline, shared occasionally, healthy view count. And there is the one that quietly turns up in the path just before people enquire: narrower, less impressive, often something dull like a page explaining how your pricing works.

Ranked by views, the first page wins every month and gets more budget. Ranked by the enquiries it produced, the second one often wins instead. Most content plans are built on the first ranking because it is the one the tooling hands over by default.

Neither ranking is wrong. They answer different questions. The mistake is commissioning next quarter's content from the traffic report when what you actually want is more customers.

What content attribution adds

Content analytics for leads shows which pages and blog posts produce form enquiries, not merely which pages attract traffic. The difference is the record underneath: instead of counting anonymous sessions, it ties each enquiry to the named person who submitted it and the pages they read on the way.

That changes what you can ask. Not just “how many conversions came from organic” but “which three posts appear most often in the journeys of people who actually became customers.” This is what content attribution is for, and it sits alongside GA4 rather than replacing it.

The assist problem, and being honest about it

One page rarely does the whole job. Someone finds you through a comparison article, reads two service pages a week later, then enquires from the contact page. Which page gets the credit?

The honest answer is that a single-page credit is always a simplification. What helps is seeing the whole path rather than arguing about the split: the first thing that brought them in, the pages in the middle, and the form at the end. Once you can see the sequence, the crediting question matters much less, because you can just look at what the sequence keeps containing.

That is also the reason to be sceptical of any tool that offers a confident percentage breakdown of content influence. At nine enquiries a month, a percentage is decoration.

What to do with it

Three practical moves, in order of how quickly they pay.

First, find the pages that appear in enquiry journeys but get modest traffic. Those are usually underpromoted rather than underperforming, and they are the cheapest thing to fix: better internal links, a mention in the newsletter, some attention to the title.

Second, find the high-traffic pages that never appear in a single enquiry journey. Do not necessarily delete them. Ask whether they are attracting the wrong reader, or the right reader with no obvious next step.

Third, stop commissioning more of whatever has never once been in the room when someone enquired. That is the budget the whole exercise frees up.

Use both, for different jobs

Keep GA4. It is the right tool for audience size, traffic trends, and spotting the week something broke. Nothing here suggests turning it off, and you can see a fuller side-by-side on Lead Source vs Google Analytics.

Add lead-level content attribution when the question changes from “is our traffic growing” to “which of this writing is bringing customers.” Those are different questions, and the second one is the one that decides next quarter's content budget.

How Lead Source fits

Lead Source captures the source, the landing page and the full page journey on every form submission, then names the person who submitted it. That record is what makes it possible to rank content by enquiries instead of views.

It is one line of code and it works with whatever CMS you already run. It will not replace your analytics, and it is not trying to.