Track lead quality in Google Analytics, not just lead count

A form fill is one lead to Google Analytics, whether it was a ready buyer or someone who typed gibberish to see what happens. The count tells you how many people filled in the form. It says nothing about which of them you wanted.

That gap can reverse your decisions. The ad that sends the most junk gets the biggest lead count. It looks like your best ad. You give it more money.

Why does lead count mislead?#

A count treats every lead as equal. Your own work does not.

You know which inquiries you call first and which you never answer. One lead is a good fit with a real budget and a date. Another is outside your service area, or has a project of a size you do not take. Google Analytics sees two generate_lead events and adds them up.

Picture two ads. A broad one brings a crowd, and a crowd fills in a lot of forms. A narrow one brings fewer people, and more of them are right for you. By count, the broad ad wins. By the calls you actually return, it may lose.

The fix is to let each lead say how good it is, inside Google Analytics.

How can a lead carry its quality into Google Analytics?#

The idea works for any form. When a lead is counted, send two extra details with the event:

1. A priority, such as hot, warm, or cold. This is the one you will group by.
2. A score, such as 0 to 100. This is the one you will average.

Google Analytics lets you attach extra details, called parameters, to an event. Out of the box it ignores the ones it does not know. A custom dimension teaches it to keep one. After that, a detail can sit next to anything else in your reports.

This needs a form that knows how good a lead is when it ends. A plain contact form does not score anything. If yours does not, you can still do a cruder version. Send one detail that you can fill in yourself, such as "budget given" or "in service area," from a field the visitor answered. The idea is the same: something about the lead's quality has to travel with the event.

How do you set it up in Google Analytics?#

You do two things in Google Analytics, once.

First, register each detail as a custom dimension. In Google Analytics, open Admin, then Custom definitions under Data display. On the Custom dimensions tab, click Create custom dimensions. Give it a name, set Scope to Event, and type the event parameter's name exactly as the form sends it. Save. Google's help is at Custom dimensions and metrics, and the steps for an event-scoped one are at Create event-scoped custom dimensions.

Two things to know before you start:

• Data fills in from the day you create the dimension, not before. Google says to allow 24 to 48 hours before it is usable in reports. So create it before your leads arrive, not after.
• Names must match exactly. If your form sends lead_band and you type Lead_Band, nothing shows up.

Second, mark your lead event as a key event if you have not. Google Analytics only counts it as a conversion after you do. In Admin, under Data display, click Events, find the event, and click its star.

How do you compare channels by lead quality?#

Once data has arrived, the clearest view is an exploration. Open Explore and start a Free form exploration. Add your priority dimension and drag it to Rows. Add a source or campaign dimension beside it, and add the key event count as a metric. You now see, for each channel, how many leads were hot, how many were warm, and how many were cold.

Read the table for ratios, not totals. A channel that brought 10 leads, 6 of them hot, is doing better than one that brought 100 leads and 4 hot ones. Do not judge a small number. Give each channel enough leads before you move money based on it.

Why is the priority better than the score for comparing?#

The score runs from 0 to 100, which gives you a table with a hundred possible values. The priority groups those into a few rows you can read.

Use the priority to compare channels. Use the score for an average per channel, which is a good second check. If a channel's share of hot leads and its average score point in opposite directions, you have a small sample or a messy ad, and it is worth looking at the leads themselves.

How does Qualiform send this?#

Qualiform scores each finished conversation with code, not with the AI's opinion, and routes it by your rules. Then it sends Google Analytics a generate_lead event from its server, with these details:

• lead_score, from 0 to 100,
• lead_band, the priority, such as hot,
• lead_tier, the routing rule the lead landed on,
• the form's name and ID, and
• a currency of USD and a value of 0.

Register lead_score, lead_band, and lead_tier as custom dimensions, and you can do everything above. Qualiform never sends the visitor's answers, name, email address, phone number, or anything they typed. The setup guide has every click.

Two things are worth knowing about the browser tag. If you connect both of Qualiform's Google Analytics options on the same property, the lead is counted once and credited to the ad or page that brought the visitor. That credit is what lets you compare channels at all. And the browser tag does not send the score. The browser is the visitor's own, and Qualiform never shows a visitor their score. The score and the priority come through the server side.

The limits are real. A visitor who blocks Google Analytics is still counted through the server, but as its own user, so that lead cannot be credited to an ad. A conversation the visitor leaves halfway sends nothing to Google Analytics, though Qualiform still saves the lead. And a custom dimension only fills in from the day you create it, so older leads in your property carry no score.

Count the leads you wanted, not only the leads you got. It takes one setup, and from then on Google Analytics can answer which ad brings the leads worth a call.