Facebook Pixel Guide 2026: Set Up, Verify, and Use the Meta Pixel

What You’ll Get

How the Facebook Pixel Works Setting Up the Meta Pixel Setting Up Standard Events Conversions API Setup

The Facebook Pixel (now officially called the Meta Pixel) is a small piece of JavaScript code that you install on your website. When visitors take actions — viewing a product, adding to cart, purchasing, signing up — the Pixel reports those events to Meta’s advertising platform.

Without the Pixel, Meta Ads is essentially blind: it can’t track which ads led to website actions, it can’t optimize campaigns for conversions, and you can’t build retargeting audiences based on website behavior.

With the Pixel properly installed, Meta can optimize your ads to find people most likely to convert, and you can retarget everyone who visited your site, viewed a product, or abandoned their cart.

How the Facebook Pixel Works

The Pixel operates in two modes:

Browser-side (JavaScript): The Pixel code loads in the user’s browser when they visit your page. It tracks page views and user interactions, then sends event data to Meta.

Server-side (Conversions API): Your server directly sends conversion data to Meta’s servers — bypassing browser-based tracking limitations like ad blockers, Safari’s ITP, and iOS 14+ privacy restrictions.

Why both matter: Browser-side pixel data is increasingly limited by privacy restrictions (iOS 14+ App Tracking Transparency reduced Meta’s ability to track iOS users by 30-50%). The Conversions API (CAPI) supplements browser data with server-side data that doesn’t rely on browser cookies.

Best practice in 2026: Implement both browser Pixel and Conversions API. This is called “redundant events” — events are sent via both methods and Meta deduplicates them. The result is more complete conversion data and better campaign optimization.

Setting Up the Meta Pixel

Step 1: Create the Pixel

Go to Meta Business Manager (business.facebook.com)
Navigate to Events Manager (in the left sidebar)
Click “Connect Data Sources” → “Web”
Select “Meta Pixel” → “Connect”
Name your pixel (use your brand name) and enter your website URL
Click “Create Pixel”

One pixel per website: You only need one Pixel per website. If you run multiple ad accounts for the same website, they can share one Pixel. Do not create multiple Pixels for the same site.

Step 2: Install the Pixel Base Code

The Pixel base code must be installed on every page of your website. It should be placed in the <head> section of your HTML, before the closing </head> tag.

Installation methods:

Via Meta’s partner integrations (easiest):

Shopify: Meta’s official Shopify channel app installs the Pixel automatically. Go to Shopify App Store → search “Meta” → install the official Meta channel.
WordPress (WooCommerce): Install the “Pixel Your Site” plugin or the official Meta Pixel for WordPress plugin.
Squarespace: Settings → Advanced → Code Injection → paste Pixel code in Header.
Wix: Settings → Tracking & Analytics → New Tool → Facebook Pixel.

Manual installation: Copy the base code from Events Manager and paste it into the <head> section of every page — either directly in the HTML or via Google Tag Manager.

Via Google Tag Manager (recommended for flexibility):

In GTM, create a new Tag → “Custom HTML”
Paste the Pixel base code
Set the trigger to “All Pages”
Publish the container

GTM is recommended because it allows you to manage all tracking codes in one place without modifying website code for each change.

Step 3: Verify the Pixel Is Firing

Use the Meta Pixel Helper Chrome extension:

Install from the Chrome Web Store
Visit your website
Click the Pixel Helper icon in your browser toolbar
It will show whether the Pixel is firing and which events it detected

What you want to see: “Pixel Found” with a green checkmark and the PageView event firing on every page.

What to investigate if Pixel Helper shows errors:

“Pixel Not Found” — the base code isn’t installed on this page
“Pixel Fired Multiple Times” — duplicate Pixel installations; remove duplicates
“Invalid Pixel ID” — wrong Pixel ID in the code; copy the correct ID from Events Manager

In Events Manager: After installing the Pixel, visit your website, then check Events Manager → Data Sources → your Pixel → Overview. You should see “Active” status and PageView events appearing.

Setting Up Standard Events

The Pixel base code tracks PageViews automatically. To track specific user actions (purchases, add to carts, leads), you need to add Standard Event codes.

Meta’s Standard Events:

Event	Code	When to fire
Purchase	`fbq('track', 'Purchase', {value: X, currency: 'USD'})`	Order confirmation page
Add to Cart	`fbq('track', 'AddToCart')`	When item is added to cart
Initiate Checkout	`fbq('track', 'InitiateCheckout')`	When checkout page is loaded
Lead	`fbq('track', 'Lead')`	When a form is submitted
Complete Registration	`fbq('track', 'CompleteRegistration')`	After account creation
View Content	`fbq('track', 'ViewContent')`	On product or key content pages
Search	`fbq('track', 'Search')`	When site search is performed
Contact	`fbq('track', 'Contact')`	Contact form submission

For e-commerce (most important): Purchase, Add to Cart, Initiate Checkout, View Content.

For lead generation (B2B/service businesses): Lead, Contact, Complete Registration.

Adding Event Parameters

The Purchase event should include value and currency parameters so Meta can optimize for revenue, not just conversion count:

fbq('track', 'Purchase', {
  value: 49.99,
  currency: 'USD',
  content_ids: ['SKU123'],
  content_type: 'product'
});

Where to add events:

Purchase: On the “Thank You” or order confirmation page, where the order is confirmed
Add to Cart: Triggered when the add-to-cart button is clicked (easier via GTM trigger)
Lead: On the “Thank You” page after form submission, or on form submission via GTM

Via GTM: Set up triggers for each event (button clicks, page URL matches) and fire custom HTML tags with the fbq() tracking code.

Conversions API Setup

The Conversions API (CAPI) sends event data from your server to Meta’s servers, bypassing browser-side limitations.

CAPI setup methods:

Partner integrations (easiest):

Shopify’s Meta channel automatically sends server-side events via CAPI
HubSpot has a native Meta CAPI integration
Most major e-commerce platforms have CAPI support built into Meta’s official channels

Manual setup: Meta provides an API endpoint and documentation for custom CAPI implementation. Requires development resources.

Event Match Quality: In Events Manager, Meta scores how well your event data matches users to their Meta profiles (Excellent, Good, OK, Poor). Better event matching = better optimization. To improve match quality, send customer data (email, phone, name) as hashed parameters with your conversion events.

Building Pixel Audiences for Retargeting

Once the Pixel is collecting data, you can build custom audiences for retargeting campaigns.

In Meta Ads Manager → Audiences → Create Audience → Custom Audience → Website:

High-value audiences to create:

All website visitors (30/60/90 days)
Product page viewers (ViewContent event, 30 days)
Add to Cart (no Purchase) — cart abandoners
Initiate Checkout (no Purchase) — checkout abandoners
Purchasers (Purchase event, 30/180 days)
High-value visitors (visited 3+ pages in one session)

Audience size minimums: Meta requires at least 100 people in an audience before you can run ads to it. Most audiences need 500+ people for effective optimization.

Exclusions: Always exclude recent purchasers from acquisition campaigns. Use the “Exclude” option when setting up retargeting ad sets — e.g., “All website visitors” minus “Purchasers (30 days).”

Lookalike Audiences

Lookalike audiences find people similar to your existing customers. They’re built from Custom Audiences.

Best lookalike seed audiences:

Purchasers (highest quality — Meta finds people similar to those who actually bought)
High-LTV customers (if you can upload a customer list with value data)
Email subscribers (lower quality than purchasers but larger in volume)

Lookalike sizes: 1% lookalike (smallest, most similar) → 5% (broader) → 10% (broad, less similar). Start with 1% for highest precision.

Pixel Data and Privacy Compliance

iOS 14+ impact: Apple’s App Tracking Transparency (ATT) framework requires apps to get user permission before tracking. Most iOS users opt out of tracking. This reduces the percentage of iOS user behavior that Meta’s Pixel can see.

Mitigation: Aggregated Event Measurement (AEM) — Meta’s solution for iOS tracking limitations. In Events Manager, verify your domain and configure priority conversion events (up to 8 per domain). Meta optimizes for these events even for iOS users who opted out, using aggregated and modeled data.

GDPR/CCPA compliance: The Pixel sets cookies and collects user behavior data — which requires user consent in GDPR jurisdictions and disclosure in CCPA jurisdictions.

Implement a cookie consent banner that blocks the Pixel from firing until consent is given (use Cookiebot, OneTrust, or similar)
Update your Privacy Policy to disclose use of the Meta Pixel and data sharing with Meta
Configure consent mode in GTM to respect user consent choices

Set up Meta Pixel-optimized landing pages, retargeting ad copy, and conversion-focused content with AdsMG.ai — AI-powered marketing for paid social advertisers.

Last updated: April 27, 2026

Next Step

Turn the ideas in this article into live campaigns, content, and creative tests.

AdsMG AI helps growth teams move from strategy to execution without stitching together separate tools for copy, optimization, and reporting.

Start free Explore free tools