--- title: "How to Track Facebook Pixel Events in WordPress?" url: https://nexterwp.com/docs/track-facebook-pixel-events-in-wordpress/ date: 2023-07-01 modified: 2026-09-23 lang: en author: "Aditya Sharma" description: "The Meta pixel counts page views on its own. What it cannot see is which button someone pressed — and that is what your ad optimisation actually needs. This sends..." image: https://nexterwp.com/wp-content/uploads/2024/05/track-facebook-pixel-events-in-wordpress-1024x519.jpg word_count: 741 --- # How to Track Facebook Pixel Events in WordPress? ## Key Takeaways - Nexter Blocks Event Tracking extension tracks WordPress website events with Facebook pixel, and the extension is part of Nexter Blocks. - Facebook Pixel ID is added in Nexter → Extra Options → Settings by enabling Add Event Tracking ID, opening the settings icon, and saving the ID in the Facebook Pixel ID field. - Nexter Blocks event tracking supports buttons, forms, and custom links, and the Event Type dropdown includes standard Facebook events plus custom Facebook events such as Purchase. The Meta pixel counts page views on its own. What it cannot see is which button someone pressed — and that is what your ad optimisation actually needs. This sends a standard pixel event when someone interacts with a block. *For every Event Tracking setting in one place, see the [event tracking guide](https://nexterwp.com/docs/add-event-tracking-in-wordpress/).* [LIVE BLOCK LINK](https://nexterwp.com/nexter-blocks/extras/wordpress-facebook-pixel-event-conversion-tracker/) ## Before You Start - **Edition:** **Pro** — event tracking needs Nexter Blocks Pro.- **Block to enable:** Event Tracking, switched on under **Nexter > Blocks** in your WordPress dashboard.- **A Meta pixel ID**, entered in Nexter's settings.- **Event tracking switched on** in those settings. > *Save the event tracking setting as enabled before configuring the block. Measured: with it never saved, the published page carries no tracking markup even though the editor offers the options.* ## Steps - Copy your **pixel ID** from Meta Events Manager. ![Finding the pixel ID](https://nexterwp.com/wp-content/uploads/2023/07/facebook-create-pixel-1.png) - Paste it into Nexter's settings. ![Entering the pixel ID](https://nexterwp.com/wp-content/uploads/2023/07/facebook-create-pixel-2.png) - Switch **event tracking** on. ![Enabling event tracking](https://nexterwp.com/wp-content/uploads/2023/07/facebook-create-pixel-3.png) - Select your block and open the **Advanced** tab. ![The Advanced tab](https://nexterwp.com/wp-content/uploads/2023/07/facebook-create-pixel-4.png) - Turn on **Facebook**. ![Choosing Facebook as the provider](https://nexterwp.com/wp-content/uploads/2023/07/facebook-create-pixel-5-1.png) - Choose the standard event that matches what the block does. ![Choosing a standard event](https://nexterwp.com/wp-content/uploads/2023/07/add-facebook-pixel-id-new-1024x569.png) - Publish. ![The configured block](https://nexterwp.com/wp-content/uploads/2023/07/event-tracking-add-facebook-event-1.gif) - Confirm the event with the Meta Pixel Helper while you click the block. ![Checking with Pixel Helper](https://nexterwp.com/wp-content/uploads/2023/07/facebook-pageview-event.gif) - Check it appears in Events Manager. ![The event in Events Manager](https://nexterwp.com/wp-content/uploads/2023/07/facebook-purchase-event.gif) - Use it as a conversion in your campaigns. ![Using the event as a conversion](https://nexterwp.com/wp-content/uploads/2023/07/tracked-facebook-events-list.png) ## How It Behaves - **Turn event tracking on in Nexter's settings first.** Measured: with the site-level setting unset, a block configured for both providers emitted **nothing** — no markup, no console message, no warning. With the setting enabled and nothing else changed, the same block immediately emitted its full tracking payload.- **The event is sent by name.** Read from the shipped script, a standard event results in `fbq('track', )`.- **The default is `ViewContent`**, so change it deliberately.- **Setting a pixel ID also fires a PageView on every page automatically**, separately from any block. That happens as soon as the ID is saved.- **Custom properties reach Google only.** Read from the script: properties are merged into an object and passed on every Google call, while the Facebook calls are made with the event name alone. If you need properties on a Meta event, this feature will not send them.- **The whole configuration is written onto the block.** Measured: the block gains a `tpgb-event-tracker` wrapper and an inner element carrying a `data-event-opt` attribute holding the providers, the event type and name, and any custom properties. You can confirm your setup reached the page by looking for that attribute.- **Only certain things inside the block fire an event.** Read from the shipped script, this is the complete list, all on click: any link, a video play button, and the submit button of Mailchimp, WPForms, Everest Forms or Contact Form 7. A block containing none of those is tracked in name only.- **Binding happens once, when the page loads.** Blocks added to the page later by AJAX are not picked up.- **Measured with Nexter Blocks Pro deactivated:** a fully configured block emits no tracking markup at all. Event tracking is Pro only and does not degrade. ## Limitations - **What this page verified, and what it did not.** The markup the block emits and the calls the script makes were measured. Whether an event *arrives* in your analytics account was not, and cannot be from the page source. Confirm arrival in the provider's own tools.- **Standard event names are Meta's, not this plugin's**, and Meta changes them independently.- **No parameters are sent with the event.** Meta's standard events accept parameters such as `value` and `currency`; this feature sends the event name alone, so a `Purchase` event carries no purchase value.- **Browser tracking protection and consent tools block the pixel outright**, in which case nothing is sent and the console says `fbq is not defined`.- **Only links and a few form submit buttons fire it.**- **Pro only.** ## Troubleshooting ### Pixel Helper shows nothing Check the site-level event tracking setting first. Then check the console for `fbq is not defined`, which means the pixel library never loaded — usually a missing ID, a consent banner, or tracking protection. ### PageView fires but my event does not PageView comes from the pixel itself and proves only that the ID is correct. The block event is separate: confirm `data-event-opt` is present on the block in the page source. ### My Purchase event has no value This feature sends the event name without parameters. For value and currency you need a purchase integration rather than a block-level click event. ### I need a name Meta does not offer Use a custom event. See [the custom Facebook events doc](https://nexterwp.com/docs/track-custom-facebook-events-in-wordpress/). ## Related Docs - [Track custom Facebook events](https://nexterwp.com/docs/track-custom-facebook-events-in-wordpress/)- [Add event tracking in WordPress](https://nexterwp.com/docs/add-event-tracking-in-wordpress/)- [Track Google Analytics events](https://nexterwp.com/docs/track-google-analytics-events-with-wordpress/)- [Track custom Google Analytics events](https://nexterwp.com/docs/track-custom-google-analytics-events-in-wordpress/)- [Advanced tab settings](https://nexterwp.com/docs/use-advanced-tab-in-nexter-blocks/)