Setting up the Meta Pixel and Conversions API is the job that should be done before you start advertising, yet it is the one most often postponed. Every account that says "let's launch the ads first and set up tracking later" loses its first weeks of data, and the system spends budget before it can learn who converts. The Pixel is a small piece of code that reports what happens on your website to Meta; the Conversions API is a second channel that sends the same information directly from the server, without relying on the browser. In this article, we explain why you need both and walk through the setup step by step.
What does the Pixel do, and why isn't it enough alone?
The Pixel runs in the visitor's browser: it reports page views, add-to-carts and purchases to Meta. This lets you see sales in your ad reports, build lookalike audiences of buyers and retarget people who abandoned their carts. The problem: because of iOS privacy settings, ad blockers and browser restrictions, the Pixel can no longer see some of the events. Every missed sale both makes your report incomplete and slows down the system's learning.
The Conversions API closes this gap
The Conversions API (CAPI) sends the same events to Meta from your website's server. Because the server sends them, data loss drops even if the browser blocks tracking. Meta recommends using the Pixel and CAPI together; the same event arriving through both channels is deduplicated thanks to the event ID. In the accounts we set up, we see the number of reported conversions rise noticeably after adding CAPI; sales didn't increase, visibility did.
Step 1: Make an event plan
Before setup, decide which events you'll track. The standard set for e-commerce: PageView, ViewContent (product page), AddToCart, InitiateCheckout, Purchase. For a service business: PageView, Contact (form submission), Lead, WhatsApp click. Send every event using Meta's standard event names; custom names can't be used for campaign optimisation.
Step 2: Create the Pixel and add it to your site
In Events Manager inside Meta Business Suite, choose web as the data source and create a Pixel. How you add it depends on your platform. On WordPress and WooCommerce, the official Meta plugin sets up both the Pixel and CAPI in a few clicks. On Shopify, the Facebook & Instagram app does the same job. Turkish off-the-shelf e-commerce platforms such as İdeasoft and Ticimax have a Pixel field in the panel; CAPI support varies by platform, so check. On custom-built sites, the Pixel code goes in the header of every page and event codes are added to the relevant actions.
Step 3: Manage it with Google Tag Manager
If you'll use several tracking codes (Meta, Google Ads, Analytics), managing them all through Tag Manager is the cleanest long-term approach. Meta's Tag Manager template installs the Pixel; for CAPI, server-side Tag Manager or a platform integration is used. For small businesses a platform plugin is usually enough; custom development is only needed on high-volume sites or those with custom software.
Step 4: Connect the Conversions API
In Events Manager, select your Pixel and proceed through the "Set up Conversions API" step. Three paths are offered: partner integration (such as Shopify, WooCommerce, Tag Manager), Meta's gateway solution and manual developer setup. For most businesses, the first option is enough. During setup, don't forget to enable event matching parameters (email, phone, city); this information is sent hashed and improves match quality.
Step 5: Test, then test again
The test tool in Events Manager shows in real time whether the actions on your site are reaching Meta. Make a real purchase or form submission on the site and check that the event comes through both the browser and server channels and is deduplicated. Look at the event match quality score; if it's low, you're sending incomplete parameters. Skipping this step is the most common mistake.
Common mistakes
1. Firing the purchase event on the checkout page instead of the thank-you page. People who didn't complete payment also show up as customers.
2. Counting the same event twice. When a plugin and manual code run together, sales are doubled; keep a single source.
3. Not sending an event ID. Pixel and CAPI events can't be deduplicated, so reports get inflated.
4. Skipping domain verification. For Aggregated Event Measurement, you need to verify your domain in Business Suite.
5. Forgetting cookie consent integration. Under KVKK, a cookie notice and consent mechanism must be added to the site; tracking codes must work in line with it.
Once setup is complete
You can now optimise your campaigns for purchase or lead events, build lookalike audiences from buyers and retarget cart abandoners. We cover audience setup in detail in our target audience post, and profitability measurement in our ROAS guide.
Once tracking is set up correctly, it serves you for years; set up wrong, every report misleads. At FG Production we set up and test the Pixel, CAPI and Google conversion tracking before handover in our web design and e-commerce projects; for a tracking audit of your current site, write to us. Having ad management and web design together among our services is precisely to close these technical gaps.