Tracking is the fourth pillar of the Website Growth System™ and the one that closes the loop. It turns reader actions into numbers attached to a URL, so the next week's work is chosen from evidence. Without it every optimisation decision is a guess, and the guess cannot be corrected because nothing measured it.
What Tracking means in the Website Growth System
Tracking in the Website Growth System is the measurement layer that answers two questions and refuses to be judged by anything else: which URL produced a customer, and at which step the readers are being lost. It is not a reporting function and not a dashboard for its own sake. It exists so the loop has a number to carry back to the first pillar.
This pillar is deliberately placed last in the causal chain and first in the implementation order. Everything built before measurement exists was built blind, and the point of the specification stating both orders is to stop that from happening by default.
The minimum measurement layer
The minimum measurement layer has three parts, and this specification states a minimum rather than a recommended stack because the failure being prevented is having none of it. Analytics records the actions, a tag manager keeps their configuration in one place, and the search console supplies the demand side that analytics cannot see.
- Google Analytics 4: key events configured for the real actions of each page type, tested in real time before any report is trusted.
- Google Tag Manager: all tracking managed centrally with a trigger per conversion action, so measurement is not edited by hand in the site's code.
- Google Search Console: impressions, click-through rate and position per URL and per query group, which is the only view of the queries that did not convert.
Naming conversion events, and verifying them before trusting them
Conversion events are named once, per page type, and then verified live before a single number from them is used in a decision. The naming part is easy and the verification part is the one that gets skipped, which is how a quarter of reporting can rest on an event that never fired. A missing event does not raise an error: it produces a zero that looks like a finding.
A workable event set for a service site distinguishes the actions that mean different things: a form submitted, a call started, a chat opened, and where a regional messaging channel is used, that channel separately. The distinction matters because a page can be excellent at starting chats and useless at producing forms, and a single merged event hides which one you just improved.
The three-column dashboard
The dashboard this pillar requires has three columns and fits on one screen, because a dashboard nobody reads weekly is not a measurement system. The three columns are visibility, journey and conversion, and they are placed side by side so that a page can be located in the chain rather than judged by one number.
| Column | Source | Question it answers |
|---|---|---|
| Visibility | Impressions and clicks from Google Search Console. | Are we being shown, and are people choosing us when we are? |
| Journey | Sessions and engaged sessions from Google Analytics 4. | Do the people who arrive stay long enough to be persuaded? |
| Conversion | Key events from Google Analytics 4. | Did anything actually happen, and on which URL? |
Read across a row and the diagnosis is usually obvious: high visibility with a low click-through rate is a title and description problem, a healthy journey with no conversions is a third-pillar problem, and low visibility on a correct page is a first-pillar problem.
The weekly review that turns numbers into a backlog
The weekly review is where Tracking stops being a report and becomes an operating cadence. Four steps, one week, and the output is a committed backlog rather than a discussion. The cadence is specified here in the same words as on the master specification page, because a pillar that describes its own rhythm differently from the framework it belongs to is already drifting.
| Step | Time box | What happens |
|---|---|---|
| 1. Read the dashboard | 30 minutes, start of week | Three questions in order: which pages have views but no key events, which pages gained impressions but hold a low click-through rate, and which pages hold traffic while leads stay flat. |
| 2. Commit a backlog by impact | 1 hour | Three to five items, not more. Each item carries the evidence from the data, the metric it should move, and one named owner. |
| 3. Ship | The rest of the week | Content, on-page, conversion path, internal links or technical work, in the order already committed. The order is not renegotiated mid-week. |
| 4. Log the change | End of week | What changed, on which URL, on which date. Without this log the following week cannot tell a result from a coincidence. |
Three questions drive the first step, and their order is the priority order: pages with views and no events, pages gaining impressions with a low click-through rate, and pages holding traffic while enquiries stay flat.
The metric for the Tracking pillar
The metric for the Tracking pillar is the share of enquiries that can be attributed to a URL and a query group. It is a measurement of the measurement, which sounds circular and is not: a site can have analytics installed and still be unable to say where last month's customers came from, and that inability is the thing this pillar is graded on.
Attribution here is expected to be imperfect. People research on one device and act on another, and some enquiries arrive by routes nothing on the site can see. The specification asks for the share that is attributable to be known and stated, not for a complete picture that does not exist.
How Tracking closes the loop back to Search Intent
Tracking closes the loop by handing a number back to the first pillar, and this is the arrow that makes the framework a loop rather than a list. The pages that received readers and produced nothing are evidence about the intent map: either they answer a stage the query did not ask for, or they own an intent that no one acts on.
That evidence changes next week's plan, which is the whole claim of the Website Growth System. Return to pillar one, Search Intent, and the map is revised with numbers instead of opinions. The loop has closed once.
Frequently asked questions about the Tracking pillar
These are the questions readers ask most often about the Tracking pillar of the Website Growth System. Each one is answered directly from the deposited specification, in a few sentences, so that the answer can be read, quoted and cited on its own without the rest of this page.
Which events does WGS configure first?
WGS configures three Google Analytics 4 key events first, form_submit, click_call and click_chat, through Google Tag Manager in the first week. They are the minimum needed to connect a page to a lead.
What is the Friday change log for?
The Friday change log records the exact URL changes, their deployment dates and the hypothesis behind each one. The next weekly loop can then attribute a change in the numbers to the change that caused it.
What happens if the Tracking pillar is skipped?
Without the Tracking pillar, nobody can tell which URLs produce leads, and optimization falls back on gut feeling. The loop never closes, so the next week's backlog has no evidence behind it.
How are the tracking triggers verified?
The Google Tag Manager triggers are verified in the GA4 Realtime report before the numbers are trusted. The Definition of Done counts tracking as complete only when the key events are active and verified this way.
How to set up and run Tracking in the Website Growth System
These steps turn reader actions into numbers attached to a URL, so next week's work is chosen from evidence and the share of attributable enquiries is known.
- Install the minimum measurement layerSet up Google Analytics 4, Google Tag Manager and Google Search Console, with one trigger per conversion action managed centrally in the tag manager.
- Name conversion events per page typeName events once for each page type, keeping a form submitted, a call started and a chat opened as separate events so one merged event does not hide results.
- Verify every event liveTest each key event in real time before any report is trusted, because a missing event raises no error and produces a zero that looks like a finding.
- Build the three-column dashboardPlace visibility, journey and conversion side by side on one screen, using Search Console for visibility and Google Analytics 4 for sessions and key events.
- Run the weekly reviewRead the dashboard for 30 minutes at the start of the week, then commit three to five backlog items by impact, each with evidence, a metric and one owner.
- Ship and log the changeShip the committed work in order without renegotiating mid-week, then log what changed, on which URL and on which date at the end of the week.
- Hand the numbers back to Search IntentTreat pages that received readers and produced nothing as evidence, and revise the intent map in pillar one, Search Intent, using those numbers.
FAQ about Tracking in the Website Growth System
Why do my reports show zero conversions on pages that clearly get enquiries?
A zero often means the conversion event never fired. A missing event raises no error, so it produces a zero that looks like a finding. In the Website Growth System, every key event is tested in real time before any report is trusted, so a broken trigger is caught before it shapes a decision.
What goes wrong when form, call and chat actions share one merged event?
A merged event hides which action you just improved. A page can be excellent at starting chats and useless at producing forms, and one combined number cannot show that difference. Keep a form submitted, a call started, a chat opened, and any regional messaging channel as separate events.
Is having analytics installed enough to know where customers came from?
No. A site can have analytics installed and still be unable to say where last month's customers came from. The Tracking pillar is graded on exactly that gap, measured as the share of enquiries that can be attributed to a URL and a query group.
What should I do when attribution misses some of the enquiries a site receives?
Accept that attribution is imperfect and state the share you can attribute. People research on one device and act on another, and some enquiries arrive by routes nothing on the site can see. The specification asks for the attributable share to be known and stated, with no demand for a complete picture.
What does each of the three tools in the minimum measurement layer do?
Google Analytics 4 records the actions as key events. Google Tag Manager keeps all tracking configuration in one place with a trigger per conversion action. Google Search Console supplies impressions, click-through rate and position per URL and query group, the only view of queries that did not convert.
How do I read a row of the three-column dashboard to find the problem?
Read across the row and the diagnosis is usually obvious. High visibility with a low click-through rate points to a title and description problem. A healthy journey with no conversions is a third-pillar problem. Low visibility on a correct page is a first-pillar problem.
How long does each step of the weekly review take?
Reading the dashboard takes 30 minutes at the start of the week. Committing the backlog by impact takes 1 hour. Shipping fills the rest of the week, and logging the change happens at the end of the week, recording what changed, on which URL and on which date.
How many items belong in the weekly backlog, and what must each one carry?
The weekly backlog holds three to five items, no more. Each item carries the evidence from the data, the metric it should move, and one named owner. The order is committed by impact and is not renegotiated mid-week, so shipping follows the plan already agreed.
Which two questions does tracking in the Website Growth System have to answer?
Tracking in the Website Growth System has to answer two questions: which URL produced a customer, and at which step the readers are being lost. Tracking is the fourth pillar and refuses to be judged by anything else, so every key event and the three-column dashboard exist to answer those two questions for next week's work.
How is Tracking in the Website Growth System different from a reporting dashboard?
Tracking in the Website Growth System is a measurement layer with a weekly operating cadence, never a reporting function or a dashboard for its own sake. Tracking exists so the loop has a number to carry back to Search Intent, and the weekly review turns the three-column dashboard into a committed backlog of three to five items.
Does a service website really need conversion tracking from the start?
Yes, a service website needs conversion tracking, because without it every optimisation decision is a guess that nothing can correct. In the Website Growth System, Tracking is placed first in the implementation order, since everything built before measurement exists was built blind. The minimum is verified named events and a three-column dashboard.
Where should I start with tracking for a service website?
Start tracking a service website with the minimum measurement layer: Google Analytics 4, Google Tag Manager and Google Search Console. Next, name conversion events once per page type and verify each one live in real time. Then build a three-column dashboard of visibility, journey and conversion, and review it every week.