Data Foundations · Server-Side & CAPI

Server-Side Tracking & Conversions API for eCommerce

We set up server-side tagging, Meta Conversions API and Google enhanced conversions so your ad platforms receive more complete, better-matched purchase signals, without double counting and without ignoring the consent your visitors gave or refused.

  • GTM server containers
  • Meta CAPI with deduplication
  • Google enhanced conversions

The problem it solves

Browser-only tracking loses signal your ads need

Ad blockers, privacy-focused browsers and limits on cookie lifetime mean a share of real purchases never reaches Google Ads or Meta from the browser. Bidding systems then learn from an incomplete picture: campaigns that drive returning buyers look weaker than they are, and audiences built on purchasers shrink.

Server-side tagging moves part of that work from the visitor's browser to a server you control. It improves delivery and matching, and it gives you control over exactly what data leaves your site. It does not replace a correct browser setup, and it is not a way around consent.

How it works

One first-party endpoint, then you decide what each platform receives

Your site sends events to a tagging server on a subdomain of your store, such as a Google Tag Manager server container. That server forwards them to GA4, Google Ads, Meta and others. Because requests go to your own domain, they're blocked less often, and you can remove or reduce fields before anything is passed on.

  • GTM server container on Google Cloud or a managed tagging host
  • Your own subdomain for first-party requests
  • Fields stripped or reduced per destination, such as full URLs or IP detail
  • Purchases sent with the same event ID as the browser event for deduplication

What we implement

The server-side pieces, matched to your stack

GTM server container

Provisioned, mapped to your subdomain and connected to your web container, with monitoring so you know if it stops receiving events.

Meta Conversions API

Purchases and key funnel events sent server-side, paired with the Pixel and deduplicated, with match quality checked in Events Manager.

Google enhanced conversions

Hashed first-party data, such as email, sent with the purchase conversion so Google Ads can match more orders, only where consent allows.

GA4 via the server

GA4 events routed through your container, with a clear rule for which purchases come from the browser and which from order data.

Native integrations first

On Shopify, the Facebook & Instagram and Google & YouTube apps offer server-side and enhanced conversion options. Sometimes that's the right answer.

Other platforms

TikTok, Pinterest and other APIs added through the same container once Google and Meta are stable.

Deduplication

The part most server-side setups get wrong

When the browser Pixel and the Conversions API both report the same purchase, Meta needs to know it's one order. It deduplicates when both events share the same event name and the same event ID. If the IDs don't match, or one side sends none, the order can be counted twice, and Meta learns from inflated results.

Google Ads deduplicates purchase conversions by transaction ID, so every purchase must carry the store's order number, and it must be identical across browser and server.

What we check before go-live

  • The same event ID generated once in the browser and passed to the server event
  • Transaction IDs that match store order numbers exactly
  • Meta Events Manager showing events received from both sources and deduplicated
  • No second purchase sender left behind in an app or the theme
  • Event Match Quality reviewed, with hashed identifiers sent only where consent allows
Consent still applies. Server-side tagging changes where data is processed, not whether you may collect or share it. We pass your CMP's consent state and Global Privacy Control opt-outs to the server container, and tags respect them there too. Confirm with your counsel which data you may share with each platform.

Better signals, then better targets

Check what your ads earn after margin

Cleaner purchase signals pay off fully when bidding targets profit, not revenue. Enter your numbers below to see profit on ad spend, or work it out with the break-even ROAS calculator.

POAS Calculator

Profit on ad spend: what your ads return in gross profit, not just in revenue.

Example values. Replace them with your store's numbers.

Last 30 days, all ad platforms.

Revenue the platforms credit to those ads.

As a % of revenue, or the total in dollars.

Total for the same orders.

As a % of revenue.

Your POAS
—
 
Enter your numbers
Gross profit from ads
—
Profit after ad spend
—
ROAS, for comparison
—
How it's calculated
  • Gross profit = Revenue − COGS − Shipping & fulfillment − Payment fees
  • POAS = Gross profit ÷ Ad spend (above 1.00 = profit)
  • Profit after ads = Gross profit − Ad spend

 

Take these numbers into the Free Profit Audit

Calculated in your browser. Nothing you enter is stored or sent.

Related services

Server-side works best on a clean foundation

A server container forwards what your data layer and web container send it, so we fix those first. A Data Health Check shows whether you're ready. Consent setup is covered under Consent Mode v2, and paid strategy under profit-based bidding. Part of Data Foundations, mostly on Shopify and also WooCommerce and Magento.

FAQ

Server-side tracking and CAPI questions

What is server-side tracking?

It's a setup where your site sends tracking events to a server you control, usually a Google Tag Manager server container on your own subdomain, and that server forwards them to GA4 and ad platforms. Requests are blocked less often, and you decide what data each platform receives. It complements browser tracking rather than replacing it.

Do we need Meta Conversions API on Shopify?

Meta recommends using the Conversions API alongside the Pixel, and Shopify's Facebook & Instagram app can send server events for you. Many stores start there. A custom setup through a server container makes sense when you need more control over event data, consistent deduplication across platforms, or a single place to apply consent rules.

Does server-side tracking get around ad blockers and consent?

It makes delivery more reliable for visitors who are tracked legitimately, because requests go to your own domain. It must not be used to track people who declined consent or opted out. We pass consent and Global Privacy Control signals to the server so tags respect them there too.

What are Google enhanced conversions?

Enhanced conversions send hashed first-party data, such as the email used at checkout, along with the conversion. Google matches it to signed-in accounts to attribute more conversions accurately. Data is hashed with SHA-256 before it's sent. We enable it only where your consent setup allows ad data use.

Is server-side tagging worth it for a smaller store?

It adds hosting and maintenance. For stores with modest ad spend, fixing browser tracking and using native Shopify integrations often captures most of the value. Server-side becomes worth it as spend grows, when you run several ad platforms, or when you need tight control over data sent to vendors.

Send your ad platforms signals they can learn from

Start with the free audit to see your tracking and consent health, or book a call to scope a server-side setup for your store.

Free Profit Audit