Setting up conversion tracking

Without conversion tracking, every metric except spend is a guess. The platforms can tell you how many people clicked, but only your own tracking can tell them how many of those clickers did the thing you wanted. This guide walks through it for the four big platforms.

What counts as a conversion?

A conversion is whatever you decide success looks like. The most common ones:

Purchase — someone bought something. Most valuable conversion type for e-commerce.
Lead form submit — someone gave you their email or phone. The default for service businesses.
Sign-up — someone created an account. Default for SaaS.
Phone call — they tapped to call from a mobile ad.
Add to cart / "started checkout" — secondary signals to optimize for.

You can — and should — track several. Optimize bidding for the most valuable one (usually purchase), but watch the upstream ones (add to cart, form starts) to diagnose drop-offs.

How conversion tracking actually works

Each platform gives you a "pixel" or "tag" — a tiny snippet of JavaScript. You install it on your site, it sets a cookie, and when a visitor performs a conversion event, your site fires a message back to the platform: "this user just converted." The platform matches that conversion to a click it sent earlier and credits your campaign.

Two ways to fire conversion events:

Page-load events — fire when a specific URL loads (e.g., your /thank-you page after a form submit). Easiest to set up.
Click events — fire when a button is clicked. Use when you don't have a thank-you page or want to track non-navigational actions.

Pixel + Conversion API

The most important upgrade in modern conversion tracking is sending events from your server, not just the browser. Browser events get blocked by ad blockers, iOS, and content-blocking extensions. Server-to-server "Conversion API" sends bypass that. We recommend doing both.

Step by step: Google Ads

1
Install Google Tag Manager (GTM) sitewide
Once GTM is on every page, you don't have to touch your site code again. Add it to your <head> following Google's instructions.
2
Create a conversion in Google Ads
Tools → Conversions → New. Pick "Website" and the action category (purchase, lead, sign-up, etc.). Assign a value if you can.
3
Add a Google Ads Conversion Tracking tag in GTM
Use the conversion ID Google gave you. Set the trigger to fire on the URL pattern (e.g., page path equals /thank-you) or on a button click.
4
Test with Google Tag Assistant
Submit a test form yourself. The tag should fire and show up in Google Ads under "Tag firings" within ~24 hours.

Step by step: Meta (Facebook + Instagram)

1
Create the Meta Pixel in Events Manager
business.facebook.com → Events Manager → Connect a data source → Web. Name your pixel after your domain.
2
Install the base pixel sitewide
Either via GTM or directly in your <head>. Verify it's firing by visiting a page with the Meta Pixel Helper Chrome extension.
3
Add specific events
Use Meta's Event Setup Tool (point and click in the Events Manager UI) for the easy path. Or fire fbq('track', 'Lead') manually in your code where the conversion happens.
4
Add the Conversion API for backup
Server-side events from your backend. Critical for iOS users where the pixel is blocked. Meta's docs walk through it for major frameworks.

Step by step: Microsoft (Bing) Ads

1
Create a UET tag (Universal Event Tracking)
Microsoft Advertising → Tools → Conversion Tracking → UET tag. Name it, copy the snippet.
2
Install via GTM or directly in <head>
Same as Google — sitewide. UET works similarly to gtag.
3
Define a conversion goal
Tools → Conversion Tracking → Conversion goals. Set the URL or event name that should count.

Step by step: Nextdoor Ads

Nextdoor's conversion tracking is offered through their Ads Manager. Once your account is approved, you'll find the pixel under Account Settings → Tracking. Install sitewide and define conversions in the Ads Manager.

One pixel to rule them all? (Almost.)

Use Google Tag Manager as your single integration point. Install GTM once on your site; then add the Google Ads, Meta, Microsoft, and any other tags as "tags" inside GTM. You can publish, version, and roll back without redeploying your site. This is how every modern marketing team manages it.

What about CGMIMM Ads?

CGMIMM Ads' conversion tracking is configured through the CGMIMM admin. SEM by CGMIMM exposes campaign metrics natively, so you don't need a separate pixel — but for a unified view across all platforms in your own analytics, you can still install a CGMIMM pixel via GTM.

How SEM by CGMIMM uses your conversion data

Each platform reports conversion data back via their API. SEM pulls those numbers (along with conversion value, when available) and shows you the rolled-up CPA and ROAS on the campaigns page. If conversions look way off compared to what you see in your e-commerce backend, your tracking is broken — go fix the pixels first.

Common tracking failures (and how to spot them)

Conversions not showing up at all. Pixel isn't installed or trigger isn't firing. Use each platform's tag tester / debug mode.
Way more conversions than orders. The trigger is firing on every page load, not just the thank-you page. Tighten the URL match.
Way fewer conversions than orders. Pixel is being blocked (ad blockers / iOS). Add server-side Conversion API.
Conversions counted twice. Both GTM and a hard-coded snippet are firing. Pick one.