Deduplicate the browser and server copy
Every browser event carries an event ID that the server copy reuses, which is the mechanism Meta uses to collapse the pair into one conversion instead of counting it twice.
Adscriptly Signals
A Conversions API that reports what the platform actually accepted.
Browser pixels lose events to blockers, ITP, and abandoned tabs. Adscriptly sends the same conversions from the server with hashed identifiers and a shared event ID, so the browser and server copies deduplicate instead of double-counting, and every delivery is logged with the platform response attached.
Product profile
DestinationsMeta CAPI, Google
DeduplicationShared event ID
EvidencePer-event delivery log
Built around the data, controls, and workflows already available in Adscriptly.
Core capabilities
What you can do with Adscriptly Conversions API.
Hash identifiers before they leave
Emails and phone numbers are normalized and hashed server-side, so raw contact details are never handed to a platform endpoint.
Survive blockers and short sessions
A conversion recorded server-side still arrives when the browser request is blocked, the tab closes early, or the outcome happens hours later in a CRM.
Keep the platform response
Each delivery stores what the platform returned, so a rejected batch is a line you can read rather than a number that quietly never appeared.
How it works
How your team sets it up and reviews the result.
- 01
Install once
Add the pixel to your site; the first origin to present the key claims the installation and starts collecting.
- 02
Name the conversions that matter
Define the events worth sending, and the qualification rules that decide which ones earn a place in the upload.
- 03
Connect the destination
Authorize Meta and Google, then map each event to the conversion action it should land on.
- 04
Watch the ledger
Review accepted, rejected, and pending deliveries per destination, and re-drive anything a platform refused.
Best fit
Who this is for.
iOS and blocker-heavy traffic
Recover the conversions a browser-only pixel silently drops on Safari and on any visitor running an ad blocker.
Lead gen with a delay
Send the qualified outcome when it happens in the CRM, still attached to the click that caused it.
Double-counted purchases
Stop reporting inflated conversion counts when both a pixel and a server integration fire for the same order.
Frequently asked
The practical questions.
What is the Conversions API?
It is a server-to-server way to send conversion events to an ad platform, instead of relying only on a tag firing in the visitor browser. Meta calls its version the Conversions API; Google exposes equivalent server-side conversion imports.
Will this double-count my conversions?
Not when the events are paired. The browser event and the server event carry the same event ID, which is how the platform recognises them as one conversion and keeps a single copy.
Do I still need the browser pixel?
Yes, in most setups. The pixel captures the click context and the browser signals; the server copy is what survives when the browser request does not. Together they cover more than either alone.
Is customer data sent in the clear?
No. Identifiers used for matching are normalized and hashed before the request leaves the server, which is what the platforms expect to receive.
Adscriptly Signals
Start using Adscriptly Conversions API.
Every plan starts with a free 7-day trial and 1,500 trial credits. Card required.