How to track Facebook ad conversions on WordPress

Decide exactly what Facebook should count. For a lead-generation site this might be a successful form submission or a visit to a thank-you page. For WooCommerce, the main conversion is usually a completed purchase, with ViewContent, AddToCart and InitiateCheckout used as supporting events.

Do not count a button click as a sale unless the click itself completes the business action. Write down the event name, trigger and any value you need to send before installing anything.

In Meta Events Manager, create or select the website data source for the business and copy its Pixel ID. Keep this ID available while configuring WordPress. Meta’s WordPress integration supports standard events including Lead, ViewContent, AddToCart, InitiateCheckout and Purchase, and can also use the Conversions API.

Use one intended pixel for the site unless you have a clear reason to send data to more than one. Installing several unrelated snippets is a common cause of duplicate PageView and Purchase events.

For a small brochure site, copy the base Pixel code supplied by Events Manager and add it to the site header so it loads on the pages where conversions can happen. You can place it through a header-code tool or a child theme rather than editing the parent theme directly. WordPress exposes the wp_head action for output in the document head.

Then add the relevant standard event at the real success point. A lead event belongs after a confirmed form submission or on a thank-you page, not merely when the form is displayed. Manual tracking is fine for one or two simple events, but WooCommerce purchase data, AJAX forms and consent blocking make hand-written tracking harder to maintain.

For WooCommerce, configure product, cart, checkout and purchase events through a maintained integration rather than trying to reconstruct order totals in theme code. The Purchase event should fire once after a successful order and should include the correct value and currency where supported.

If you send both browser Pixel events and server-side Conversions API events, use the same event identifier so Meta can deduplicate them. Otherwise one order can appear as two conversions. Duplicate events and missing Purchase events are recurring WordPress support problems, especially after adding a second tracking plugin or changing checkout software.

Open Events Manager and use the test-events view while completing the journey yourself in a private browser window. Check the exact event name, URL, value, currency and whether the event arrived once. A browser Pixel helper or the browser’s Network panel can also show whether the script and event request are present, but the test-events view is the final check.

Test successful and unsuccessful journeys, mobile checkout, logged-out visitors and any payment method that redirects away and back. Do not assume the event works because the base pixel appears on the homepage.

If no event appears, check the Pixel ID, consent banner, ad blocker, cache and whether the success page actually loads. Cookie-consent tools can prevent the Pixel or its cookies from being set until consent is granted; current plugin support threads also report compatibility issues around consent and AJAX AddToCart events.

If events appear twice, disable duplicate snippets and integrations before changing the event code. If Purchase is missing, inspect the payment return flow, failed orders and whether the order-received page is cached. Never cache a personalised success page in a way that lets another visitor trigger the same conversion.

For most advertising sites, install and configure PixelYourSite Pro instead of maintaining event code yourself. It is aimed at Facebook-focused attribution, supports WooCommerce events and can handle more of the product, form and conversion setup from WordPress. Choose it when ad conversion tracking matters more than general site analytics.

After activation, enter the correct Pixel ID, enable only the events you need, configure consent behaviour, and test a real lead or test order in Events Manager. Remove any old Pixel snippets or overlapping tracking plugins first, or the same event may be sent twice.