Server-side tracking implementation

We route key events through a Google Tag Manager server container hosted on Stape. GA4, Google Ads and Meta receive agreed data according to your consent settings.

Free review · implementation €250 + VAT

  1. Website

    purchase · transaction_id · value

    Event with order details

  2. Consent

    ad_storage · analytics_storage

    Consent Mode state travels with the event

  3. Web GTM

    siunčia į sgtm.jusudomenas.lt

    Google events use your subdomain

  4. Server container

    Stape · filtruoja · paskirsto

    In your Stape account, on your subdomain

What is server-side tracking?

The browser sends events to a container on your subdomain rather than directly to each platform. We usually host it on Stape, a specialist server-side GTM service. Events can be processed, unnecessary fields removed and agreed data added before forwarding to GA4, Google Ads or Meta. The website still uses a CMP and web GTM; Meta Pixel generally works alongside server events.

Browser-side measurementEach platform runs its own browser script and receives data directly.
Server-side trackingThe browser sends events to your subdomain; the server routes them onwards.

What a server container changes and what it does not

These limits affect whether the investment makes sense.

What changes

  • Control over data routing

    Routed events reach your server environment first. You decide which fields go to each platform and which remain.

  • Requests use your domain

    Your subdomain accesses the server container. Google recommends first-party domain deployment.

  • Meta receives server purchase events too

    Pixel and Conversions API can work together. Matching event_id and event_name values allow Meta to deduplicate browser and server events.

  • Fewer browser scripts may be needed

    Moving eligible tags can reduce third-party browser code. We measure the actual performance effect after implementation.

What does not change

  • Consent still applies

    Consent states reach the server and Google tags respond accordingly. Advanced Consent Mode may send cookieless signals to Google; basic mode blocks relevant Google measurement until consent. We configure consent conditions separately for Meta and other non-Google tags.

  • Incorrect source events remain incorrect

    Duplicate purchases or wrong values can be forwarded, so source measurement is checked first.

  • Not every action becomes measurable

    Visitors may block scripts or decline cookies. A server container does not remove these limits.

  • Sales do not increase automatically

    Better conversion data can inform budgets and optimisation, but sales still depend on campaigns, offers and the website.

When is implementation worthwhile?

Hosting and maintenance have costs, so we do not recommend it universally.

Consider it when

  • you regularly invest in Google Ads or Meta and allocate spend using conversions;
  • recorded ecommerce purchases differ from actual orders;
  • you need CRM or offline-sales signals in advertising platforms;
  • you need control over data shared with third parties.

It may be too early when

  • GTM and clearly defined conversions are not working;
  • advertising spend and conversion volume are small;
  • nobody will maintain or pay for hosting.
Start by improving Google Tag Manager

What we implement

Scope follows the measurement review. Typical components are below.

Measurement review and plan

Review web GTM, events, consent and duplicates, compare purchases or enquiries with orders/CRM and plan events and channels.

Server container on Stape

Create the GTM server container, host it on Stape and connect your subdomain through DNS. Choose a plan for request volume.

GA4 through the server

Route events through the container and verify required parameters reach GA4.

Google Ads conversions

Configure server-side Google Ads conversions and Conversion Linker. Enhanced Conversions are discussed where suitable data and consent exist.

Meta Conversions API

Send browser and API events with matching event_id values and check deduplication in Events Manager.

Consent transmission

Check that CMP consent states reach the server and tags behave accordingly. This does not replace legal compliance assessment.

Other channels, TikTok Events API, ecommerce platforms and CRM connections are separately scoped.

Trademarks belong to their owners and identify example technologies.

Pre-launch checks

We inspect important events in server Preview, checking consent, parameters and fired tags.

  • Consent state and tag behaviour
  • Order ID, amount and currency
  • Fired and unfired tags
  • Browser/server duplicates

Implementation process

  1. Free review

    Discuss conversion destinations and missing data, then review measurement. If server-side work is unnecessary, we say so.

  2. Plan

    Agree events, platforms and the Stape plan, then start after access is granted.

  3. Implementation

    Create container and hosting, connect the subdomain and configure agreed tags.

  4. Testing

    Test orders or enquiries under different consent states and verify each destination.

  5. Handover

    Document setup, transfer access and agree monitoring responsibilities.

How much does it cost?

The initial review is free. Implementation is €250 + VAT. You pay Stape directly for hosting; ongoing support is optional and separately priced.

Server-side tracking implementation250 €+ VAT

ComponentPaid toPricing basis
Measurement reviewSeoRocketFree before implementation
ImplementationSeoRocket€250 + VAT
Stape hostingStape, in your accountMonthly, based on request volume
MaintenanceSeoRocket, if selectedAdditional agreed fee

Stape's price list dated 17 October 2026 offers a free tier up to 10,000 monthly requests and Pro at USD 17/month on annual billing, up to 500,000 requests. Larger plans serve higher volumes. We estimate requirements from traffic and event volume, then confirm current vendor pricing. Stape pricing.

Server-side tracking FAQs

Ask a question

Does it bypass cookie consent?

No. The container receives the CMP's consent state, and transmission depends on configured conditions. Applicable consent requirements should be assessed with your legal or data-protection adviser.

Does it bypass ad blockers?

We do not promise that. Some allow subdomain requests; others recognise and block them. Lists change, so bypassing protections is not the implementation objective.

Where is data hosted?

We choose location during setup. Stape and Google Cloud offer EU hosting options. With a company-owned Stape account, the provider's processing terms apply to your company.

Must website code change?

Usually DNS and an accurate data layer are needed, especially for purchases. If your platform already supplies required data, code changes may be unnecessary. The review establishes this.

How long does implementation take?

We estimate after the free review, based on channels, platform, access and any developer support required.

Why do you usually use Stape?

Its specialist GTM hosting can reduce setup and maintenance work compared with a self-managed Google Cloud project. It offers a small free tier and tools such as logs. If company policy requires your own cloud environment, Google Cloud can be scoped instead.

Request a free measurement review

Send your website and advertising platforms. We will assess whether server-side implementation is useful. Implementation is €250 + VAT.