Connect your Meta pixel to Nevian

Time needed: about 5 minutesLast updated:

Let Nevian send each sale to your Meta pixel from its server (Conversions API), with the data of the original click, so Meta sees the sale even when the browser blocks the pixel.

What you need

  • A Meta pixel in Events Manager and developer access to its business: Meta shows the token link only to people with developer privileges.
  • A Nevian workspace with an active plan (Beginner, Pro or Enterprise), where you are the owner, an admin or a member.
  • Already connected your Meta ad accounts? Then you can skip the token: see step 1. If not, have Events Manager open in another tab.

Steps

  1. In Nevian, open Pixels, click Add pixel when needed and pick Meta. Choose Use your connected Meta account to select a connection and pixel without a token, then click Connect and continue at step 5. Otherwise choose Paste a Conversions API token and click Open Events Manager.

    The Connect Meta pixel window offering a connected Meta account without a token, or a Conversions API token.

  2. In Events Manager, open Data sources, choose your pixel and select the Settings tab. Copy the Pixel ID.

    The Settings tab of a pixel in Meta Events Manager, with the Pixel ID highlighted.

  3. On the same tab, find the Conversions API section and click Generate access token under Set up manually. Follow Meta's window and copy the token it shows.

    The Conversions API section of the pixel's Settings tab, with the Generate access token link under Set up manually highlighted.

  4. Back in Nevian, click Next. Paste the Pixel ID and the Access token, then click Connect.

    The second step of the Connect Meta pixel window, with the Pixel ID and access token filled in and the Connect button highlighted.

  5. In Events Manager, select the pixel's Test Events tab and copy the test code Meta shows there.

    The Test Events tab of the pixel in Meta Events Manager, with the test code highlighted.

  6. In Nevian, open the pixel (Pixels › Meta, then Open) and click Send test event. Paste the code in Test event code and click Send test event. The panel shows Meta received 1 event.

    The Send test event panel in Nevian with the test code, the line Meta received 1 event and the Send test event button highlighted.

Check that it works

  • In Events Manager, the Test Events tab lists the event within a few seconds.
  • From then on, each approved sale goes to Meta with the data of its click. The pixel's page in Pixels shows every delivery and its match quality, and Logs › Pixel events keeps each request.
  • Meta keeps events sent with a test code in Events Manager, so send one test, not a series.

Problems

"Meta rejected the test event"

The line below it shows Meta's reason. Most of the time the token belongs to another pixel or was copied incomplete: generate a new one in the pixel's Settings, then open the pixel in Nevian, click Edit, paste the new token in Access token and click Save changes.

"Enter the pixel ID, only digits."

Paste only the number shown as Pixel ID in the pixel's Settings, with no name or spaces.

"No pixel is shared with this connection."

Your connected Meta account can't see any pixel. Give it access to the pixel in your Meta business settings, or click Paste a Conversions API token instead and follow steps 2 to 4.

Meta shows it only to people with developer privileges for the business. Ask an admin of the business to give you that access, or to generate the token for you.

Purchases counted twice in Meta

If your checkout also sends purchases to the same pixel from its own server, Meta receives each sale twice. Turn off the checkout's Meta pixel integration and let Nevian send them.

Still stuck? Write to [email protected].

Images are drawings of Meta's and Nevian's screens, not screenshots; the real screen may look a little different.