Proper Conversion
to stop wasting ad spend
and increase sales↗ 5X

Every time a shopper on Safari or an iPhone lands on your store, there's a good chance the browser silently blocks or truncates the tracking scripts that feed your ad platforms. Add a mainstream ad blocker on top, and a meaningful share of your purchases never reach Google Ads, Meta or GA4 at all.

The result is familiar: your ad platform reports fewer conversions than your store actually made, its algorithm optimizes toward incomplete data, and your cost per acquisition climbs even though nothing about your product or offer changed.

Server-side tracking moves the data collection off the browser and onto a subdomain you own — for example, tracking.yourstore.com. Events still fire in the browser, but they're forwarded to your own server endpoint, which cleans them up and passes them on to the ad platforms through their official server APIs.

Because the request leaves your first-party domain, ad blockers that target third-party tracking scripts don't see it. Because you control the payload, you can enrich it: deduplicate purchases, hash and attach customer emails for better matching, and drop bots before they pollute your reporting.

The practical setup is GTM Server-Side running on a cloud container (Stape, Google Cloud Run or similar), with your web GTM forwarding events to it. Meta receives events through the Conversion API, Google Ads through Enhanced Conversions, and GA4 through its Measurement Protocol path.

Stores that switch from pure browser tracking to a proper server-side setup typically recover 15–30% of previously lost conversions within the first weeks — which immediately improves how every bidding algorithm in your account makes decisions.

If your reported ROAS has been drifting away from what your bank account says, your tracking layer is the first place to look. A tracking audit maps every event from click to purchase and shows exactly where data is leaking before any rebuild starts.

Most stores we audit have exactly two GA4 events working: page_view and purchase. That's like running a checkout funnel where you can only see who entered the store and who paid — with total darkness in between.

GA4's recommended eCommerce event set gives you the middle of the funnel: view_item, view_item_list, select_item, add_to_cart, remove_from_cart, view_cart, begin_checkout, add_shipping_info, add_payment_info, and purchase.

With those events flowing, GA4 builds real funnel explorations: you can see that 12% of carts abandon at the shipping step, or that mobile users drop off at payment method selection. Those are fixable, revenue-bearing problems — but only if the events exist.

Two details make or break the setup. First, every event needs its parameters populated: item_id, item_name, price, quantity, and currency. Without them, GA4 can't join the events into user journeys. Second, purchase must fire exactly once per order, with a stable transaction_id — duplicates silently inflate your revenue reporting.

If you also run server-side GTM, forward the same event names and parameters through the GA4 client. That way browser-blocked events still arrive via Measurement Protocol, and your funnel data survives Safari and ad blockers.

Once the event map is complete, the next step is connecting it to outcomes: custom funnel explorations per campaign, and audiences based on add_to_cart without purchase, which you can retarget on both Google and Meta.

A well-mapped GA4 property usually takes 2–3 days to build and pays for itself the first time it shows you exactly which funnel step is burning your ad spend.

Event Match Quality (EMQ) is Meta's 0–10 score for how completely your Conversion API events identify the person behind them. Below roughly 6, Meta treats your conversions as guesswork, and the learning phase stretches out while cost per result suffers.

The single biggest lever is sending hashed customer information with every event: email, phone number, first and last name, city, state, zip and country. Email alone typically lifts EMQ by 2–3 points; adding phone and name takes most stores into the high 8s and 9s.

Capture that data where it's naturally entered — account creation, checkout forms, newsletter sign-ups — and pass it through your data layer into server-side GTM, which hashes it with SHA-256 before forwarding to the Conversions API.

The second lever is event_id deduplication. If you run both the Meta Pixel in the browser and CAPI on the server, both must carry the same event_id and event_name for the same action. Get it wrong and Meta double-counts; get it right and you get browser coverage plus server reliability.

Third: fbp and fbc cookies. The _fbp browser cookie and the click-through _fbc parameter let Meta tie server events back to the exact ad click. On server-side setups, forwarding fbc from your landing URLs is what makes click attribution actually work.

Fourth, match keys on the right events. Purchase events with full checkout data score highest; lead events with only an email score lower. Where your CRM or store backend knows more about the customer, send it.

Stores that move from a 5 to a 9 EMQ routinely report 10–25% lower cost per purchase within a few weeks — same budget, same creatives, simply a signal Meta can finally trust.

What a Meta CAPI Gateway does and when to use it is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For Meta Ads, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

Why your server GTM container needs a custom subdomain is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For Server-side tracking, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

Setting up the TikTok Events API through server-side GTM is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For TikTok Ads, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

Pinterest Conversions API: a practical setup guide is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For Pinterest Ads, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

Enhanced Conversions for leads: capturing more form fills is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For Google Ads, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

Consent Mode v2: what changes for your tracking is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For Privacy, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

Server-side tracking for Shopify stores, step by step is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For Shopify, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

Server-side tracking for WooCommerce is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For WooCommerce, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

Browser + server events without double counting is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For Meta Ads, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

How Safari's ITP shortens cookies and how to extend them is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For Server-side tracking, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

Sending CRM sales back to Google Ads and Meta is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For Offline conversions, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

GA4 Measurement Protocol: when and how to use it is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For GA4, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

The data layer explained for marketers is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For GTM, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

Filtering bot traffic before it reaches your ad platforms is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For Server-side tracking, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

Building a Looker Studio dashboard for paid ads is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For Looker Studio, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

UTM tagging rules that keep reports clean is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For Analytics, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

Storing gclid and fbclid for reliable attribution is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For Attribution, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

What server-side tracking really costs to run is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For Server-side tracking, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

A 15-point conversion tracking audit checklist is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For Audit, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

Using MCP servers to manage Google Ads and Meta Ads with AI is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For MCP, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.

Feeding profit data into value-based bidding is one of the most common questions advertisers bring to a tracking audit. Getting it right directly affects how much conversion data your ad platforms receive.

Browser restrictions, ad blockers and consent rules mean that client-side tags alone now miss a meaningful share of real conversions. Every missing event weakens the bidding algorithm.

For Google Ads, the reliable approach is to collect events in a clean data layer, forward them to a server-side GTM container on your own subdomain, and deliver them through the platform's official server API.

Make sure every event carries consistent parameters — event IDs for deduplication, values and currency for revenue, and hashed customer data where consent allows it.

After launch, compare platform-reported conversions with your backend orders or CRM for at least two weeks. The gap between the two is the clearest health check of your setup.

If you want this done for you, book a free tracking audit and we will map exactly where data is leaking before any rebuild starts.