Track every event.
Power every result.

Events leave from a server

Conversions are sent through the Conversions API, the Events API and the Measurement Protocol. An ad blocker in the browser has nothing to block, because nothing is being sent from the browser.

Collection on your own domain

The script and the cookies live on a subdomain of your store, not on ours. Cookies set this way are first-party, so Safari keeps them for two years instead of seven days.

A graph, not a single session

Customers are linked by a hash of their phone number, so a returning visitor is recognised across devices. Browsing events go out with the identity we already know, not with an empty payload.

The ad link survives the visit

The click identifier appears in the address bar exactly once, on landing. We store it for 90 days and attach it to every later event, so a purchase three weeks after the click still credits the ad.

Every event is auditable

Each order shows which events were sent, to which platform, and the exact reply that came back. When a platform rejects something, you see its reason, not a generic failure.

Bots never reach your pixel

Automated traffic is scored on arrival and dropped before it consumes your quota or distorts your conversion data — with the reason recorded, so the filter is never a black box.

What happens without server-side tracking

• The order is created through the API, so no checkout page loads and the pixel never fires a purchase.
• Meta sees browsing but no conversions, so it optimises toward the wrong people.
• Refused and undelivered parcels are still counted as revenue, because the platform never learns what was actually paid for.

What NDA Signal does instead

• The purchase is reported from the order webhook, which fires whether or not a checkout page was ever shown.
• Identity comes from the order form itself — name, phone and address — hashed before it leaves, giving a far higher match quality.
• You can report on collected revenue, not just placed orders, and see which campaign brought the parcels that were actually paid for.

As soon as the order is placed

The conversion is reported the moment the form is submitted. The platform starts optimising immediately, on the largest possible volume. The trade-off: refused and undelivered parcels are reported as revenue too, so the algorithm learns from buyers who never paid.

After phone confirmation

The purchase goes out once your agent confirms the order by telephone. Most fake and duplicate orders are gone by then. The trade-off: a delay of a few hours, and orders you never manage to reach on the phone are never reported at all.

On delivery

Nothing is reported until the courier marks the parcel as delivered. Every conversion the platform sees is money you actually collected. The trade-off: a delay of several days, which slows down learning on campaigns that are still fresh.

Report early, then send the adjusted value

The purchase is reported at once, and when the parcel comes back refused we send the correction, so the reported revenue drops back to what was really collected. The trade-off: your platform reports move after the fact, which takes some getting used to.