Server-Side Tracking: What It Is, the Best Platforms and What It Costs (2026)

Server-side tracking moves the job of reporting visits, carts and sales out of the shopper’s browser and onto a server you control. Instead of a dozen vendor scripts each sending data from the page, your site sends one stream of events to a server running on a subdomain of your store, and that server passes them on to GA4, Meta, Google Ads and anyone else you advertise with. This guide explains how that works, what it fixes and what it leaves alone, and what the hosting costs at your traffic. Prices checked 14 Oct 2026, each one on the provider’s own pricing page.

If you would rather have it built than read about it, our server-side tracking setup service covers the container, the conversion APIs, consent and testing, all in accounts you own.

Summary

• What it is: a tagging server, most often server-side Google Tag Manager, answering on a subdomain like data.yourstore.com. It receives your events and forwards them to each analytics and ad platform.
• Why stores do it: fewer events blocked by ad blockers or expired by Safari’s cookie rules, plus a direct line to Google Ads enhanced conversions and to Meta’s Conversions API.
• Hosting cost: $20 a month on Stape or €25 on TAGGRS for a small store, around $90 a month on Google Cloud Run at Google’s two-server minimum, and €90 upwards on Addingwell.
• Stape vs TAGGRS: the cheaper one changes with volume. TAGGRS has the lower list price from 500K to 3M and from 5M to 10M requests a month; Stape is lower below 500K and from 3M to 5M, and lists a plan up to 20M.
• Limits: it does not override a visitor’s consent choice, and it cannot repair events your site never sends correctly.

What server-side tracking is

In a standard setup every marketing tool loads its own script in the browser and reports straight home: the GA4 tag to Google, the Meta pixel to Meta, the TikTok pixel to TikTok. Server-side tracking puts a server of yours in between.

1. The browser sends one stream. A slim web container, or on Shopify the customer events system, sends page views, add-to-carts and purchases to your tracking subdomain.
2. The server container reads it. A server-side Google Tag Manager container receives each event and decides what every platform should get.
3. The server forwards it. Tags inside the container send the event on to GA4, the Meta Conversions API, Google Ads and any other platform with a server API.

Because the server answers on your own domain, the identifier cookies it sets are first-party cookies written in an HTTP response, not by JavaScript. And because every event passes through the container first, you can remove or hash data before a vendor ever sees it. Each platform receives only what the container chooses to forward.

Why stores move tracking to a server

Ad blockers

Most blockers work from lists of known tracking domains and scripts. Requests to google-analytics.com or connect.facebook.net are on those lists; requests to a subdomain of your own store usually are not. That is not a guarantee, because some blockers also match script names and URL paths, but a first-party endpoint brings back a share of the events the browser would otherwise drop.

Safari’s cookie rules

Safari’s Intelligent Tracking Prevention deletes cookies created in JavaScript after 7 days without user interaction on the site, and that is where browser tags keep their visitor IDs. A shopper who comes back after ten days looks brand new, and the sale is credited to whatever channel brought them back. A tracking server can set the ID in an HTTP response instead. WebKit caps those server-set cookies at 7 days too when it detects that the server is a third party behind a CNAME or a different IP address, so how the subdomain is connected to the host matters as much as which host you pick.

Conversion APIs feed the bidding

Meta and Google bid against the conversions they can see. Meta’s Conversions API accepts purchases from your server alongside the browser pixel; when both arrive with the same event name and event ID within 48 hours, Meta keeps one and discards the other. Google Ads enhanced conversions attach a hashed email address or phone number to each conversion so Google can match it to a signed-in account. Both can run from the server container, where the customer data is hashed before it leaves.

Control over what leaves your site

With vendor scripts in the browser, each vendor collects whatever its script collects. With a server container you choose: drop IP addresses before an event reaches GA4, hash emails before they reach Meta, and delete fields a platform has no use for. That makes privacy reviews shorter, and any tag you move entirely to the server is one less script on the page.

What it does not fix

• Consent. A visitor who declines in your cookie banner must not be tracked, server or no server. Consent Mode v2 passes each choice, including the ad_user_data and ad_personalization signals, to every Google tag, and the server tags must honour it as well.
• A broken data layer. If the site reports the wrong revenue, leaves out the order ID or fires the purchase twice, the server forwards the same mistake. Most of a setup is getting the events right, not running the server.
• Disagreement between platforms. GA4, Meta and Google Ads each count conversions under their own attribution rules, so their totals will still differ. Server-side tracking gives each of them fuller data; it does not make them agree.

How hosting is billed: requests, not visits

Nearly every host prices by requests, meaning each hit the browser sends to your tracking server. A page view is one, so is an add-to-cart, a scroll or a purchase, and some setups add a few more for the ad platforms. A typical store visit produces somewhere between 10 and 20.

The fastest estimate comes from GA4. Open Reports, then Engagement, then Events, take last month’s total event count and add about 20% for hits that only go to ad platforms. A store with 200,000 visits a month typically lands around 3 million requests.

Server-side tracking cost calculator

Drag the slider to your monthly requests or pick a store size. These are monthly list prices excluding VAT, shown in the currency each provider bills in.

The best server-side tracking platforms compared

Four of these host a server-side Google Tag Manager container, either for you or in your own cloud account. The other three sell tracking as a product and price it by events or orders. All figures were taken from the providers’ pricing pages on 14 October 2026.

Stape

A managed host for server-side GTM, billed in dollars. Pro costs $20 a month for 500K requests, Business $100 for 5M and Enterprise $200 for 20M, with custom plans above that and a lower monthly rate on yearly billing. Stape publishes no overage rate: outgrow a plan and you move up one. Its add-ons, such as the cookie keeper and bot detection, are the main reason to pick it over a cheaper host.

TAGGRS

A managed host billed in euros. Basic costs €25 for 750K requests, Pro €65 for 3M and Ultimate €145 for 10M, less on yearly billing. Check one setting before you sign up: when a plan’s limit is reached, TAGGRS stops forwarding data unless automatic upgrading is on, so a sale-day spike can leave a hole in your reports.

Addingwell

Billed in euros, free up to 100K requests, then €90 for 1M, €120 for 5M, €210 for 12M and up to €1,190 for 100M. There is no hard cap: extra traffic is charged at €1.30 to €2.30 per 100K requests at the end of the month. That makes it the dearest of the managed hosts at low volume and the most forgiving when traffic jumps. Extra containers, domains and regions cost more.

Google Cloud Run

Here you run the container yourself in Google Cloud. Google’s setup guide recommends at least two servers so an outage does not lose data, at about $45 a month each, which puts the floor near $90. Stape’s own estimate is about $40 a server, scaling to five or six servers and $240 to $300 a month on busy sites. Two things catch teams out: request logs can add a large charge above roughly a million requests a month, which is why Google suggests switching them off, and somebody has to own updates and monitoring.

Tracklution, Elevar and JENTIS

These sell tracking as a finished product rather than hosting for your own container. Tracklution has a free tier, and its Grow plan is €39.20 a month on yearly billing for 50K events, suited to small sites after conversion APIs with no GTM to manage. Elevar, now sold as Audiense Online, charges by orders: $225 a month for 2,000 on Core, $650 for 10,000 and $1,250 for 30,000, with a ready-made Shopify data layer and support included. JENTIS is enterprise software with no public prices, aimed at large European businesses with strict privacy review.

Stape vs TAGGRS

These two make most shortlists for managed hosting at a low price. Their plan limits do not line up, so which is cheaper depends on where your monthly requests fall:

Monthly requests	Stape	TAGGRS	Lower list price
Up to 500K	$20 (Pro)	€25 (Basic)	Stape
500K to 750K	$100 (Business)	€25 (Basic)	TAGGRS
750K to 3M	$100 (Business)	€65 (Pro)	TAGGRS
3M to 5M	$100 (Business)	€145 (Ultimate)	Stape
5M to 10M	$200 (Enterprise)	€145 (Ultimate)	TAGGRS
10M to 20M	$200 (Enterprise)	Enterprise, by quote	Stape lists a price

The order holds at any realistic euro to dollar rate. Past price, the two differ in what happens at the limit and what each plan includes. TAGGRS pauses data at the limit if automatic upgrading is off, while Stape expects you to move up a plan. Stape’s Business plan adds multi-zone hosting and 10 days of logs, which is worth having if a short outage would cost you a day of sales data. If you sit near a boundary, price the next plan too, because November traffic is not March traffic.

What we’d pick

Our default choice by volume, assuming nobody on your team wants to run Google Cloud:

1. Under 500K requests

   Stape Pro or TAGGRS Basic

   $20 or €25 a month, and either is plenty. Stape includes its cookie keeper, which helps Safari attribution.

2. 1M to 5M requests

   TAGGRS Pro or Stape Business

   TAGGRS is €65 up to 3M requests. Above that, or if you want multi-zone uptime and 10 days of logs, Stape Business at $100 covers up to 5M.

3. 10M requests and up

   TAGGRS Ultimate or Stape Enterprise

   €145 for 10M, or $200 for 20M with an account manager. Addingwell suits sites that would rather pay overage than hit a cap.

4. Shopify, no developer

   Elevar

   Several times the cost of hosting alone, but the tracking setup comes with it. Compare it with hosting plus a one-off setup.

Setting up server-side tracking on Shopify

Shopify adds one twist. Checkout pages no longer run your own scripts, so checkout and purchase events come from Shopify’s customer events (the Web Pixels API), which run in a sandbox Shopify controls. The order we work in:

1. Audit what fires today. List every tag, pixel and app that sends data, and where purchases are missed or counted twice.
2. Size the volume and choose the host. Monthly requests from GA4 as described above, then the plan that fits with headroom for peak season.
3. Point a subdomain at the tracking server. A DNS record such as data.yourstore.com, so the server and its cookies are first-party.
4. Send events from the storefront and checkout. A custom pixel subscribed to Shopify’s standard events, such as product_viewed, product_added_to_cart, checkout_started and checkout_completed, sends each one to the server with an event ID.
5. Build the server container. GA4, the Meta Conversions API, Google Ads conversions with enhanced conversions, and any other platform you buy ads on, all mapped from the same events.
6. Connect consent. Shopify’s customer privacy settings and your banner feed Consent Mode, and the server tags check consent before sending.
7. Test against real orders. Place test orders, watch GA4 DebugView, Meta’s Test Events and Google Ads diagnostics, then compare a week of tracked purchases with the orders in Shopify before the old setup is switched off.

Creating the server is the quick part. Getting every platform to count each sale exactly once is where the testing time goes. We run this as a fixed-price project; the scope is on our server-side tracking page. For the reporting tools that sit around it, see the analytics and tracking apps worth installing after GA4.

Questions people ask

What is server-side tracking?

A method of routing analytics and ad events through your own server, most often a server-side Google Tag Manager setup on a subdomain of your store, instead of letting each vendor’s script report straight from the visitor’s browser. The server forwards each event to GA4, Meta, Google Ads and other platforms.

Is server-side tracking worth it for a small store?

If you spend on Meta or Google ads, usually yes: hosting for under 500K requests a month is $20 on Stape or €25 on TAGGRS, and the conversion APIs it feeds are what those ad platforms optimise against. If you run no paid ads, GA4 in the browser is normally enough.

Does server-side tracking make a store GDPR compliant?

Not on its own. It gives you control over what each vendor receives, such as removing IP addresses or hashing emails, but you still need a lawful basis and a working consent banner, and the server has to respect each visitor’s choice. Ask your privacy adviser how it fits your own setup.

How much does server-side tracking cost?

Hosting, at list prices on 14 October 2026: from $20 a month on Stape or €25 on TAGGRS, about $90 a month on Google Cloud Run, and from €90 on Addingwell, rising with your request volume. The setup itself is a separate, one-off cost.

Which is cheaper, Stape or TAGGRS?

It depends on your volume. Stape has the lower list price below 500K requests a month and from 3M to 5M; TAGGRS is lower from 500K to 3M and from 5M to 10M. Above 10M, Stape lists a plan up to 20M while TAGGRS quotes.

Do I still need the Meta pixel with the Conversions API?

Meta recommends running both. The browser pixel and your server report the same events with a shared event ID, and Meta keeps one copy of each when the event name and ID match within 48 hours. Running both catches events that either route alone would miss.

Does server-side tracking work with Shopify checkout?

Yes. Checkout and purchase events come from Shopify’s customer events, which a custom pixel can subscribe to and send on to your tracking server, then to each platform.

Sources

Where each price in this guide comes from:

Technical documentation used in this guide:

• WebKit, Tracking Prevention in WebKit: the 7-day rule for cookies created in JavaScript, and the cap on cookies set by third-party servers behind a CNAME or another IP address.
• Meta, Handling duplicate Pixel and Conversions API events: matching on event name and event ID within 48 hours.
• Google, Server-side Tag Manager on Cloud Run: a minimum of two servers, about $45 a month each, and request logging charges.
• Google, Set up consent mode on websites: the ad_user_data and ad_personalization parameters.
• Google Ads Help, About enhanced conversions: hashed first-party data sent with conversions.
• Shopify, Web Pixels API standard events and Custom pixels: the checkout events a pixel can subscribe to.