You can set up the Facebook Pixel on WordPress, WooCommerce, and Wix without Shopify by adding your Meta Pixel base code to every page, then mapping the key events — PageView, ViewContent, AddToCart, and Purchase — to each platform's checkout steps. This facebook pixel setup course guide walks through the method for each platform, how to verify it in Meta Events Manager, and the mistakes that quietly break tracking.
Meta gives you a unique Dataset ID, formerly called a Pixel ID, and a JavaScript snippet that must load on every page.
Setting Up the Pixel on WordPress
On a standard WordPress site you have two reliable options. The first is a plugin — Meta's official partner integration or a trusted header and footer code plugin — which lets you paste the base code once and have it appear sitewide. The second is adding the code directly to your theme's header, which works but risks being overwritten during a theme update.
For most owners, the plugin route is safer. Install it, paste your Pixel ID, set it to load on all pages, and confirm PageView appears. A step-by-step facebook pixel setup course helps here, because small choices decide whether later events fire cleanly.
Adding Events on WordPress Pages
PageView fires automatically with the base code. For a lead form, add a Lead event on the thank-you page or on successful submission. For a product or content page, add ViewContent with the content ID, name, and value where relevant. Keep parameters consistent: same currency format, same ID system, and numeric values without currency symbols.
WooCommerce: Mapping Events to the Store Flow
WooCommerce needs more than the base code, because the valuable events happen inside the shop flow. A good integration handles this mapping for you:
- ViewContent on single product pages, with the product ID and price.
- AddToCart when a visitor adds an item, including on AJAX add-to-cart buttons.
- InitiateCheckout when the checkout page loads.
- Purchase on the order-received thank-you page, with the real order value and currency.
Check plugin settings carefully. Some plugins fire Purchase from the checkout page instead of the confirmation page, inflating results if a payment fails. Others miss AJAX AddToCart events, so the funnel looks broken even though shoppers are buying. Test a full order, then confirm each event appears once, in order.
See also our beginner's guide to starting a Shopify store.
Wix: Working Within the Platform Limits
Wix is more restrictive. You cannot freely edit the underlying page code as you can on WordPress, and custom code added through Wix settings has placement and page limits depending on your plan. The standard approach is to connect your Pixel through Wix's marketing integrations panel by pasting your Pixel ID, which handles PageView reliably.
For deeper events, expect workarounds. Purchase tracking depends on the built-in integration, you have less control over parameters than on WooCommerce, and custom code cannot run on checkout pages. Verify what the integration actually sends and base ad decisions on that.
How to Verify With Meta Pixel Helper and Test Events
Never trust a setup you have not verified. Install the Meta Pixel Helper browser extension, visit your site, and check that the correct Pixel ID loads with no warnings. Then open Meta Events Manager, go to your dataset, and use the Test Events tab. Browse your site in the same session, add a product to the cart, and complete a test purchase. Each event should appear in Test Events within moments, with its name and parameters.
Watch for deduplication if you add the Conversions API later: browser and server copies of an event should share an event ID. See also our guide to Facebook Ads sales campaigns for online stores.
Common Mistakes That Break Tracking
- Duplicate events: A plugin and a manual code paste both fire PageView or Purchase, doubling your numbers. Use one installation method only.
- Wrong currency or value: Sending value as text, mixing currencies, or sending a subtotal instead of the order total makes optimization data unreliable.
- Page-builder conflicts: Some page builders delay or block scripts, so events on builder pages may not fire. Test those pages separately.
- Multiple pixels on one site: An old Pixel ID left in a plugin field alongside a new one splits data across two datasets.
- No testing after changes: A theme update, new plugin, or consent change can silently stop events. Re-test after every site change.
Frequently Asked Questions
Do I need a plugin to install the Pixel on WordPress?
No, you can add the code manually to your theme header, but a plugin is safer for most owners because it survives theme updates and usually handles WooCommerce events automatically.
Why does my Purchase event fire twice in WooCommerce?
Usually because both a plugin and a manual snippet — or two tracking plugins — are installed. Remove one method, clear your cache, and run a fresh test order to confirm a single Purchase.
Can I fully track purchases on Wix?
You can track standard events through Wix's Meta integration, but checkout pages do not accept custom code, so control over parameters is limited. Verify in Test Events exactly what the integration sends.
How long before events show in Events Manager?
Test Events shows browser activity almost immediately. Aggregated reporting in Events Manager and Ads Manager can take longer, so always debug in Test Events first.
Learn the Full Setup, Step by Step
If you want the complete walkthrough for all three platforms — installation, event mapping, verification, and troubleshooting — the Pixel Setup Without Shopify course covers WordPress, WooCommerce, and Wix in full for $39. You can also browse all of our practical marketing courses on the courses page.