A conversion on a Facebook ad is any specific action a person takes after seeing or clicking your ad that you’ve defined as valuable to your business. That could be a purchase, a form submission, an app install, adding a product to a cart, or dozens of other actions. Meta tracks these actions through code on your website or server and reports them back in your ad dashboard so you can see which ads are actually driving results, not just clicks.
What Counts as a Conversion
Meta doesn’t decide what a conversion is for you. You choose which actions matter based on your business goals, then tell Meta to track and optimize for them. A conversion for an online store might be a completed purchase. For a service business, it might be a submitted contact form. For a SaaS company, it could be a free trial signup.
Meta organizes trackable actions into three categories:
- Standard events are predefined actions that Meta already understands. There are at least 17 of them, including Purchase, Add to Cart, Initiate Checkout, Complete Registration, Lead, Search, and Contact. Because these are built into Meta’s system, the ad platform knows how to optimize for them automatically.
- Custom events are actions you define yourself when none of the standard events fit. You name them whatever you want and send the data to Meta using code. The tradeoff is that Meta doesn’t inherently understand what these events mean, so optimization may be less precise initially.
- Custom conversions let you create conversion rules based on URL patterns or parameters. For example, if everyone who submits your quote request lands on a page ending in “/thank-you,” you can tell Meta to count any visit to that URL as a conversion. This approach doesn’t require additional code beyond the basic tracking setup.
Most advertisers start with standard events because they’re the easiest to set up and give Meta the clearest signal about what you want.
How Meta Tracks Conversions
Meta uses two main tools to detect when someone converts after interacting with your ad: the Meta Pixel and the Conversions API.
The Meta Pixel is a small snippet of JavaScript code you place on your website. When a visitor takes an action, like completing a purchase, the pixel fires and sends that event data from the visitor’s browser to Meta. This is called client-side tracking. It works well in most situations, but it has blind spots. Ad blockers can prevent the pixel from firing. Browser privacy settings, slow page loads, and connectivity issues can all cause missed conversions.
The Conversions API (often called CAPI) works differently. Instead of relying on the visitor’s browser, it sends event data directly from your server to Meta. This makes it resistant to ad blockers and browser-related tracking failures. It can also track actions that happen outside a browser session entirely, like in-store purchases, subscription renewals, or post-purchase events. When a user inputs information like their name, email, or phone number on your site, CAPI can use those identifiers to match the conversion back to the person who saw or clicked your ad.
Many advertisers run both the Pixel and CAPI together. Meta deduplicates the data so conversions aren’t counted twice, and the combination fills in gaps that either tool would miss on its own.
Attribution: When a Conversion Gets Credited
Not every conversion happens the moment someone clicks your ad. A person might click on Monday, browse your site, leave, and come back to buy on Thursday. Meta’s attribution settings determine how long after a click or view a conversion still gets credited to your ad.
The default attribution window is 7-day click and 1-day view. That means Meta will count a conversion if it happens within seven days of someone clicking your ad, or within one day of someone viewing your ad without clicking. Both the optimization algorithm and your reporting reflect this window.
You can adjust these settings. Click-through attribution can be set to either 1 day or 7 days. View-through attribution can be set to 1 day or turned off entirely. There’s also an engaged-view option (for video ads where someone watched for a meaningful duration) that can be set to 1 day or off, though it requires view-through to also be set to 1 day.
Choosing a shorter window gives you a more conservative count, only capturing people who converted quickly. A longer window captures more conversions but includes people whose purchase decision may have been influenced by other factors between seeing your ad and converting.
How Privacy Changes Affect Conversion Data
Apple’s App Tracking Transparency framework, introduced with iOS 14.5, lets iPhone users opt out of cross-app tracking. When someone opts out, Meta has limited ability to track their actions after they leave the Facebook or Instagram app. This means some conversions that actually happened won’t show up in your reports.
Meta responded with Aggregated Event Measurement, a protocol that limits the number of conversion events you can prioritize per domain and uses statistical modeling to estimate conversions it can’t directly observe. In practice, this means your reported conversion numbers may be modeled estimates rather than exact counts, especially for iOS users. Events from users without an available advertising identifier may not be shared or attributed at all.
This doesn’t mean conversion tracking is broken. It means the numbers in your dashboard are less precise than they were before 2021, particularly for campaigns targeting mobile users. Running the Conversions API alongside the Pixel helps recover some of that lost signal.
Conversions vs. Other Ad Metrics
It’s worth understanding where conversions fit among the other numbers in your ad reports. Impressions tell you how many times your ad was shown. Reach tells you how many unique people saw it. Clicks tell you how many people tapped on it. None of those tell you whether anyone did the thing you actually wanted them to do.
Conversions fill that gap. They measure outcomes, not just engagement. When you set up a campaign with a “conversions” objective (Meta calls this “Sales” or “Leads” depending on the goal), Meta’s algorithm specifically targets people it predicts are most likely to take your chosen action, not just people likely to click. This is why properly configured conversion tracking often produces dramatically better results than optimizing for traffic or engagement.
Cost per conversion, sometimes called cost per action or cost per result, is the metric most advertisers care about most. It tells you exactly how much you’re spending to generate each purchase, lead, or signup. You calculate it by dividing your total ad spend by the number of conversions. If you spent $500 and got 25 purchases, your cost per conversion is $20.
Setting Up Conversion Tracking
To track conversions, you need at least the Meta Pixel installed on your website. Most website platforms, including Shopify, WordPress, Squarespace, and Wix, have built-in integrations that let you add your Pixel ID without editing code directly. Once the base pixel is installed, you add event code to the specific pages or buttons where conversions happen. A “Purchase” event typically fires on the order confirmation page. A “Lead” event fires when someone submits a form.
If you’re using a major e-commerce platform, the standard events are often configured automatically through the platform’s Meta integration. For custom setups, Meta’s Events Manager walks you through adding event code manually or using a point-and-click tool that lets you select buttons and pages on your site without writing code.
After setup, use the “Test Events” tool in Events Manager to verify that conversions are firing correctly. Visit your own site, complete the action you’re tracking, and confirm the event appears in the testing dashboard. Getting this right before launching a campaign saves you from spending money on ads that can’t measure their own performance.