Setting up the Meta pixel for conversion tracking
Without a properly configured pixel, Meta ads run nearly blind: the algorithm has no way to know who actually became a customer and optimises on guesswork. Here's the setup, step by step.
Installing the base code
Create a pixel under Data Sources in Meta Business Suite to get a unique ID. The base pixel code goes on every page of the site — usually in the head section — and records the fact of a visit even before specific events are configured.
The easiest way to install it is through Google Tag Manager: one GTM container lets you add and update tags without editing site code every time, especially useful when development access is limited or slow.
After installation, verify it fires using the Meta Pixel Helper browser extension — green means the pixel was found and is sending data, red means something is misconfigured.
Standard events: what to track
The minimum set for most sites: ViewContent, AddToCart, InitiateCheckout, and Purchase or Lead. Meta recognises these automatically and uses them to power automated bidding.
Configure events to fire on the specific action, not on a page load in general — for example, a Lead event should fire after a form successfully submits, not when the page with the form opens, or the statistics inflate and the algorithm learns from false data.
Don't tag actions as events if you don't genuinely consider them a valuable result. If a campaign is optimised toward an event weakly tied to a real sale, automated bidding starts bringing in traffic that doesn't convert to revenue.
Conversions API as insurance against blockers
A standard browser pixel loses a portion of data to ad blockers, browser restrictions, and user privacy settings — by various estimates, a meaningful share of events. Conversions API sends conversion data directly from the server, bypassing the browser, and partly compensates for that loss.
Setting up Conversions API takes a bit more technical work — usually through a site-level integration or ready-made solutions for popular CMS platforms and site builders — but for active ad budgets it pays off through more accurate data and, in turn, more effective optimisation.
Common problems and how to find them
Duplicate pixels are a frequent issue on sites rebuilt by several contractors: the same pixel gets installed twice, doubling event counts and skewing statistics. Check with the same Pixel Helper extension, which shows how many pixels fired on a page.
A mismatch between conversions reported in Meta and actual sales or leads signals some events aren't landing or are counted incorrectly. Reconcile these numbers every week or two rather than relying solely on the ad account's report.
A purchase event that fires on every visit to a 'thank you for your order' page, including when someone just refreshes it or returns to it later, inflates conversion statistics and distorts the real cost per sale.