“Plugin activated” does not mean your advertising setup is receiving the right data. A Pixel can send events to the wrong source, measure page views only or duplicate actions. Finish installation by checking a real event, not by admiring a green status in WordPress.
Validate the data source, the real action and repeat behavior before relying on the measurement.
This guide uses one integration: the official Meta pixel for WordPress plugin by Facebook. It supports the Pixel and Conversions API. That does not promise automatic measurement for every form builder or custom checkout: verify the events you actually need. If you need the underlying concept first, read our explanation of Meta Pixel.
Identify what is already installed
You need permission to install WordPress plugins and access to the intended Meta data source. Record its ID and the site's address beforehand. Several assets may have similar names, and “Pixel 1” is not a useful identifier. Meta's general implementation requirements include website access, the Pixel ID or base code, and access to its advertising tools.
Check existing plugins, theme settings and Google Tag Manager. If another specialist already installed the Pixel, establish where the active installation lives. Adding another copy while leaving the old one in place is not extra reliability. Record current settings and keep a way to roll back, particularly on a website taking orders.
Define the action before connecting anything: a page view, a successful enquiry or a purchase. A lead event should represent an accepted form submission, not every click on its button. Otherwise, your advertising data may include people who clicked Submit with an empty required field.
Connect the official plugin
- In WordPress, open Plugins and the option to add a new plugin.
- Find Meta pixel for WordPress. The installation instructions also use the search name Facebook for WordPress. Confirm that its author is Facebook.
- Install and activate it.
- Open the plugin settings and select Get Started.
- Complete the Facebook Business Extension connection, selecting the appropriate business assets and finishing the integration's authorization.
Compare the selected source with the ID you recorded earlier. Do not include an access token in a team chat or a screenshot sent to a contractor: status and the source ID are enough for an initial check. If your website uses caching, refresh the relevant cache after the installation change so you test the current page.
Individual screen labels vary by language and integration version. If an expected business asset is missing, check permissions first. Creating another Pixel does not solve access to the existing one.
Test the action, not the plugin
Open the intended data source in Meta Events Manager. Use event testing and the information for received events. Check the event name, time and connection method: browser or server. Meta exposes the channels through which events arrive.
Make one controlled visit: open the page, then perform the target action. Record the time. A normal page load should produce PageView; an enquiry should produce the event you configured for successful submission. Seeing PageView does not prove that Lead or Purchase also works.
Test a failed attempt too. Submit the form without a required field: it should not produce a successful lead event. For a shop, check that a purchase corresponds to a confirmed order rather than opening the cart. These checks take less time than untangling attractive but incorrect campaign reporting later.
Verify a real lead before optimizing ads
Run two controlled form tests: one successful submission and one invalid attempt with a required field missing. Open Test Events in Meta Events Manager and reproduce both. Lead should fire only when the form actually accepts the request, not just when someone taps Submit. Compare those events with entries saved by the form or CRM.
Inventory every installation path. The official Meta pixel for WordPress plugin supports the browser Pixel and Conversions API. If an older Pixel also runs through GTM, the theme or another plugin, multiple active implementations can send duplicate browser events for one action.
A browser event and a server event are not necessarily two purchases. When Pixel and CAPI report the same transaction, coordinate event names and event IDs so deduplication can match them. Use a stable order identifier for purchases and preserve it if the server retries delivery.
Document the Pixel ID, integration owner, event name, trigger and test outcome. A received event in Test Events does not prove that a particular advertising campaign was credited with a conversion. Event delivery and attribution should be investigated separately.
Missing events or suspiciously high counts?
Start with the source ID, completed connection and current page version. Then check whether your test browser blocks measurement and whether the site's required consent has been provided. Test an ordinary visitor scenario rather than removing everyone's privacy controls to make a status indicator turn green.
A browser record and a server record do not necessarily represent two conversions. When Pixel and Conversions API both describe the same action, their event name and identifier must be coordinated for correct deduplication. Two independent browser installations are a separate issue.
Save a short handover note: which ID is in use, what action triggers the event and what happens when the page is opened again. That gives the next specialist useful evidence about the setup. A screenshot of an activated plugin does not.


Комментарии