Tracking capability
Track the leads your ad spend is supposed to buy.
If Google Ads cannot tell which clicks became calls, forms, and real leads, the account starts optimizing around noise. I build GA4 and conversion tracking so the account has a clean signal to learn from.
What gets measured
Measure the actions that actually look like leads.
Page views tell you someone arrived. They do not tell you whether the visit created demand. The useful tracking layer starts where buying intent shows up.
What I look for
The usual failures are small enough to miss and expensive enough to matter.
- GA4 exists, but the money actions are not wired.
- Google Ads is learning from page views, duplicate conversions, or junk imports.
- Form submissions work for the user but never reach the ad account.
- Phone clicks happen, especially on mobile, but nobody counts them.
- Paid, organic, referral, and direct traffic collapse into one muddy story.
- Consent settings are undocumented, inconsistent, or stricter than the business realizes.
- Nobody can explain which conversion Google Ads is actually optimizing toward.
Live self-proof
This page has to live under the same standard.
This page should not get a pass just because it talks about tracking. The same basic standard applies here: name the valuable actions, wire them, document what fires, and make the proof inspectable.
Page measurement. The page participates in the site-wide analytics layer.
Tracked CTA. The audit button carries an explicit event label.
Attribution context. First and last touch can travel with audit requests.
Conversion path. The contact form is the primary audit-request path.
Showcase metadata. The page declares the proof the showcase cluster inspects.
The event names are technical. The decisions are not.
| Signal | What it tells you | Why it matters |
|---|---|---|
| page_view | Which pages brought a visitor into the journey. | Useful context, but not enough to optimize against by itself. |
| cta_click | Which page section created contact intent. | Shows whether the offer and page structure are moving people toward action. |
| phone_click | Which visitors attempted to call from mobile or desktop. | Local services lose a lot of visible lead intent when phone clicks are not measured. |
| audit_request | Confirmed form-submit conversion. | The primary lead event. This is the kind of event Google Ads should learn from. |
| form_submit_error | Attempted leads that hit a form problem. | Separates low demand from a broken conversion path. |
How it is built
One tracking path is fragile. Two is safer.
The implementation uses two measurement paths. Browser-side events handle normal interaction tracking. A server-side backup handles the highest-value form conversion.
That gives the account useful behavioral data without making the most important lead event depend on one fragile browser request. The public page explains the pattern. The operating system underneath stays private.
Attribution
The first click and the final click answer different questions.
First touch answers "what originally brought this person in?" Last touch answers "what brought them back when they converted?"
Those are different questions. Keeping both makes reporting less sloppy, especially when paid search, organic, referrals, and direct visits all touch the same lead.
Want to know if your tracking is lying to you?
Free audit first. I will tell you whether your current tracking is trustworthy, what is missing, and which fixes matter before you spend another month optimizing against bad data.
Get a tracking audit