Skip to main content
Go to nevuto.com

Meta Pixel

Published April 29, 20267 min read

What is Meta Pixel?

Meta Pixel (formerly the Facebook Pixel) is a small piece of code Meta asks you to install on your store. It watches how visitors interact with your pages and reports that activity back to Meta so your Facebook and Instagram ads can learn who's interested, show up in front of the right audiences, and measure which campaigns actually drive sales.

At a minimum, the Pixel records page views and standard e-commerce events (viewing a product, adding to cart, starting checkout, completing a purchase). Over time this data powers Meta's ad optimization, custom audiences, and remarketing — for example, running an ad that only targets people who looked at a product but didn't buy.

Meta Pixel collects the visitor's IP address, user agent, browsing events and Meta-specific cookies (_fbp and _fbc). No raw personal information (names, emails, phone numbers) is ever sent from the browser.

How Nevuto handles Meta Pixel

Nevuto ships the deepest Meta Pixel integration of any of its tracking tools. Unlike script-only integrations, Meta Pixel runs both in the browser (client-side) and on Nevuto's servers (Conversions API / server-side), so your conversion data survives iOS 14+ tracking limitations, ad blockers, and flaky mobile networks.

Browser-side events Nevuto fires

As your customers browse your store, Nevuto fires these Meta Pixel events on their behalf:

  • PageView — every page load
  • ViewContent — when a customer opens a product page
  • Search — when a customer runs a product search
  • AddToCart — when a customer adds an item to their cart
  • InitiateCheckout — when a customer opens the checkout page, from either the cart page or the "Buy Now" shortcut on a product
  • AddPaymentInfo — when a customer enters payment details during checkout
  • Purchase — on the order confirmation page after payment succeeds

Server-side tracking with the Conversions API (CAPI)

When you provide a Conversions API Access Token (under the Advanced section of the Meta Pixel setup page), Nevuto additionally sends these events directly to Meta's servers from its own backend:

  • AddToCart — fires the moment an item is added to a cart
  • InitiateCheckout — fires when a checkout session is created
  • CompleteRegistration — fires when a new customer signs up on your store
  • Purchase — fires asynchronously from Nevuto's queue worker when the order is confirmed paid, so Meta receives the conversion even if the customer closes their tab mid-redirect

Each server-side event carries the matching signals Meta needs — hashed email, phone, name, address and external ID from the customer, plus the _fbp / _fbc cookies captured during checkout, the real browser user agent and the customer's IP address. Meta uses these to recognize the same person the browser Pixel saw.

Deduplication is handled automatically using deterministic event IDs (order_<id>, checkout_<cart_id>, cart_item_<id>, customer_<id>), so turning CAPI on won't inflate your conversion counts — every server event is matched back to its browser twin.

Why the Conversions API matters

  • iOS 14+ and App Tracking Transparency: Apple's ATT prompt blocks a huge share of browser-based Pixel hits. Server-side events bypass this entirely.
  • Ad blockers and privacy extensions: browser events can be silently blocked at the network level. Server events are sent from Nevuto's backend to Meta's backend and cannot be blocked by the visitor's browser.
  • Network reliability: if a customer closes their browser during the redirect back from a payment provider, the browser-side Purchase event may never fire. The server-side Purchase event always fires once the order is marked paid in Nevuto.

Running the Pixel alone still works — you'll just get weaker attribution and a lower match quality score. Adding the Access Token is strongly recommended whenever you're actively spending on Meta ads.

Add Meta Pixel to your Nevuto store

  1. Log in to your Nevuto admin panel.
  2. Go to Settings → Integrations.
  3. Click the Add button next to Meta Pixel.
  4. Paste your Pixel ID into the first field.
  5. (Recommended) Under the Advanced section, paste your Conversions API Access Token.
  6. (Optional) Paste a Test Event Code while you're validating the setup — events tagged with this code appear under the Test Events tab in Meta Events Manager instead of polluting your live data.
  7. Toggle the status to Active and click Save.

You can save the integration with only the Pixel ID filled in if you want to start with browser-only tracking. Advanced fields can be added later at any time from the same page.

Where to find your Pixel ID and Access Token

Pixel ID

  1. Sign in to Meta Business Manager at business.facebook.com.
  2. Open the Events Manager (All Tools → Events Manager).
  3. Select your Pixel from the left sidebar, or click Connect Data Sources → Web → Meta Pixel to create a new one.
  4. Your Pixel ID is shown at the top of the overview page — a 15-digit number.
  5. Copy it and paste it into the Pixel ID field in Nevuto.

Conversions API Access Token

  1. In Meta Events Manager, open your Pixel.
  2. Go to Settings → Conversions API.
  3. Scroll to Set up manually and click Generate access token.
  4. Copy the token immediately — Meta only shows it once. If you lose it you can always generate a new one.
  5. Paste it into the Access Token field in Nevuto.

Test Event Code (optional, for debugging)

  1. In Meta Events Manager, open your Pixel.
  2. Open the Test Events tab.
  3. Copy the test code shown at the top of the page (e.g. TEST12345).
  4. Paste it into the Test Event Code field in Nevuto.
  5. Remove it once you're done testing — leaving a test code live means your real traffic won't show up in the main Events dashboard.

Test that it's working

  • Browser events: install the official Meta Pixel Helper Chrome extension. Open your storefront in the same browser — the extension icon should light up and show your Pixel ID. Browse to a product page, add it to the cart, and start checkout; you should see ViewContent, AddToCart and InitiateCheckout events fire in real time.
  • Server events: in Meta Events Manager, open your Pixel and watch the Overview tab. Server-side events show a small server icon next to them. During a test purchase, both the browser and server versions of the same event should appear within a few seconds of each other.
  • Test Events tab: if you set a Test Event Code, go to Events Manager → Test Events and trigger a test order. Every event — browser and server — should show up in real time under that tab.
  • Match quality: after a few real orders have flowed through, open your Pixel → Overview → Event quality. A well-configured CAPI integration typically scores 7/10 or higher. Scores below 5 usually mean the Access Token isn't set.

Troubleshooting

  • "Meta Pixel is not configured correctly" error on save: the Pixel ID format is wrong. Nevuto expects 15+ digits. Strip any dashes, spaces or prefixes before pasting.
  • Events missing in Events Manager: confirm the integration status toggle is set to Active in Nevuto settings and that you've saved the page. Then test again in an incognito window with no ad blockers.
  • Purchase event never fires on the server: confirm the Access Token is saved and hasn't been revoked. Tokens generated in Events Manager stay valid until the Meta user who created them loses access to the business account.
  • Duplicate conversions in Meta: this should not happen — Nevuto deduplicates every server/browser pair via stable event IDs. If you do see duplicates, check that you haven't pasted the Pixel script manually into your theme's custom code section on top of the integration. Nevuto injects it automatically; adding it twice will double-count.
  • Ad blockers are blocking everything: this is why CAPI exists. Even if the browser Pixel is fully blocked, the server-side events will still reach Meta. Turn on CAPI and you'll continue seeing conversions in Events Manager.

Related articles