Setting up Facebook Pixel and the Conversions API

When you advertise on Facebook, you need to know which ads actually sell. Nimeshe runs both the Facebook Pixel and the Conversions API (CAPI) — purchases are reported from the browser and the server, so they aren't lost to ad blockers or iPhones, and Facebook counts each sale only once.

Events that are sent

Purchase is also sent from the server, which makes your ad reporting more accurate.

1. Get your Pixel ID

1. Go to Meta Events Manager.
2. Pick your Pixel (dataset), or create one.
3. Copy the 15–16 digit Pixel ID under its name.

2. Get a Conversions API token

1. In Events Manager, open the same Pixel and go to Settings.
2. Under Conversions API, click Generate access token.
3. Copy the long token. It's only shown in full once, so keep it safe.

3. Add them in Nimeshe

1. In your admin, open Tracking & Ads.
2. Enter the Pixel ID in Facebook Pixel ID.
3. Paste the token in Conversions API Token.
4. Click Save. It's live on your store at once.

4. Test it

1. In Events Manager, open Test events and note the test event code (e.g. TEST12345).
2. Enter it in Test Event Code in Nimeshe and save.
3. Click Send Test Event. "Facebook received the event ✓" means the connection works.
4. Open your store, view a product and add it to the cart — check the events appear under Test events.

Google Analytics 4 (optional)

To see where visitors come from, enter your Google Analytics Measurement ID (starts with G-) in Google Analytics 4 Measurement ID on the same page.

FAQ

The Pixel works but Purchase doesn't show.

Check the Test Event Code is empty and the token belongs to the same Pixel. Then place a real test order — it can take a few minutes to appear in Events Manager.

How do I change the token?

Paste the new token and save; it replaces the old one. Remove Token stops server events, leaving only the browser Pixel.