# Server-side tracking

What server-side tracking is, how Zernio turns it on for a website in one click, and what reaches your ad platforms.

Server-side tracking sends your website's sales, leads and signups to your ad platforms from a server, not only the browser. Zernio sets it up from your store and ad accounts in one click.

## What a pixel is

A pixel is a script from an ad platform that runs on your site, in each visitor's browser. When the visitor views a product, adds to cart or buys, it reports that to the platform.

The platform uses those reports twice: to show you which ads earned sales, and to find more people like your buyers. Fewer reports means worse numbers and worse targeting.

## Why pixels miss conversions

A pixel only works if the browser lets it. Four things stop it:

| What stops it | What happens |
|---|---|
| Ad blockers | They block requests to known ad domains, so the pixel's report never leaves the browser |
| Safari and other privacy rules | Cookies set by scripts expire after 7 days, sometimes 24 hours, so a returning buyer looks new |
| Closed tabs | A visitor who leaves before the thank-you page loads is never reported |
| Consent | A visitor who refuses tracking is rightly left out, in every setup |

Vendors put the loss at 20 to 40% of conversions. It varies with your audience: more Safari and more blockers, more loss.

## How a sale finds its ad

When someone clicks an ad, the platform adds a click id to your link, such as `gclid` for Google or `fbclid` for Meta. It is the proof the visit came from that ad.

The id has to survive until the purchase, which can be days later. If the cookie holding it expires, the sale is reported but credited to no ad.

<ClickIdFlow />

## What server-side tracking adds

With server-side tracking, the browser sends each event once, to a collector on an address you control. The collector sends it on to each platform's server API, such as Meta's Conversions API.

<TrackingFlow />

| | Browser pixel | Zernio |
|---|---|---|
| Sent from | The visitor's browser | Zernio's servers |
| Ad blockers | Blocked as an ad domain | Sent to your own address |
| Click ids | Kept in short-lived browser cookies | Kept and restored by the collector, longer on [your own subdomain](/products/server-side-tracking/custom-subdomain) |
| Consent | Depends on each pixel's setup | Applied the same way for every platform |
| Platforms | One script each | One tag for all of them |

## Pixel and server together

Keep your pixels. The platform then receives each conversion twice: from the pixel and from Zernio. Both carry the same event id, so it [counts once](/products/server-side-tracking/deduplication).

Server-side tracking never sends what a visitor refused. It recovers conversions from visitors who agreed, which blockers and cookie limits would have lost.

## What it does not fix

- **Cross-device journeys.** A click on a phone and a purchase on a laptop link only when the buyer is identified, for example by email.
- **View-through conversions.** Sales from people who saw an ad without clicking stay with each platform's own modelling.
- **Exact matches with your store.** Platforms credit sales their own way, so their totals and your orders will differ.

## How it works

1. **A tag on your site** records page views and conversions, and keeps the ad click that brought the visitor.
2. **Zernio's collector** receives them on a first-party address, drops bots and applies the visitor's consent.
3. **Each conversion goes to your ad accounts** from Zernio's servers, with the same event id as your browser pixel, so it is [counted once](/products/server-side-tracking/deduplication).
4. **It is also stored** as an event with source `web`, so it counts for its campaign in [campaign results](/guides/campaign-results) and [ad rules](/guides/ad-rules).

## Get started

1. **Connect your ad accounts**, and your store if you have one.
2. **Open Ads, then Conversions, then Sources**, and click **Turn on** for your website. [Install the tracking tag](/products/server-side-tracking/install) covers every way in.
3. **Check the ticks.** Each ad account shows a tick once it is linked. [Test and verify](/products/server-side-tracking/verify) shows how to see the first events on each platform.

## What the one click does

Clicking **Turn on** for a connected store does the whole setup. You choose nothing:

| Step | What Zernio does |
|---|---|
| Site | Creates it from the store: its address, its platform host and your profile |
| Tag | Installs it through the store's own app, or publishes it in your Tag Manager container |
| Ad accounts | Links each ad account you picked when you connected the platform, to its purchase pixel or conversion action |
| Missing destination | Creates one: a **Zernio** pixel on Meta, a **Purchase (Zernio)** conversion action on Google Ads |
| Events | Captures purchases, checkouts and carts on Shopify, and page views everywhere |
| Consent | Follows your banner's Google Consent Mode, with EU visitors opted out until they choose |
| Checks | Ticks the tag and each ad account as they finish |

Every setting has a default you can change later and none is required.

## Choose how to install

| Your site runs on | Install with |
|---|---|
| Shopify, WooCommerce, Wix or Webflow | [One click on the store](/products/server-side-tracking/install#install-on-a-connected-store) |
| Any site with Google Tag Manager | [One click on the container](/products/server-side-tracking/install#install-with-google-tag-manager) |
| Anything else | [One line in the page](/products/server-side-tracking/install#paste-the-line) |

## What reaches your ad platforms

Every page view is collected for your traffic. Conversions are what reach your ad platforms, under these names in any case:

| You send | Sent to ad platforms as |
|---|---|
| `Purchase`, `purchase` | `Purchase` |
| `Lead`, `generate_lead` | `Lead` |
| `CompleteRegistration`, `sign_up` | `CompleteRegistration` |

On Shopify, purchases are captured for you. On any other site, send them from your order confirmation page with [`zernio('track', 'Purchase', …)`](/products/server-side-tracking/script#track-an-event).

How each platform receives them, and which customer data it reads, is on [Platforms](/products/conversions-api/platforms).

## What to expect

- **Numbers will not match your store exactly.** Visitors who refuse consent, bots and test orders are left out, and each platform credits conversions to its own ads its own way.
- **Platforms show events with a delay.** Meta shows them within about 20 minutes. Google Ads can take a few hours, and its diagnostics a few days.
- **Consent lowers the count in Europe.** Under the default [consent](/products/server-side-tracking/consent) setting, EU visitors who make no choice are counted but not sent.
- **Your pixels can stay.** Keep them for audiences and the platform's browser signals. Zernio's copy is deduplicated against theirs.

## How it behaves

- **First-party.** The tag keeps the visitor and click ids on your own domain. A [custom subdomain](/products/server-side-tracking/custom-subdomain) also sets them as server cookies.
- **Bots stay out.** Known crawlers, AI agents and headless browsers are counted apart and never forwarded.
- **Only your domains.** Events from a page outside the site's `domains` are dropped.
- **Never breaks your site.** An unknown or removed site gets an empty script, and the collector never answers with an error the page sees.
- **Backend sales too.** Sales that never touch the browser, such as a renewal or a phone order, go through [`POST /v1/events`](/products/conversions-api), and Zernio [joins them to the visit](/products/server-side-tracking/backend-events) that brought the customer.

## Related

- [Install the tracking tag](/products/server-side-tracking/install)
- [Choose the ad accounts](/products/server-side-tracking/ad-accounts)
- [The tracking script](/products/server-side-tracking/script)
- [Test and verify](/products/server-side-tracking/verify)
- [Conversions API](/products/conversions-api)