Server-side tracking

Recover the conversions the browser throws away.

Archon Signal is a server-side tracking service for marketing agencies that recovers the 15 to 40% of conversion signals lost to ad blockers and browser restrictions.

Request a free audit →

Archon Signal at a glance

The signal never makes it back.

Safari and iOS clear cookies in one to seven days. Ad blockers strip 30 to 40% of events before they leave the browser. What reaches Google and Meta is a fraction of what actually happened.

The platforms then optimize on that fraction. Enhanced conversions, CAPI and customer match all quietly underperform, not because the strategy is wrong, but because the data feeding them is thin.

The same campaign week counted twice. Left, the conversions as the ad platform reported them. Right, the same week measured server-side, with the missing slice broken out into ad blockers, Safari and iOS. Consent refusals are shown above both bars as permanently out of reach. Figures in the image are illustrative.

How it works

Three steps, no mystery.

Audit the leak

We measure how much signal each client account is losing and where.

Move it server-side

A first-party server container that browsers and blockers can’t strip.

Verify and monitor

Enhanced conversions and CAPI confirmed live, then watched for drift.

What you get

Deliverables, not slideware.

First-party server-side container, configured per client

Adblocker-proof and Safari-proof event collection

Enhanced conversions, CAPI and customer match wired up

First-party cookies extended to 400 days

Server-side consent handling that respects Consent Mode

Documented event schema your team can read

One conversion following two routes. Browser-only tagging stops at the browser boundary because the request to a third-party domain is never sent. Server-side collection sends the same event to a host you control first, then on to Google Ads, GA4 and Meta.

Numbers we can stand behind.

15–40%

of lost conversion signals recovered

400 days

first-party cookie life, vs 1–7 in the browser

30–40%

of events ad blockers strip before Archon

Questions

What agencies ask about it.

We already use Stape. Why would we need you?

Running a server-side container isn’t the same as configuring it right. Most setups we audit leak enhanced conversions, misfire consent, or double-count events. We fix the configuration, not the tool.

Is this compliant?

Yes. Server-side collection runs alongside Consent Mode v2, so measurement respects consent. Compliance and recovery are two sides of the same setup, not a trade-off.

Will this break our existing GA4 and Ads setup?

No. We run the server-side path in parallel and validate every conversion against the current setup before anything is switched over. Nothing goes live unverified.

How long does implementation take?

A typical client account is live in one to two weeks after the audit, depending on how many platforms and conversions are in play.

What it does not do.

It does not make your data complete. Consent refusals, blocked requests and plain network failure always remove a share of events. The honest ceiling on any collection setup is around 95%, and that is a ceiling rather than a promise.

It does not fix a campaign that is not working. Recovering signal changes what the bidding algorithm can see, not whether the offer, the creative or the price is right.

It does not replace your analyst. It gives them numbers worth analysing, which is a different job.

It is not a migration. Google Ads, GA4 and Meta stay exactly where they are, they just start receiving events that used to go missing.

The thinking behind it.

Meta conversions dropped suddenly, what happened?

Spend held. The client's own order count held. Meta fell anyway. That is a measurement break wearing a performance break's clothes.

July 31, 2026

Does server-side tagging slow down your site?

The Core Web Vitals objection, answered honestly: what really leaves the browser, what stays, and when a container costs you speed.

July 31, 2026

How does server-side tracking actually work?

One conversion traced from the browser to the ad platform, and the three hops that decide whether a migration pays off.

July 31, 2026

Why your data breaks when checkout lives on another domain

The checkout domain shows up as a traffic source, sessions double, and Google Ads disagrees with the order table. Here is why.

July 31, 2026

Terms that come up in this work

Server-side tracking

Data layer

Enhanced conversions

Conversions API (CAPI)

Event deduplication

Where teams go next.

First-party analytics

Archon Pixel

First-party analytics straight to BigQuery.

Explore Archon Pixel →

Consent & compliance

Archon Consent

Consent Mode v2, compliant without the data loss.

Explore Archon Consent →

The next step

See what you’re losing.

We map where conversion data goes missing across your client accounts, and show what recovering it would be worth. Not a demo, not a sales call.

Request a free audit →