How to track Facebook conversions on a WordPress site

List the actions that matter to your campaigns before adding code. Common Meta events include PageView, ViewContent, Lead, CompleteRegistration, AddToCart, InitiateCheckout and Purchase.

For a brochure site, a lead or registration event may be enough. For WooCommerce, plan to send product, currency, value and order information with the relevant events. WooCommerce tracking documentation lists product views, add-to-cart, checkout and purchase events as typical ecommerce conversions.

Open Meta Events Manager, select your website data source and copy its Pixel ID. You need access to the correct business, ad account and data source; copying an ID from the wrong business is a common reason events appear in the wrong account.

Do not create a second Pixel just because no events have arrived yet. First install the existing ID, then use Events Manager's test tools to check it.

For a manual setup, add Meta's base Pixel code to the site-wide head section using a child theme, a code-injection facility, or a small custom implementation. Replace the placeholder with your Pixel ID and make sure the base code loads only after the visitor has granted any consent required by your privacy setup.

The base code normally records page views. It does not automatically know that a form submission, checkout or purchase has happened, so those actions need separate event instructions.

Add a standard event where the action actually completes. For a lead form, fire Lead on a reliable thank-you page or successful submission callback, not merely when the form is displayed. For a registration, use CompleteRegistration. For WooCommerce, purchase tracking must use the completed order's value, currency and a stable order reference.

Manual ecommerce tracking is the part most likely to break: AJAX add-to-cart buttons, failed payments, cached thank-you pages and repeat visits can cause missing or repeated events. A WooCommerce integration can place events on the relevant shop and checkout actions instead of relying on a single static script.

In Events Manager, open the data source's test or diagnostic view, enter your website URL and complete each test action in a fresh browser session. Confirm the expected event name, URL and parameters, then check that a purchase is counted only once.

Browser extensions, ad blockers, caching and script optimisation can hide or delay events. Test logged out as well as logged in, and test the real mobile checkout if that is where customers convert.

For a simple site with one lead form, the manual route is reasonable once you understand the event code and consent requirements. For WooCommerce, multiple Pixels, dynamic purchase values or Conversions API support, use a dedicated tracking plugin instead of maintaining event scripts yourself.

PixelYourSite PRO is a suitable fast route when you want automated Meta event setup, WooCommerce conversion tracking, custom events or more than one Pixel. Install it from Plugins, enter the correct Pixel ID, enable only the events you need, and disable duplicate Pixel features in other plugins or in your theme.