GTM:METRICS/Modules

One place where the numbers agree

Which source produced which customer, cohort reporting, and the weekly number everyone quotes. Built so it still works after the team changes and the channels move.

First result One place the numbers agreeRuns Weeks 8 to 12Built in HubSpot, GA4, Semrush

What this actually is

The common failure is not a missing dashboard. It is three dashboards that disagree, so every meeting starts with an argument about whose number is right and ends before anyone decides anything. This module produces one set of figures that everybody quotes, and makes the disagreements visible rather than hidden.

What gets built

  • Source attribution that holds. Every record carries where it came from in a field nothing else overwrites, set at creation. Retrofitting this later is the single most expensive data job in go-to-market.
  • Cohort reporting. By month of entry rather than by month of close, because a channel that looks bad this quarter often just has a longer cycle.
  • Funnel by stage, by segment, by owner. Each view answering a question somebody actually has to act on. Views nobody acts on get deleted.
  • The weekly number. One figure, defined in writing, that the whole team quotes. Everything else supports it.
  • Organic and paid visibility. Where you appear, for what, and whether that is moving. Increasingly this means AI answers as well as search results.
  • An honesty layer. Every reported figure marked with how proven it is: verified against live data, running but unverified, or a gap where nothing measures it yet.

Why attribution is usually wrong. Not the model. The data underneath it. If source is set by whichever integration touched the record last, no attribution model will save you. Fix the field before arguing about first touch versus last touch.

What you keep

The dashboards, the definitions in writing, and the status map showing which numbers are verified and which are not. That last part is the one clients keep referring back to, because it tells them which figures they can take into a board meeting.

When this is not the right module

If the underlying data is not being captured yet, reporting on it produces confident nonsense. Lead sources and pipeline come first. Reporting is the last module for a reason, and anyone selling it as the first is selling you a dashboard rather than an answer.

Where this connects

WHERE THIS STARTS

You get the map first.

The first two weeks produce a status map of your own stack. Every piece named, colour coded by how proven it is, gaps included. You keep it whether or not we work together.