Meta Conversions API setup

Nishchit adds no browser pixel — not a single line of JavaScript. Every event goes from the server. So there is no way to double count, and no “turn off the browser pixel” setting to hunt for.

What you need: admin access in Meta Business Manager, and Nishchit 1.4.0 or later.

1. 1

   Get the Dataset (pixel) ID

   Open Events Manager → on the left, Data sources → pick the dataset you advertise with. If there is more than one, check the name — send to the wrong one and the events still arrive, but no campaign learns from them.

   Under the name, the 15- or 16-digit number is the Pixel id. Copy it somewhere.

2. 2

   Create an access token

   Inside that same dataset: Settings → scroll down to the Conversions API section → Generate access token.

   The token is shown only once. Copy it now and paste it into Nishchit. If you lose it, you will have to make a new one.

   Meta changes its screen wording now and then. If you can't find the button, look for “Conversions API” on the dataset's Settings page — that section doesn't move.

3. 3

   Check whose name the token is in

   The Generate button creates a System user on its own and issues the token in its name. In Business Settings → Users → System users, check that your dataset is assigned to that user.

   A token in a person's name dies the moment they leave the business, and nobody notices until the reports go blank.

4. 4

   Get the Test event code — for testing only

   In the same dataset, the Test Events tab. At the top there is a code like TEST12345. Events sent with it show up on that screen straight away, and are not used for optimisation.

   Don't forget to clear the box before going live. While the code is in, your real sales stay marked as “test” too, and Meta learns nothing from them.

1. 5

   Check the module is switched on

   Nishchit → Features: Advertising events must be ticked. If it is off, the Advertising page still opens, but a note at the top says nothing is being sent from here.

2. 6

   Fill three boxes, then check

   Nishchit → Advertising → The connection.

   Pixel id

   The number from step 1. 15 or 16 digits.

   Access token

   The token from step 2. It is stored encrypted and never shown again. Save with the box empty and the old one stays.

   Test event code

   The code from step 4. Clear it before going live.

   Save, then press Check the connection. It asks Meta who owns the pixel — it writes nothing to your ad data, so press it as often as you like. If no answer comes back, the problem is the token, not the pixel number.

3. 7

   Decide when a sale counts

   The only decision on this page that needs real thought. With cash on delivery, an order being placed and the money coming in are not the same thing.

   When it sends	Who it's for	Watch out
   When the order reaches a statusDefault	Every COD shop	Pick the status in the box below — most shops keep Delivered, where the money is real.
   When the customer's record is good	Shops that want faster feedback	Sent the moment the order is placed, but only for numbers whose delivery record is above the rate you set (default 75%). Fraud check must be set up. With no record, it waits for the status.
   The moment the order is placed	Prepaid shops	This is what most plugins on the market do. With COD it teaches Meta to find people who order and then refuse at the door — and you pay for that lesson twice.

4. 8

   What it reports afterwards

   What Meta hears afterwards — the event name Meta receives when an order reaches each stage. Three by default: Delivered, Returned, Confirmed.

   These are your own names, not Meta standard events — search for exactly these names when you create a custom conversion in Ads Manager. Clear a box and that stage stops being sent.

   The trigger is the status type, not the raw status — so renaming “Delivered” to something else won't break it.

5. 9

   If you need them: a separate pixel, and excluded pages

   A different pixel for some pages — to measure a funnel on its own pixel, make a rule from part of the page address. The order remembers the page the customer came in through, so that decides which pixel it goes to. If the rule has no token of its own, the shop's token is used.

   Pages never tracked — one piece of an address per line. Orders from these pages go to no pixel at all.

   Whatever you type in both places is a piece of the address, not a regular expression. A dot means a dot, nothing more.

With the Test event code in place, place an order, then look at Meta's Test Events screen — it should arrive within seconds.

Then Nishchit's own log: at the bottom of the Advertising page, What has been sent. Every order has one of four states.

The seven-day limit is Meta's, not ours. Meta does not accept events older than seven days — it returns Invalid parameter, and people then start fiddling with the token for no reason. So older rows have no Send again button at all; this note is written in its place. The log is kept for 14 days.

• Going live with the Test event code still in. The most common one. Events are going, you can even see them, yet no campaign is learning anything.
• Choosing “the moment the order is placed” in a COD shop. The bigger numbers are tempting. But you are paying to teach Meta who orders and then turns the parcel away at the door.
• Sending to the wrong dataset. If you have more than one pixel, press Check the connection and see whose name comes back.
• A token in a person's name. When they leave the business, the token dies. Use a System user token.
• held showing up, and panicking. That is normal — once the order is delivered it turns sent on its own.