Destinations / Conversion Signals
Send observed server-side conversions to supported ad platforms
Deliver first-party and server-observed conversions to Google, Meta, TikTok, and Snap — with the identifiers, values, and deduplication each platform needs, and a status record for every send.
The problem
Browser pixels do not observe every conversion your business records
Purchases, qualified leads, and offline outcomes land in your backend or CRM even when no browser event reaches the ad platform. That missing signal starves the algorithms that spend your budget — Vendo delivers it, mapped correctly, straight to the platform.
Advertising destinations
One workflow, supported ad platforms
Vendo handles each platform's event and identifier requirements — see the integration catalog for the details.
What the conversion-delivery workflow handles
From payload to platform — Vendo does the mapping, deduplication, and delivery so you don't maintain scripts.
Server-side delivery
Send conversions straight to the destination API — ad blockers and browser limits can’t touch them.
Deduplication fields
Stable event identifiers let each platform recognize duplicates, so your pixel and server events don’t double count.
Documented conversion logic
Every workflow records its event, value, currency, attribution rule, and time window — no mystery numbers.
Destination-specific mapping
Send exactly the identifiers and fields you choose, in the format each platform requires.
Four steps from source event to platform
Set up the source event, mapping, and identifiers once — then deliveries run on schedule with a visible result.
Collect the conversion event
Start from events your business observes directly — an order, a qualified lead — from first-party or server-side sources.
Map destination identifiers
Map click identifiers and customer fields to what each platform expects — Vendo handles the format differences.
Set the event identity and attribution fields
Set stable event identifiers so platforms deduplicate against your pixel, and choose the attribution fields you need.
Send and inspect the result
Run the delivery job and watch its status. Backfill historical or offline events within each platform’s accepted windows.
Common gaps in a browser-only setup
- A browser request can fail or never contain an outcome that is recorded later on the server.
- Web and server copies may be double counted without a shared event identifier.
- Offline and CRM outcomes never make it to the platform at all.
- Platform-reported conversions may not match the business transaction record.
What the Vendo workflow adds
- A documented mapping from your source event to the platform's event.
- Stable event identifiers so platforms deduplicate against your pixel.
- Historical and offline delivery within platform windows.
- A job record showing whether every delivery succeeded or failed.
How it works
Map, deliver, and record every event
Vendo builds the payload from your source fields, sends it to the destination, and adds stable event identifiers so the platform deduplicates against your pixel.
You stay in charge of what the event means, which identifiers to send, and how to measure the impact — Vendo handles the plumbing.
New to server-side signals? Start with the server-side tracking and conversion APIs guide.
Signal flow
FAQ