IndiSell Docs Dashboard →
Grow revenue

Set up Meta Pixel & Conversions API

Where to find your Meta Pixel ID and Conversions API token, and how IndiSell deduplicates browser and server events.

IndiSell fires purchase events to Meta both in the browser (Pixel) and server-side (Conversions API), deduplicated by order id — so you get CAPI's reliability without double-counting.

What IndiSell needs

IndiSell field (Conversions → Meta)What it isLooks like
Meta Pixel IDYour pixel/dataseta 15–16 digit number
Conversions API access tokenAuthorises server-side eventsa long token
Test event code (optional)For verifying setupTEST12345

Step 1 — Pixel ID

1
Open Events Manager

Go to Meta Events Manager and select your Pixel / Dataset (create one via Connect data sources → Web if you don't have it).

2
Copy the ID

The Dataset ID (a.k.a. Pixel ID) shows under the dataset name — a long number. Paste it into Meta (Facebook) Pixel ID.

Step 2 — Conversions API token

1
Settings → Conversions API

In the dataset, open Settings → scroll to Conversions API → Generate access token.

2
Copy the token

Copy it once (it's shown once) and paste into Conversions API access token in IndiSell. It's encrypted at rest.

Step 3 — Verify (optional)

1
Grab the test code

Events Manager → your dataset → Test events tab → copy the Test event code (TESTxxxxx).

2
Paste & place a test order

Put it in Test event code, place a test order, and watch it appear in the Test events tab. Remove the code when you're done.

💡
Because IndiSell sends the Pixel and CAPI events with the same order id, Meta deduplicates them automatically — you won't see inflated purchase counts.
ℹ️
Server-side events include the OTP-verified phone (hashed), which improves Meta's match quality — the same advantage that makes IndiSell's Google enhanced conversions strong.