Conversion Tracking & Data

Enhanced Conversions vs Server-Side Tagging

In short: Both improve conversion tracking under privacy pressure, but they operate at completely different layers. Enhanced Conversions enriches one conversion event with hashed customer identity so Google can match it to a signed-in user. Server-side tagging changes the transport for every event of every type, running a container on your own infrastructure so requests are more durable and easier to control. Running server-side tagging does not automatically improve identity matching, and turning on enhanced conversions does not require server infrastructure. Use enhanced conversions for a fast, targeted match-rate fix; use server-side tagging when you're managing many vendors and want durability and control across all of them.

By the AdFlint research team · Fact-checked against current Google and Meta platform behavior · Last reviewed July 2026

Enhanced Conversions

Sends hashed first-party customer data with a Google Ads web conversion so Google can match it to a signed-in user.

At the conversion, your page or server passes email, phone, or address fields hashed with SHA-256; Google matches them against signed-in accounts and recovers conversions the cookie alone would have missed. Turn it on whenever the confirmation step already captures customer details. The frequent mistake is enabling the setting without actually supplying the fields, since the toggle does nothing if no user-provided data reaches the tag.

Full definition

Server-Side Tagging

Runs a tagging container on infrastructure you control, so the browser sends one request and your server forwards data to vendors.

The page posts to a first-party endpoint on your own subdomain; a server container then enriches, filters, and fans the event out to Google Ads, GA4, or Meta. Teams adopt it to set durable first-party cookies, cut client-side script weight, and keep vendor payloads under review. Two misconceptions persist: it does not manufacture data the browser never sent, and it does not exempt you from consent requirements.

Full definition

Side by side.

The differences that actually change what happens in your account.

 Enhanced ConversionsServer-Side Tagging
What it addsHashed first-party fields - email, phone, name, address - attached to an existing conversion ping.A server-controlled hop for every tag's request, regardless of vendor or event type.
What it touchesOne conversion action at a time.Every tag routed through the container - GA4, Ads, Meta, and anything else pointed at it.
Cookie behaviorSets no cookies of its own; it only rides along with the existing conversion tag.Can set durable first-party cookies on your own domain that hold up better than third-party ones.
Setup effortA toggle plus supplying the right fields on an existing tag, typically minutes.Provisioning and maintaining a cloud-hosted container, an ongoing infrastructure commitment.
What breaks when misconfiguredNothing visibly - the setting silently does nothing if no user-provided data reaches the tag.Delivery for every vendor behind it can drop at once if the container or forwarding rule breaks.
Consent handlingStill governed by whatever consent state the underlying conversion tag already respects.Still has to respect consent signals - it changes where the request is processed, not whether consent applies.
Where it reportsMatch-rate diagnostics inside the conversion action's enhanced conversions status.No report of its own - verified through DebugView, server logs, or the network tab.

What actually separates them.

01

Enhanced conversions only enriches a conversion event that already fires; server-side tagging changes how every event, of any type, physically travels from browser to vendor.

02

Server-side tagging can set durable first-party cookies that improve tracking broadly; enhanced conversions sets no cookies and only supplements identity matching on the events it's attached to.

03

Misconfigured enhanced conversions fails quietly and narrowly, hurting one action's match rate; misconfigured server-side tagging can fail loudly and broadly, cutting off every vendor behind it at once.

04

Enhanced conversions is a per-action setting inside Google Ads; server-side tagging is a separate piece of infrastructure you provision and maintain outside any single ad platform's UI.

05

Running server-side tagging does not automatically improve identity matching - you still need enhanced conversions configured on the conversion action to get the hashed-match benefit.

Which one should you use?

Use Enhanced Conversions when

  • Your confirmation page or backend already captures verified email or phone at the moment of conversion.
  • You want to recover conversions cookie loss and privacy restrictions are undercounting.
  • You want a fast, low-effort improvement without new infrastructure.
  • You're optimizing one or two key conversion actions, not your whole tagging stack.

Use Server-Side Tagging when

  • You're running tags for many vendors and want one durable, first-party cookie strategy for all of them.
  • You want to filter or strip sensitive fields before anything leaves your infrastructure.
  • You're losing meaningful data to ad blockers or slow client-side script loads.
  • You need a review point where your team, not a vendor, controls exactly what payload goes out.

Common questions.

Does server-side tagging automatically turn on enhanced conversions?

No. Server-side tagging changes how data travels, not what identity fields are attached to a conversion. You still have to configure enhanced conversions on the conversion action and make sure hashed customer data actually reaches the tag, whether that tag lives client-side or server-side.

Do I need server-side tagging to use enhanced conversions?

No, enhanced conversions works fine on a standard client-side tag as long as hashed fields reach it. Server-side tagging is a separate infrastructure decision usually made for cookie durability, script weight, or data governance reasons, not a prerequisite for enhanced conversions.

Can I use enhanced conversions and server-side tagging together?

Yes, and it's common. The server container forwards the conversion event, and the enhanced conversions fields travel along with it, sometimes hashed server-side for consistency. They solve different problems and stack cleanly.

Or stop choosing between them.

AdFlint picks the setting, writes the ads, and keeps optimizing inside the Google and Meta accounts you already own.

Try AdFlint freeSee how it works

Related comparisons

All comparisons