Setting up Meta Pixel

Use Meta Pixel to measure visits to your storefront and send purchase activity to Meta. The browser pixel works with your Pixel ID. Adding an optional Conversions API access token lets Nevuto also send supported events from its servers.

Before you start

• Sign in as the store owner, or use a staff account with access to manage Apps and integration settings.
• Have access to the correct pixel in Meta Events Manager. Use a separate test data source when preparing your setup.
• Copy the Pixel ID for your website. This is a numeric identifier, not your ad account ID or a complete tracking script.
• Decide whether to use the browser pixel alone or also configure Conversions API (Advanced).

Check that your storefront's customer privacy settings allow the tracking you intend to test. Marketing consent and browser blocking can affect delivery. A saved integration does not confirm that Meta has received an event.

Install or open Meta Pixel

1. In Nevuto Admin, open Settings > Apps.
2. If Meta Pixel is not installed, click Explore apps, find Meta Pixel in the app store, and start its installation for the intended store.
3. Review the Install Meta Pixel? dialog and its requested permissions, then click Install app.
4. If it is already installed, open its app details under Settings > Apps and click Open app to reach its configuration.

The installation dialog shown before installing Meta Pixel in the demo store. Installing the app and enabling tracking are separate steps. Select any image to view it at full size.

Connect the browser pixel

1. In the Meta Pixel configuration, find App settings.
2. Enter your Pixel ID in the field labeled Meta Pixel. Paste the ID only.
3. Turn on Enable Meta Pixel when you are ready for the integration to run.
4. Leave the advanced fields empty if you want browser tracking only.
5. Click Save in the upper-right corner. Resolve any validation error, then reopen the configuration to check the saved ID and enabled setting.

Initial configuration with no Pixel ID or token entered and tracking disabled. The Save button becomes available when the form has unsaved changes.

Nevuto checks the submitted values' format when saving; this does not authenticate your token with Meta or test event delivery. Do not add the same pixel again through a theme script or another integration without checking for duplicate tracking.

Add optional server events

Use the same pixel for browser and server tracking. In Meta Events Manager, select that pixel, open Settings, and find Conversions API. Under its manual setup, generate an access token using an account allowed to do so. See Meta's Conversions API setup guide.

Back in Nevuto:

1. Expand Conversions API (Advanced).
2. Paste the generated token into Access Token.
3. If you are testing server events, copy the code from the pixel's Test Events tab into Test Event Code. This field is optional and is used with the access token.
4. Check Enable Meta Pixel and click Save.

The advanced section expanded for reference. All fields are empty and tracking remains off in this screenshot; no connection or successful event is being demonstrated. Keep access tokens out of shared screenshots and support messages.

A Test Event Code makes server events visible in Test Events; it is not an isolated sandbox. Meta can still use those events for measurement and targeting. Use a dedicated test data source where possible. See Meta's test-event guidance.

Server purchase events are tied to paid storefront orders. Simply opening the configuration or placing an unpaid order does not prove that a purchase event will be sent.

Browser Purchase events come from the order-completed screen. An order using a manual payment method can reach that screen while still awaiting payment. Check the order's payment status in Nevuto when comparing browser events with server purchases.

Verify your setup

After saving your own test configuration:

1. Open Test Events for the matching pixel in Meta Events Manager.
2. Visit your storefront in a separate browser tab and grant marketing consent if your privacy settings request it.
3. Confirm that a browser PageView arrives for the intended website and pixel.
4. Complete a test checkout using your payment provider's test environment, including its successful payment and return to the store.
5. Check the paid order in Nevuto and the corresponding Purchase event in Meta. If you supplied an access token and test event code, inspect the server event in Test Events as well.
6. Confirm that a failed or cancelled checkout does not appear as a successful purchase. Browser and server copies of the same purchase should not inflate your purchase count.

These are verification steps for your account. The screenshots show setup screens, not a completed tracking test. For Meta's event-testing instructions, see Using the Conversions API.

Move from testing to normal reporting

Confirm that the Pixel ID and access token belong to your intended production pixel. When server-event testing is complete, clear Test Event Code and click Save so subsequent server events are no longer tagged with that test code. Leave Enable Meta Pixel on for normal collection, and verify new activity in Meta after the change.

Meta Pixel has no separate Nevuto sandbox switch. Test routing is different from your payment provider's sandbox setting; review both before accepting and measuring real orders.

Edit or stop tracking

Open Settings > Apps > Meta Pixel > Open app to change the Pixel ID or replace the access token. To stop this integration's browser and server tracking, turn off Enable Meta Pixel and click Save. Disabling it does not remove events Meta already received, and it does not disable another copy installed through your theme or a tag manager.

Troubleshooting

• The settings form is unavailable: Confirm the app is installed for this store and that your staff role can manage its settings.
• Save is disabled: The form has no unsaved changes. Change the setting you intend to update before saving.
• The ID is rejected: Paste only the numeric Pixel ID, without script tags, spaces, or an ad account ID.
• No browser events arrive: Check the saved ID, Enable Meta Pixel, marketing consent, and browser extensions. Use a fresh visit to the actual storefront, rather than the admin page.
• Browser events arrive but server events do not: Confirm the token belongs to the same pixel, a test code is current when testing, and the order was paid. A browser-only setup has no access token and does not send server events.
• Purchases appear twice: Check for additional manual pixels or tag-manager tags before adding any more tracking code. Contact support with the order reference and event time; never send the access token.