---
title: "Measuring ABM SEO by Segment"
description: "Report organic leads and SQLs per segment: one page-to-segment sheet, a Search Console filter per cluster, four CRM fields and a monthly readout you can trust."
canonical_url: https://abm-seo.com/seo/measuring-by-segment/
last_updated: 2026-10-31
chapter: 12 of 14
---

# Measuring ABM SEO by Segment

Search Console knows pages and your CRM knows leads, but neither knows segments. Join them with one sheet and report leads and SQLs per segment every month.

**Key takeaways.** For: SEO leads who have to report ABM SEO results. Walk away with: a monthly report of clicks, leads and SQLs per segment, compared with the forecast.

- Search Console knows pages, the CRM knows leads. The join between them is one sheet that gives every page a segment.
- Four fields on every lead record carry the segment from the first visit to the SQL.
- Check attribution before you trust a number: at one client, 10 to 15 organic leads a month were counted as direct.
- Read the funnel per stage. A falling SQL rate can sit entirely after sales accepts the lead.

The [forecast](https://abm-seo.com/cmo/mql-prediction-model/) gives you leads per segment before you publish. This chapter is how you get the actuals to compare it with. Without them, the [quarterly review](https://abm-seo.com/cmo/forecast-vs-actuals/) has nothing to show and the forecast that won the budget quietly disappears.

The problem is a missing join. Search Console reports pages and queries. The CRM reports leads and deals. Neither knows which segment a page or a lead belongs to.

## The join: a page-to-segment sheet

Every page in a cluster belongs to one segment. Every lead has a first page it landed on. Put those two facts in one sheet and you can report anything per segment. An illustration, with made-up paths:

| Path                                             | Segment      | Stage         | Live since |
| ------------------------------------------------ | ------------ | ------------- | ---------- |
| /construction/invoice-financing/                 | Construction | Decision      | 2026-03    |
| /construction/borrowing-without-annual-accounts/ | Construction | Consideration | 2026-05    |
| /compare/us-vs-competitor-a/                     | All segments | Decision      | 2025-10    |

Keep the path without the domain, the query string or the trailing variations, so it matches what the CRM stores. Pages that serve every segment, such as comparison pages, get "All segments" and their own line in the report. Don't force them into one.

Done when every URL in every cluster has a row. This sheet is the whole infrastructure. The rest reads from it.

## Search Console: one filter per segment

In the Performance report, add a page filter, choose Custom (regex), and match the segment's paths. If the segment name is in the URL, the filter is short. An illustration:

```
/construction/|contractor
```

If it isn't, paste the paths from the sheet as one pattern separated by `|`. Save the comparison or pull it through the API every month, so the numbers come from the same filter each time.

Split brand from non-brand queries before you read a segment. Brand searches land on the homepage and a few product pages, and they hide whether the segment pages are earning anything on their own.

## The CRM: four fields on every lead

**Ask your CRM owner:** You need: the four fields on every lead.

> Hi \[name], I'd like to report our organic results per customer segment, and I think the CRM can almost do it already. Could you check four things on our lead records: is the first page seen filled in, is the original source filled in, could we add a Segment field that fills itself from a list of pages I'll give you (not picked by hand), and do we record the date a record becomes a lead, a sales-accepted lead and an SQL? If any of these are missing, I'd love 15 minutes to work out the simplest way to add them.

1. **First page seen.** The path of the first page the visitor landed on, matching the sheet. HubSpot fills this by default.
2. **Original source.** Organic search, paid, direct, referral. Also a default in HubSpot.
3. **Segment.** A custom field, filled from the sheet by a workflow or at import. Not chosen by a sales rep from a dropdown.
4. **Stage dates.** The dates the record became a lead, a sales-accepted lead and an SQL. Without dates you can't tell which month's content produced which month's SQLs.

**Ask your developer:** You need: the first page stored on every form submission (only if your CRM doesn't do it already).

> Hi \[name], small request: when someone fills in a form on the site, could we store the first page they landed on, without the domain or query string, in a hidden field that goes to the CRM with the lead? HubSpot does this by itself, but our forms don't pass it through yet. It lets me see which pages bring in which leads. Happy to test it with you once it's in.

At the business lender I work with, the leads export from the CRM goes into a sheet with one row per month and landing page: month, path, organic leads. That shape is enough. It rolls up to segments through the page sheet, and it is the same shape the forecast uses.

## Check attribution before you trust a number

Two things went wrong at that client, and both would have made the segment numbers look worse than they were. The figures in this chapter come from that engagement, anonymised, and illustrate the method; they are not a benchmark for your site.

**Prompt for your AI:** Your AI can find the misfiled leads in a minute.

> I've attached two files: a leads export with original source and first page seen, and a sheet that gives every page a segment. Find organic leads that were recorded as direct.
>
> 1\. Take leads whose source is direct and whose first page is in the page sheet. Those are almost always organic.
>
> 2\. Count them per month and per segment for the last six months.
>
> 3\. Show the corrected organic total per segment next to the recorded one.
>
> Give me a table and the ten clearest examples. Use only these two files. If the first page is missing for many leads, tell me the share that is missing before you count anything.

**Organic leads counted as direct.** I estimated that 10 to 15 organic leads a month were recorded as direct. Check it by comparing the first page seen with the source: a lead whose first page is a cluster article and whose source is direct is almost always organic.

**An empty value field.** The pipeline value field in the CRM was empty, at that client and at a second one. Until it is filled, report leads and SQLs per segment, not euros. A revenue number built on an empty field is worse than no number, because people trust it.

**Decision:** Can you answer: how many organic SQLs did the construction segment produce last month?

- **If yes:** Build the monthly readout below.
- **If no:** Fix the four fields and the page sheet first. A readout without them is guesswork.

## The monthly readout

One table, one row per segment:

| Segment | Clicks | Leads | SQLs | SQL rate | Forecast leads | Gap |
| ------- | ------ | ----- | ---- | -------- | -------------- | --- |

Then ask the question the [quarterly review](https://abm-seo.com/cmo/forecast-vs-actuals/) asks: is the gap in traffic or in conversion? Traffic gaps point to rankings, links and authority. Conversion gaps point to the page, the offer and the intent.

Read the funnel one stage at a time before you blame the content. At the lender, the organic SQL rate fell from 23.7% in the last quarter of 2025 to 15.0% in the third quarter of 2026. Over the same period, lead to sales-accepted held at 45 to 47%, and sales-accepted to SQL fell from 51% to 36%. The leads were as good as before; the drop sat after sales had accepted them. The first step is a conversation with sales about lost reasons and credit criteria, not a content rewrite.

> Before you rewrite a page for a falling SQL rate, find the stage where the rate fell.

The segment view also shows which pages to build next. At the same client, a 37-page sector set brought 6 leads and no SQLs from June to mid-September, while one comparison page brought 16 leads and 6 SQLs from June to late October. Without the page sheet, both would have been "organic leads".

## Small numbers

Most segments produce single-digit leads a month for the first quarters. Treat 0 to 3 conversions as a direction, not a result. A page with real traffic and a consistent gap is a signal; one lead more or less is noise. Report three-month rolling totals per segment next to the monthly figure.

## What this doesn't do

**It doesn't measure accounts that never fill in a form.** Visits from target accounts who read and leave are invisible here. Account-identification tools show some of them; this setup only counts what reaches the CRM.

**It doesn't fix the CRM.** If sales doesn't record stage dates or lost reasons, the SQL rate can't be read per stage. That is a sales process fix, and it needs the sales lead in the room.

**It doesn't replace the forecast.** Actuals without a forecast tell you what happened, not whether it was enough. Build the [forecast spreadsheet](https://abm-seo.com/seo/mql-forecasting-mechanics/) next to it.

## Where to start

Export every URL in your clusters and give each one a segment in a sheet. Then filter your CRM's last three months of leads by first page seen and count them per segment. If that count is far from what your team believes, start with attribution.
