# Choose how to send conversions

Connected sources, the website tag, POST /v1/events and tracking links compared: what each needs, what it reaches and how reliable it is.

Conversions reach Zernio four ways. Most setups combine two: the website tag for what happens on the site, and your server for what happens after.

## The four ways

| Way | You build | Counted per campaign | Sent to ad platforms | Reliability |
|---|---|---|---|---|
| [Your server](/products/conversions-api/send) (`POST /v1/events`) | One API call per event | Yes | Yes | Highest: no browser in the way |
| [Website tag](/products/server-side-tracking) | Nothing on a store, one tag elsewhere | Yes | Yes | High: first-party, but needs ad consent |
| [Connected source](/products/conversions-api#by-connecting-accounts-with-no-code) | Nothing: connect the account | Yes, when tied to an ad | Stripe and Salesforce only | High for the sale, low for its ad |
| [Tracking link and postback](/products/server-side-tracking/tracking-links) | A link, and a postback URL at the network | Yes | No | High: server to server |

## Your server

Send from your backend what only it knows: a paid invoice, a qualified lead, a trial that converted. Nothing a browser blocks can lose it.

Your server rarely knows the ad click. Send the tag's visitor id (`user.visitorId`) with each event, and Zernio adds the visit's click ids. See [Backend events](/products/server-side-tracking/backend-events).

## Website tag

The tag records page views, sign-ups and purchases on the site, captures each ad click id, and sends the events from Zernio's servers. Ad blockers that stop a pixel let it through.

It respects your cookie banner. A visitor who refuses ad cookies is counted in totals, but not sent to ad platforms.

## Connected source

Lead forms, stores, Stripe, HubSpot and Salesforce report their results once connected. You write nothing, and nothing is missed.

A store or a payment rarely knows which ad sold it. Such a sale counts in totals but not for a campaign, unless it carries a UTM tag or click id.

## Tracking link and postback

For affiliate offers and traffic you send off your site. The link records the click, and the network reports the sale back by postback, with no tag on the offer page.

Postback conversions count for the link's campaign. They are not sent to ad platforms yet.

## Which to use

| You run | Use |
|---|---|
| A store on Shopify, WooCommerce, Wix or Webflow | The website tag, installed in one click. It covers purchases and counts each one once |
| A SaaS or app with sign-ups and payments | The website tag for sign-ups, and your server for trials, payments and upgrades, with the visitor id |
| Lead generation with a CRM | Lead forms connected, plus HubSpot or Salesforce for leads that become deals |
| Affiliate offers | Tracking links and postbacks |

## How it behaves

- **One event, one id.** When the tag and your server both report a sale, send the same `eventId`. See [Deduplication](/products/server-side-tracking/deduplication).
- **Every way lands in one place.** `GET /v1/events` lists events from every source, and `source` says which.

## Related

- [Conversions API overview](/products/conversions-api)
- [Send events](/products/conversions-api/send)
- [Server-side tracking](/products/server-side-tracking)
- [When numbers don't match](/products/conversions-api/numbers)