Measurement guide 07
A monthly report should say what changed, how reliable the numbers are, and what you will do next. Use a short scorecard from search appearances to completed jobs, a few notes, and an action list. Show where each number came from and which dates it covers. Allow for seasons, tracking changes, and small numbers.
← All measurement and analytics guidanceClose the month
Check sources
Compare the scorecard
Explain the change
Assign next steps
Why this matters
A stack of screenshots can show activity without showing whether marketing helped. More traffic can come with fewer good requests. Steady lead numbers can hide a broken mobile form offset by repeat customers. A useful report keeps each step visible, so the owner can see whether the bottleneck is visibility, the website, follow-up, or capacity.
A month is a meeting rhythm, not a promise that every result is in. Google notes that Analytics processing can take 24–48 hours, and some credit can shift later. Customers may take longer still to decide. Close the month on a set date, note when you pulled the numbers, and label recent results as provisional.
Responsible practices
Make columns for metric, source, this month, comparison month, change in count, change in percent, and a short note. Useful rows: search impressions and clicks (Search Console), website sessions (GA4), inquiries received (your inbox and call log), qualified inquiries, and completed jobs (your records). Mark missing values as missing; a blank should never look like zero.
Compare the closed month with the month before and, if you have it, the same month last year. Check working days, holidays, and seasonal demand. Note site changes, campaign launches, consent changes, and tracking changes beside the affected numbers. A new tracking setup is a break in the data, not growth.
Hypothetical example: inquiries rise from 40 to 50, while qualified inquiries rise from 24 to 25. Inquiries grew 25%; qualified inquiries grew about 4%. The qualified share fell from 60% to 50%, a drop of 10 percentage points. Look into the extra poor-fit requests before celebrating the bigger total.
If search clicks are steady but sessions fall, check tracking and page availability first. If inquiries fall, test forms and phones. If qualified inquiries hold but bookings fall, look at response times and availability. These are starting points to check, not conclusions. Record withheld GA4 rows as withheld, not zero.
If you want a live dashboard, Data Studio (formerly Looker Studio) is Google's free reporting tool and can pull in GA4 and Search Console data. Build only the rows in your scorecard. A dashboard does not replace your lead records, the notes, or the action list.
For each decision, write what you saw, the likely reason, the action, the owner, the due date, and how you will know it worked. Hypothetical example: out-of-area requests rose, so review the service-area wording and compare next month. At the next meeting, mark each action done, still open, or dropped.
Monthly reporting routine
Pick a monthly review date a few days after month-end, and write the period and pull date at the top.
Choose a short list of scorecard rows and give each one source and one owner.
Pull the same reports each month with the same filters and time zone.
Check for tracking outages, setting changes, and unreviewed inquiries before calculating changes.
Fill in this month, last month, and the same month last year, showing counts beside percentages.
Write three notes: the biggest change, the most likely reason, and the biggest remaining unknown.
Agree a few actions with the owner, carry their status into next month, and save a copy of the report.
Avoid these failures
Collection, attribution, qualification, bookings, costs, and revenue depend on technical, customer, operational, and platform factors outside any provider's control. Results are not guaranteed.
Questions business owners ask
As few as cover the decisions you need to make. A short scorecard from search appearances through completed jobs is a practical start. Keep detailed tables for digging into problems, not as headlines.
Pick a consistent date after the tools have processed data and staff have updated inquiry statuses, often a few days into the month. Label recent outcomes provisional and update them later.
Both, when the history is comparable. Last month shows recent change; last year adds seasonal context. Note big differences in opening days, campaigns, or tracking. Neither proves marketing caused the result.
Show the actual counts, review individual reasons privately, and use a rolling three- or six-month view for trends. Avoid big conclusions from one extra inquiry or job.
Primary guidance
Turn measurement into a working routine