Tracking

Conversion Tracking

In short

Conversion tracking records which users complete a desired action after clicking an ad – such as submitting a form, booking a call or buying.

Also known as: conversion measurement

Conversion tracking measures which visitors complete a defined goal after interacting with an ad – for example submitting a form, booking a meeting or making a purchase. Without conversion tracking you know what your campaigns cost, but not what they deliver.

How conversion tracking works

Every conversion tracking setup has three parts:

  1. Capture the source: When someone clicks an ad, click IDs like gclid or fbclid and UTM parameters are added to the URL and stored on the website.
  2. Detect the conversion: A tracking pixel or script registers the goal action, such as a form submission.
  3. Report back: The conversion is attributed to the campaign and sent to the ad platform – either through the browser (client-side tracking) or directly server to server via a Conversion API.

Example

A Google Ads campaign gets 1,000 clicks. 40 visitors fill out the contact form, and 6 of them become customers. Without tracking you only see 1,000 clicks and $3,000 in spend. With conversion tracking you see 40 leads ($75 cost per lead) – and if closed deals are reported back too, 6 customers at $500 acquisition cost each.

Conversion tracking for lead generation

In lead generation, the form fill is only the beginning. Whether a lead was worth anything shows up days or weeks later in the CRM. If you only track form submissions, you train the algorithm to bring in as many leads as possible – not good ones. That's why it pays to send offline conversions like won deals or payments back to the ad platforms.

LeadMetrics captures sessions and their traffic source with a single script and detects form leads automatically (lead tracking). Deals from HubSpot or Close and payments from Stripe, CopeCart or Digistore24 are matched to the original lead and sent to Meta, Google Ads, TikTok and LinkedIn via the Conversion API.

Common mistakes

  • Counting clicks or page views: Treating a thank-you page as the conversion leads to double counts on reloads.
  • Relying on the pixel alone: Ad blockers and declined cookies mean part of your conversions go missing.
  • Double counting: If you run pixel and Conversion API in parallel, you need event deduplication.
  • No conversion values: Without a value, the platform can't tell a $50 lead from a $5,000 lead.

Read more in our article from CRM lead to real conversion.

Ready for better tracking?

Try LeadMetrics free for 10 days and see which campaigns actually drive revenue.
Start a 10 day trial

Frequently asked questions

Ad platforms only count what their pixel or API sees. Ad blockers, declined cookies and deals that close later in the CRM are missing there. Your CRM knows the real leads and deals, but often not the campaign behind them.

Guides on this topic

Tracking7 min read

Campaign Tracking with UTMs and Click IDs: Setup Guide

Set up clean campaign tracking: a UTM naming convention, dynamic parameters in Meta and Google Ads, click IDs, common mistakes and how to test it all.

Read guide

Articles on this topic

Related terms

All terms

Server-Side Tracking

Server-side tracking sends tracking data to ad and analytics platforms from a server instead of the browser – more robust and under your control.

Conversion API · CAPI

A Conversion API (CAPI) is an interface that sends conversions directly from server to server to ad platforms like Meta or Google, without the browser.

Attribution · Assigning conversions to marketing channels

Attribution assigns leads, purchases and revenue to the channels, campaigns and ads that drove them – the basis for every budget decision you make.

Offline Conversions · Reporting deals that happen off your website back to ad platforms

Offline conversions are conversions that don’t happen on your website – like a closed deal in your CRM – and are sent back to ad platforms like Meta.

Conversion Rate

Conversion rate is the percentage of visitors or leads who complete a desired action, such as submitting a form or making a purchase.

Client-Side Tracking

Client-side tracking captures user actions with JavaScript directly in the browser and sends them from there to analytics and ad platforms.