Service · The Rebuild

Conversion Tracking Setup

Track it once, track it right.

Conversion tracking setup means wiring Google Ads, the Meta Conversions API (CAPI), GA4 and call tracking so every real lead or sale reaches the ad platforms with the right value attached. I build it server-side, test every event end to end, and document it. It is for businesses that spend on ads every month and cannot prove the numbers are right.

By Forrest Adsit, founder of Adsit Digital. Updated .

Schedule a Call All Services
Conversion Events Live
Event Match Quality 8.4 / 10
Server-side · deduplicated · iOS-safe
  • 09:41:22 purchase $129.00 m 0.86
  • 09:41:14 add_to_cart — m 0.81
  • 09:40:58 purchase $58.50 m 0.84
  • 09:40:33 lead — m 0.79
CAPI + GA4 + GTM Server-side ↑ from 0.42

The honest version

Your tracking was set up once, probably through a native app or by someone who never verified it, and it's been quietly broken ever since.

Events come through with no value, the platform can't tell a real conversion from a bounce, and your ad algorithm is optimizing toward nothing.

  • 01

    "I think the pixel is firing but I have no idea if any of it's actually right."

  • 02

    "The native app integration looked plug-and-play and now nothing matches."

  • 03

    "Half my best leads call and I have zero idea which ad made them call."

The Approach

How I set up conversion tracking.

  1. Step 01

    Scope

    We confirm what needs to fire, on which platforms, and what counts as a real conversion for your business.

    EventsChannelsValue mapping
  2. Step 02

    Build

    I set up the server-side infrastructure, the events, and the deduplication so nothing double-counts.

    Meta CAPIGA4Server-side GTMCall tracking
  3. Step 03

    Verify

    I test every event end to end and confirm match quality and values are landing, not just that it 'looks fine.'

    Match qualityDeduplicationEnd-to-end test
  4. Step 04

    Hand off

    You get documentation of what's tracking and how, so it's not a black box you're afraid to touch.

    DocumentationEvent reference

What's Included

What gets built: Meta CAPI, Google Ads, GA4, calls.

  • Meta CAPI, done right

    Server-side, deduplicated, high event match quality, not the native-app version that silently breaks.

  • GA4 & Google Ads

    Conversion tracking set up so Google is optimizing on events that actually happened, with the right values attached.

  • Server-side GTM

    A server-side container so your tracking survives browser changes, ad blockers, and iOS.

  • Call & offline tracking

    Tie phone calls and offline conversions back to the ad that caused them. Huge for home services and local.

Scope and price for this work are set after the audit, once I've seen what's actually broken. See how the audit works.

What Success Looks Like

What changes after server-side tracking.

  • 01

    The platforms optimize on real events.

    Meta and Google start getting clean, valued conversions instead of guesses, and the algorithm has something to actually learn from.

  • 02

    Phone calls finally tie back to the ad.

    Your highest-value lead source stops being a black hole and starts feeding the same loop as your forms.

  • 03

    Your match quality stops embarrassing you.

    Server-side, deduplicated, with a high enough score that Meta has a real shot at finding you more buyers.

  • 04

    You can change the tracking without breaking it.

    Documented, owned, and yours. No more 'don't touch that' black box living in your tag manager.

From a real account: A window-tint contractor's Google leads read as 13 and Facebook read as zero until the tracking was rebuilt. See how I tied their Facebook and Google leads to Jobber revenue.

FAQ

Questions about conversion tracking setup.

Why does server-side matter?

Browser-side tracking gets blocked, dropped, and de-valued by iOS, ad blockers, and privacy changes. Server-side sends the event directly, so the platforms keep getting clean data to optimize on. It's the difference between guessing and knowing.

What is event match quality and why do you keep mentioning it?

It's Meta's score for how well your events can be matched to real people. Low match quality means Meta is half-blind when it optimizes. Getting it high is one of the biggest levers on ad performance, and most setups score badly without anyone noticing.

Can you fix the tracking I already have instead of starting over?

Existing tracking can usually be repaired rather than rebuilt. The audit tells us whether it's worth fixing what's there or starting clean. Either way the goal is the same: events that fire, deduplicate, and carry real values.

Do you track phone calls?

Phone calls are part of every conversion tracking setup I build, and they're one of the most overlooked things in the whole stack. If half your best leads call instead of filling out a form, you need to know which ad made them call. Most setups miss this entirely.

What is the Meta Conversions API, and do I still need the pixel?

The Meta Conversions API (CAPI) sends your conversion events to Meta from your server instead of from the visitor's browser. The browser pixel still runs, but it loses events to ad blockers, iOS privacy settings, and consent choices, so Meta sees only part of what happened. CAPI fills in the rest. The two have to be set up together: each event gets a shared ID so Meta can deduplicate it when both the pixel and the server send it. If the IDs are missing or mismatched, Meta double counts, and if the server event carries no customer data, the event match quality score drops and Meta optimizes on a fuzzy picture. So yes, you keep the pixel, and the real work is in making the server side carry the right data and line up with it.

Ready to see what's actually working?

Book a call. I'll walk through what you're running and where the numbers stop making sense. No strings attached.

Schedule a Call Explore Services