Meta Ads

This video walks through the whole Meta setup on a real store, from the Pixel ID and access token to testing a WooCommerce purchase and a WS Form entry in Meta's Test events:

Enable Meta Ads

In your WordPress admin, go to Settings → Conversion Bridge → Ads and turn on Meta Ads. Its settings open below the toggle, with fields for your Pixel/Dataset ID, Access Token and Test Event Code.

Getting Your Meta Pixel ID

Follow the steps provided by Meta to create a new Pixel. Once done, you only need to provide the Pixel or Dataset ID that was created.

To find the ID, open Meta Events Manager and select your pixel under Datasets. The ID shows under the pixel's name and again in the Dataset ID panel on the right, as highlighted below. Copy it into the Pixel/Dataset ID field in Conversion Bridge.

Getting Access Token for API based tracking

By default Conversion Bridge always uses JavaScript based tracking for all platforms, including Meta. However, you can optionally enable API based tracking which allows for more accurate tracking as it can get around browser-based ad blockers.

To get started, you need to get an Access Token from Meta.

• Go to Meta Events Manager
• Be sure to select the proper account
• Select your pixel under Datasets
• Click on "Settings"
• Scroll to Set up direct integration and click Generate access token
• Copy and paste this into your Conversion Bridge settings

Above the button, Meta asks whether to set up with or without the Dataset Quality API. Either option works with Conversion Bridge, since it only needs the token to send your events. The Dataset Quality API option also lets other tools read Meta's quality reports for that pixel. Meta doesn't let you turn it off for a pixel once it's on, so if you're not sure, setting up without it keeps both choices open.

Configuring Multiple Meta Pixels

Conversion Bridge supports adding multiple Meta pixels to your website, allowing you to track conversions to different Meta advertising accounts simultaneously.

Why Use Multiple Pixels?

Agency Partnerships: When an agency takes over marketing for a client, they can add their own Meta pixel alongside the client's existing pixel. Both parties can track conversions independently in their respective Meta Business accounts while maintaining separate reporting and optimization capabilities.

Multi-Brand Management: If you manage multiple brands or business units under one website, each can maintain their own Meta pixel for separate campaign tracking and attributionThe process of determining which channels, campaigns, or actions contributed to a conversion, helping you understand what influenced a visitor’s decision to take action..

Testing & Migration: During pixel migrations or A/B testingA method of comparing two versions of a webpage, email, or element to see which one performs better based on user behavior or conversion rates., you can run multiple pixels simultaneously to compare data accuracy and ensure a smooth transition without losing tracking data.

How It Works

In the Meta Ads settings, use the Pixels repeater field to add multiple pixel configurations. Each pixel entry includes:

• Pixel/Dataset ID (see above): The unique identifier for your Meta pixel
• Access Token (optional, see above): Required only if you want to use the Meta Conversions API for server-side tracking
• Test Event Code (optional): A temporary code from Meta Events Manager used to send server-side Conversions API events to Meta's Test Events view

When multiple pixels are configured, all pixels are initialized on page load and every conversion event is automatically sent to all configured pixels. Each pixel can have its own access token for Conversions API tracking, allowing for server-side event tracking to specific pixels.

Testing Server Events in Meta

Meta Events Manager can provide a temporary Test Event Code so you can confirm Conversions API events are arriving in Meta's Test Events screen.

1. In Meta Events Manager, open your pixel and go to the Test events tab.
2. Choose Website as the channel, open Confirm your server's events are set up correctly, and copy the test code Meta shows.
3. In WordPress, go to Settings → Conversion Bridge → Ads → Meta Ads, paste the code into Test Event Code on the pixel row you're testing, and save.
4. Back in Test events, open Confirm your website's events are set up correctly, enter your site's address and click Test Events. This opens your site in a new tab that Meta marks as a test visit, so the browser (Pixel) events show up too, not only the server ones.
5. In that tab, place a test order or submit a form, and keep the Test events page open while you do.
6. Remove the Test Event Code from Conversion Bridge when you're done.

Each conversion shows up twice, once from the browser and once from the server, with the same event ID. Meta groups the two copies and labels one of them Deduplicated, but that label can take 15 minutes or so to appear. Until then, both copies can show as Processed, which is normal.

Click an event to open it. The User data keys line lists the customer details that came with it, such as email, name, phone and address.

The Test Event Code is added to server-side Conversions API events, so the same pixel row must also have an Access Token. If you have multiple Pixel/Dataset rows, add the code only to the row for the Meta data source you are testing.

Deduplication (Pixel + Conversions API)

When you add an access token, the same conversion gets reported to Meta twice: once from the browser by the Meta Pixel, and once from your server through the Conversions API. That's on purpose. (For how the server-side half actually reaches Meta, see how Conversion Bridge records events.) The browser copy is fast, the server copy survives ad blockers and browser restrictions, and between them far more conversions get through.

Meta needs to know those two reports are one conversion, not two. Conversion Bridge handles this for you by sending the same event ID with both copies. Meta matches them on event name plus event ID and counts the conversion once.

For purchases, the shared ID is the order's transaction ID, which is already unique per order. For other events, Conversion Bridge generates a unique ID in the browser at the moment the event fires, so cached pages can't freeze one ID across different visitors.

Two things worth knowing:

• The Pixel only sends an event ID when an access token is configured. DeduplicationDeduplication prevents the same conversion from being counted twice. It keeps your data accurate and is handled automatically by Conversion Bridge. only matters when the Conversions API is also sending the event, so without a token there's nothing to deduplicate against.
• Event names have to match on both sides. Conversion Bridge keeps them in sync automatically. If you rename events with custom code, matching names is what makes deduplication work.

You don't need to configure any of this. If you're seeing doubled conversions in Meta, it's almost always a second tracking tool also sending events, not Conversion Bridge.

Facebook Click ID (fbc)

Meta frequently prompts advertisers to "enable click tracking by adding the fbc parameter." Conversion Bridge already does this.

When someone lands on your site from a Facebook or Instagram ad, the URL carries an fbclid parameter. Conversion Bridge captures it on that first visit and stores it as part of the visitor's conversion journey. When the person converts later, the click ID is sent to Meta with the conversion so Meta can tie it back to the exact ad click.

It works in this order:

1. If Meta's own _fbc cookie is present, that value is used.
2. If not, Conversion Bridge looks up the most recent ad click in the visitor's journey and rebuilds the value from the stored fbclid.

That second step is the one that matters. Meta's _fbc cookie is often missing, either because a cookie banner blocked the Pixel from setting it or because the visitor came back in a different session. Conversion Bridge can still supply the click ID from its own journey data. Meta's _fbp browser ID is also forwarded with the conversion whenever that cookie exists.

Like Advanced Matching, this requires an access token, since the click ID is sent with the server-side Conversions API event.

Track Page Views

The Track all Page Views option gives you control over whether to track every pageview via the Meta Conversions API, or only track important conversion events (purchases, form submissions, etc.) via the API.

Default Behavior

By default, this option is disabled:

• Pageviews are tracked only via the browser-based Meta Pixel
• Conversion events are automatically sent via the Conversions API when an access token is configured
• This minimizes API calls while ensuring critical conversion events are tracked server-side

When to Enable

Enable Track all Page Views if you want to track every page view via the Meta Conversions API. This provides complete server-side tracking for all pageviews and better accuracy when browser-based tracking is blocked.

Requirements

• At least one access token must be configured for your Meta pixel(s)

Conversion events are always sent via the Conversions API when an access token is configured, regardless of this setting. This option only controls whether page views are also sent via the API.

Enhanced Conversions / Advanced Matching

Meta allows for Enhanced Conversions (or as Meta calls it Advanced Matching). This allows your website to send first-party dataInformation collected directly from your website visitors, customers, or users—such as form submissions, purchase history, and behavior on your site. securely along with your conversion data to better associate a user click with a conversion.

Most plugin conversion tracking integrations will automatically send enhanced conversion tracking data without any additional configuration. However, learn how to configure Enhanced Conversions for form integrations.

Customer details from every conversion, including guest checkouts and form entries, are sent through the Conversions API, so full Advanced Matching needs an access token. Without one, the Meta Pixel still receives the email and name of logged-in visitors.

Enhanced matching data directly impacts your Event Match QualityWhat it means: Event Match Quality is a score that Meta (Facebook) gives to each type of conversion event you send from your website. It measures how well the data you send -- things like email addres... score in Meta Events Manager. A higher score means Meta can match more conversions to real users, improving ad optimization and lowering costs. Learn how to check your Event Match Quality score.

Targeting Specific Conversion Events

Conversion Bridge sends event parameters along with each conversion event to Meta. You can use these parameters to create Custom Conversions in Meta that target specific events—such as a particular form, product category, or membership level—rather than optimizing for all events of a given type.

Event Parameters

Conversion events include parameters that provide context about the conversion. Common parameters include:

• id: A unique identifier (e.g., form ID, product ID)
• title: The name of the item (e.g., form name, product name)
• label: A custom label you can configure in Conversion Bridge settings
• value: The monetary value of the conversion
• currency: The currency code for the value

The specific parameters available depend on the event type and integration. For example, form submissions include the form's ID, title, and any custom label you've set.

Product Line Item Data

Purchase events from ecommerce integrations (WooCommerce, Easy Digital Downloads, etc.) also include a contents array with individual product line items. Each item in the array contains:

• id: The product ID (or variant ID if applicable)
• quantity: The number of units purchased
• item_price: The price per unit

This data allows you to create Custom Conversions that target purchases containing specific products. For example, you can create a conversion that only fires when a particular product ID is in the order, letting you optimize ad campaigns for specific products rather than all purchases.

Creating a Custom Conversion in Meta

Custom Conversions allow you to filter events by their parameters. This is useful when you want to optimize ad campaigns for a subset of conversions.

1. Go to Meta Events Manager
2. Click "Custom Conversions" in the left sidebar
3. Click "Create Custom Conversion"
4. Configure the custom conversion:
5. Name: A descriptive name for this conversion
6. Data Source: Select your pixel
7. Action Source: Website
8. Event: Choose the event type (e.g., Lead, Purchase)
9. Rules: Switch the rule type from URL to Event Parameters, enter the parameter name (for example title), choose contains or equals, and enter the value
10. Click "Create"

Once created, you can select this Custom Conversion as the optimization goal in your ad campaigns.

Example: Targeting a Specific Form

Suppose you have three forms on your website:

1. Newsletter Signup (ID: 123)
2. Contact Form (ID: 456)
3. Free Consultation Request (ID: 789)

All three send Lead events to Meta, but you want to optimize your ad campaign specifically for "Free Consultation Request" submissions.

Step 1: Identify the parameter to filter by

Form submissions include these parameters by default with every form submission as custom event parameters:

• id: The form's unique ID
• title: The form's name
• label: A custom label set in Conversion Bridge

Using the label is often the most flexible option since you control it directly and it won't change if you recreate the form.

Step 2: Create a Custom Conversion

In Meta Events Manager, create a Custom Conversion with these settings:

• Event: Lead
• Rule: Parameter label equals consultation-lead (or use id equals 789)

Step 3: Use in your ad campaign

When setting up your campaign, select your Custom Conversion as the optimization event. Meta will optimize delivery for users likely to complete that specific form.

Example: Targeting Purchases of a Specific Product

Suppose you sell several products and want to optimize a campaign specifically for purchases that include your flagship product (ID: 42).

Step 1: Identify the parameter to filter by

Purchase events include a contents array with each product's id. Meta's Custom Conversion rules can match against values within this array.

Step 2: Create a Custom Conversion

In Meta Events Manager, create a Custom Conversion with these settings:

• Event: Purchase
• Rule: Parameter contents contains 42 (the product ID)

This Custom Conversion will only count purchases where product ID 42 was in the order, regardless of what other products were also purchased.

Step 3: Use in your ad campaign

Select this Custom Conversion as your optimization event. Meta will optimize delivery for users likely to purchase that specific product.

Tips

• Use descriptive labels: Configure meaningful labels in Conversion Bridge (e.g., demo-request, pricing-inquiry) to make filtering easier
• Create separate Custom Conversions: For each high-value conversion action, create its own Custom Conversion for independent optimization and reporting
• Combine rules: Use multiple conditions (AND/OR) in Meta's Custom Conversion rules for more complex filtering

How to Confirm Events Are Being Tracked

If you are using the Meta Pixel for tracking events, you can install the Meta Pixel Helper Chrome extension. This will tell you when events are tracked by performing the conversion event yourself and check the results from this extension.

Example WooCommerce purchase event tracked in Meta

If you are using the Access Token for API based tracking, there are two ways to confirm conversion events are being tracked:

Using Conversion Bridge logging

Enable Conversion Bridge logging and then check the log file to see if Meta ad events are being successfully logged. It will appear similar to this in the log file if it is a success:

Example Meta Conversion API result in log file

Using Meta Events Manager

Alternatively, you can confirm the event in Meta Events Manager by looking at the latest events for your site's pixel, or run a live check with Test events.

Events can take up to 30 minutes to appear on the pixel's Overview, so give it a little time after running a test.

Access token disappears or "Cannot parse access token"

If your access token works for a few days and then the field is empty again, or the Health page shows "Invalid OAuth access token - Cannot parse access token", your site's security keys most likely changed. The token is fine on Meta's side. Conversion Bridge just can't unlock the copy it saved.

Some security plugins and hosts change those keys on a schedule. See keep your saved tokens working when security keys change for the two lines to add to wp-config.php so it stops happening, then enter the access token again.