How to Set Up Facebook Pixel on WordPress

To set up Facebook Pixel on WordPress, create or select your Meta Pixel in Events Manager, connect it through one WordPress integration or add the base code manually, then test a page view and the action you actually want to measure. Facebook Pixel is now called Meta Pixel. Installing the code is only the first part: a working PageView does not prove that a contact form, booking or purchase is recorded correctly.

If you use Niwa on your WordPress site, start with the customer journey you want to support. A visitor might ask Niwa about a product and proceed to checkout, or ask about a service and complete a website booking. Install your measurement around those real outcomes, with one clear owner for each event.

Before you change anything

You need WordPress administrator access, access to the correct Meta business and website data source, and a way to manage advertising consent. Keep a backup or a recorded configuration you can restore.

Check whether your site already loads a Pixel. Review your tracking plugins, tag manager, header scripts and theme settings. Adding another integration to an existing one can make the numbers harder to trust. Write down the existing Pixel ID and the component that installs it.

Choose a concrete goal. For a service business, that might be a successfully received enquiry or a confirmed appointment. For a store, it could be a completed checkout with the actual order value.

1. Create or select the website data source

Open Meta Events Manager in the business that owns your advertising assets. If a suitable Pixel already exists, select it instead of creating another.

For a new connection, Meta's setup flow starts with Connect data, then Web. Follow the guided setup to create the Pixel and give it a recognizable business name. Copy its numeric ID. Account interfaces can vary, so follow the available website connection flow rather than looking for an old screenshot's exact layout.

Meta separates installing the base code from configuring the events you want to measure. Its installation guide describes partner integration and manual setup.

2. Choose one installation route

For an ordinary WordPress site, use a maintained Pixel integration that supports your consent setup. If you already operate a tag manager, you can manage the Pixel there instead. A developer can also install the code without a dedicated tracking plugin.

For WooCommerce, choose an integration that reads store events and order data. If your store uses Niwa's storefront assistance, measure the checkout result after the customer's product questions have been resolved. A header-code tool can load the base Pixel, but it does not automatically supply a reliable Purchase event.

Confirm which component owns PageView and which owns each conversion. Avoid combining a plugin's automatic Purchase tracking with a second Purchase rule on the same confirmation page.

3. Connect the correct Pixel

One concrete route is the free PixelYourSite plugin by PixelYourSite. Its current WordPress package provides the following controls:

In WordPress, open Plugins > Add New, search for PixelYourSite and select the plugin authored by PixelYourSite.
Choose Install Now, then Activate. Open PixelYourSite > Dashboard.
Expand Your Meta Pixel. Paste the ID from the intended Meta business's website data source into Meta Pixel ID.
Turn on Enable Pixel and click Save Changes. This ID-based route does not require pasting the entire base script into a header field.
Open the plugin's Consent section and connect the supported integration for the consent tool your site uses. The vendor's consent instructions cover the supported options. Configure that tool to ask before advertising tracking where required.
Clear the relevant page cache. Run the accepted-consent and declined-consent tests described below, checking the same ID in the browser and Events Manager.

These control names were verified against the free plugin's current source. The vendor's Meta settings guide also explains the ID and Enable Pixel controls, although its navigation example is for Pro. Check the options in your installed edition before enabling automatic events or an additional server connection.

If you choose manual installation, copy the base code from your own Meta setup and place it in your site's persistent header through an update-safe mechanism. Meta's developer instructions describe the base code and tag-manager option. Do not paste it separately into every page.

Clear relevant page caches after a change so that you test the version visitors receive.

Advertising tracking should follow the consent requirements that apply to your audience. For UK visitors, the ICO explains that non-essential advertising cookies require consent. A privacy-policy link alone does not give that consent. See the ICO's cookie guidance.

Connect the actual Pixel loader to your consent system. A banner that changes appearance while advertising scripts load anyway is insufficient. Test the declined state as well as the accepted state. Other jurisdictions may impose different requirements.

5. Test a page view and a completed action

Use Meta's Chrome diagnostic extension. Current Meta documentation calls it Meta Ads Data Advisor, formerly Meta Pixel Helper. Open your website, give the appropriate advertising consent, and inspect the Pixel ID and events. For installation checks, use its diagnostic features; review any proposed automated changes before approving them.

Then open the correct data source's Test Events area and follow its browser-testing instructions. Visit a page and complete your chosen action once. Check the event name, destination ID and relevant parameters.

A form submit button is not a received lead. Opening a booking calendar is not a reservation. With Niwa website booking, check that the appointment is saved before recording it as a booking. A failed payment should not count as a successful purchase under a paid-order measurement definition.

Where Niwa fits

Niwa helps customers use the website: it can explain products or services and guide them toward a purchase or booking. Configure your Pixel around the confirmed outcome of that flow. Niwa's customer assistance and your tracking integration have different jobs.

An AI-built website uses AI during construction. An AI-powered website continues helping customers after launch. Existing WordPress owners can use the standalone Niwa plugin; a new site is not required.

Niwa Business costs USD 150 and includes a custom WordPress website or migration, hosting, maintenance and AI tools adapted to the business. Contact Niwa about your WordPress workflow and include your website, current tracking setup and the action you want visitors to complete.

If the first test fails

If no Pixel appears, inspect consent, caching and the integration's saved ID. If PageView works but the conversion does not, inspect the success trigger. If one action generates two browser conversions, check for a second installation or event rule.

Finish with a short record: Pixel ID, installation owner, event owner, consent behavior and successful test result. That gives the next person maintaining the site a useful starting point.