Transcript

Unqualified Leads – Episode 016 Highlights

Hosts: Harry Hughes & Dan

Topic: Why server-side tracking and offline conversion signals are now baseline requirements for paid media performance, how browser/pixel-only tracking leaves large gaps, and how to audit and improve event quality across Meta and Google, plus how to push deeper-funnel CRM outcomes back into platforms for better optimisation.

The Core Argument

Tracking Quality Is a Growth Lever (Not a “Nice to Have”)

• Most ad accounts do not have server-side tracking set up correctly

• Even when it exists, it’s often:

  
  

  • implemented for only a few events

  • sending poor match quality

  • not monitored inside platform tools (e.g., Meta Events Manager)

The consequence is not just “messy reporting”, it’s worse optimisation.

Why This Matters

Attribution Isn’t Everything, But Missing Data Hurts Performance

Harry frames attribution as a diagnostic tool (especially in B2B), but still argues:

• You don’t want to miss conversions

• You don’t want to under-feed platforms the conversion data needed to learn

• Pixel-only tracking creates a negative flywheel:

  
  

  • fewer tracked conversions → less algorithmic learning

  • less learning → worse targeting & optimisation

  • worse performance → higher spend to hit the same outcome

Agency operating principle: audit conversion tracking first, fix it early, then scale spend.

Common Friction

“Data Worries” Block Implementation (Even When It’s Safer)

Dan flags a recurring objection:

• Some clients resist server-to-server due to “data concerns”

• But the data passed is hashed, server-to-server, and secure

• In 2026, it’s “table stakes”:

  
  

  • Meta / Google / LinkedIn server-to-server tracking is non-negotiable

Dan’s point: if you’re paying to acquire customers, you should also pay attention to the system that makes that spend efficient.

The Context Shift

Why Browser Tracking Degraded (iOS14, Cookies, GDPR, Ad Blockers)

Dan explains the “why now”:

• iOS 14 / ATT reduced trackability dramatically (especially cross-device)

• Retargeting pools shrank overnight (e.g., 50k → 5k)

• ROAS efficiency dropped because platforms lost visibility across the journey

Then add:

• Safari / Firefox cookie restrictions

• GDPR/ePrivacy tightening

• Ad blockers

• Reduced reliability of identifiers like GCLIDs over time

Result: browser-only tracking still captures some data, but not close to the full picture.

Definition + Mechanism

Server-Side Tracking (CAPI) in Practical Terms

Harry’s explanation:

Server-side tracking = capturing conversion events on your server and sending them back to platforms (Meta/LinkedIn/Google) via Conversions API (CAPI).

What this helps with:

• bypassing cookie deletion

• bypassing ad blockers

• improving cross-device measurement

• increasing event accuracy and match rate

What gets sent: hashed identifiers and event metadata, e.g.

• hashed email / phone

• IP address

• event IDs / deduplication signals

• platform IDs (e.g., Meta click IDs)

• (and where relevant) Google click IDs

More matchable signals → better platform learning.

Implementation Paths

DIY vs Tooling (and Why Tools Often Win)

Two routes:

1. Custom build in codebase

   
   

   • possible, but debugging + correctness costs time

   • many dev teams haven’t implemented it repeatedly

   
   

2. Use a specialist tool

   
   

   • example mentioned: Stape

   • distributes server-side data to multiple ad platforms

   • faster to deploy, fewer errors, minimal cost

   • improves speed-to-market for performance gains

   
   

Other tools referenced:

• Zapier (for automation / templates)

• Segment (similar category)

Google-Specific Layer

Enhanced Conversions

Harry calls out an extra lever in Google Ads:

• In a Google Ads conversion action, you can enable Enhanced Conversions

• It captures user-provided form fields (B2B: name/email/phone; ecom can include address/postcode)

• Setup is typically via Google Tag Manager / data layer

• It’s now easier than it used to be (including automated field detection), but should be validated via GTM preview/debug

Purpose: increase match rate and conversion accuracy inside Google’s ecosystem.

The Big One for B2B Lead Gen

Offline Conversion Tracking (CRM → Ad Platforms)

Harry’s main argument for lead gen businesses:

Tracking only the initial form submit is insufficient.

You need to send down-funnel lifecycle events from your CRM back to platforms, such as:

• Lead becomes SQL

• Lead becomes Opportunity (proposal stage)

• Closed-won / Customer

Why:

• those events happen in the CRM, not on the website

• platforms can’t “see” them unless you import them

• optimisation should be driven by value, not just volume

  
  

Implementation options:

• Direct CRM integrations (example: HubSpot ↔ Meta/LinkedIn/Google)

• Or automation tools (e.g., Zapier) if a direct integration isn’t available

Bidding to Quality

Value-Based Bidding in Google (When Volume Allows)

Dan adds the next step:

• assign values to stages (example given)

  
  

  • MQL = £1,000

  • SQL = £4,000

  
  

• import those conversions into Google

• then bid toward the higher-value stage using value-based bidding (e.g., Target ROAS)

Key constraint:

• needs sufficient conversion volume (Dan mentions needing meaningful counts, not tiny datasets)

Dan’s broader point:

• bidding strategy changes traffic quality dramatically (max clicks → max conversions → TROAS is a meaningful shift)

  
  

Meta Auditing Tooling

Meta Events Manager: What to Check

Harry recommends regular inspection inside Meta Events Manager, especially during audits:

Key diagnostics:

• Deduplication status (server + browser matching properly)

• Match quality score (out of 10)

• Event freshness (how close to real-time events arrive; hourly common, multi-day is poor)

• Parameter coverage (email/phone/IP versions etc.) and suggested improvements

Red flags:

• server events far lower than browser events (or vice versa)

• double counting

• stale event delivery

Rule of thumb mentioned:

• Aim for high match quality (around ~8+ as a minimum target in many cases)

Regulated Categories

When Meta Restricts Optimisation Events (Finance/Medical/etc.)

Dan flags recent restriction changes:

• Some regulated categories can lose the ability to optimise toward standard lead events

• Workaround concept: use server-side custom events tied to meaningful steps (e.g., button clicks, journey milestones, thank-you page logic) that aren’t the explicit restricted “lead” event

Note: framed as a workaround requiring careful, creative implementation.

Harry adds this also applies to political advertising constraints.

Key Takeaways

• Server-side tracking is now baseline for efficient paid media

• Pixel-only/browser tracking leaves substantial conversion and match data on the table

• Enhanced Conversions (Google) improves signal quality from form submissions

• Offline conversions (CRM lifecycle stages) are essential for lead gen businesses

• You can optimise platforms to SQLs/opportunities/closed-won—not just form fills

• Meta Events Manager is a practical auditing tool for match quality, freshness, and dedupe

• In restricted verticals, server-side custom events can preserve optimisation signals