Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Performance Marketing › Expert

Planning a Server-Side Tagging Move for a Riding Equipment Retailer

You judge an agency's proposal to move every tag of an invented riding equipment retailer into a server container at once. You finish with each measurement gap matched to the fix that closes it, the case for a server container tested and its prerequisites put first, and a cutover plan that moves one destination at a time with consent passed through, deduplication proved, a parallel run whose end is agreed and a way back.
ExerciseExpert levelModule 1: Moving conversion collection server-side5 minUpdated

Why this matters

At the advanced performance marketing level you specified enhanced conversions and server events for two platforms. At expert level the proposal on the table is infrastructure, and here it arrives as an answer to every measurement complaint at once. The comparison of the two fixes says they close different gaps: enhanced conversions change what one platform's tag sends, while a server container sits beneath every vendor and someone must host and run it.

The saddlery and its two gaps

Vreiroth Saddlery is an invented online retailer of saddles, riding boots and stable supplies. A paid media manager runs Google Ads and Meta in-house, a freelance developer looks after the shop, and the owner, who also handles data protection, wants one place to decide what each vendor receives.

Illustrative example — not a real result

Vreiroth Saddlery: what the team found

EvidenceWhat the team found
Orders in the shop systemAbout 1,150 a month
Google Ads purchasesAbout 760 a month, short since the account began
How riders buySaddle buyers return over weeks; many click an ad on a phone and order on a computer
Base tagFires once on each test order, from a phone and from a computer
MetaBrowser pixel only; the paid media manager wants the Conversions API
Web container13 vendor tags, 3 of which nobody can name; the reviews and chat widgets render on the page
Product pagesSlow on mobile, much of the weight from vendor scripts
Outgoing requestsThe confirmation page sends the buyer's email to the affiliate network in a URL
ConsentThe banner works, but the heatmap tag fires before the visitor chooses
Hosting and on-callNobody named; the developer works 2 days a week
Agency planAll 13 tags moved in one release, the week before the spring sale; the busiest weeks run from March to May

Match the fix to the gap

Google Ads counts fewer purchases than the shop although its base tag fires. The comparison lists long gaps before purchase and cross-device journeys, both how these riders buy, among the cases where the enhanced conversions guide says the gain tends to be large, and gives that gap to enhanced conversions, which need no server container. The second gap is control (page weight, what each vendor receives, Meta's server integration), which the comparison and the server-side tagging basics guide give to server-side tagging. Both wait while consent wiring is broken, and with no owner for hosting the comparison allows enhanced conversions only.

Task

  1. Name each gap and the fix the comparison points to.
  2. Run the case test from the server-side guide: which requests leave the page, which vendors the server calls and who answers when the endpoint fails.
  3. List what must be true before any traffic moves.
  4. Plan the cutover one destination at a time, gated by the server-side tagging go-live checklist, and place it against the calendar.
  5. Say what the server container will not fix.

Worked answer

The Google gap. Switch on enhanced conversions after the heatmap fix, in the web container Vreiroth already runs: the developer passes the checkout's email address to the Google Ads conversion tag through the data layer, the tag hashes it, and the consent banner gates it. Diagnostics, one tagged test order and purchases against shop orders before and after show whether it works.

The case test. Requests removed: the unnamed tags go first, and the page-weight case rests on the scripts that can move; the reviews and chat widgets draw what visitors see, so they stay. Vendors called from the server: analytics, Google Ads conversions and Meta's Conversions API. The person on call is blank, so the case is not ready until the developer owns hosting, uptime and the domain, the paid media manager owns the container's contents, and a short runbook says who acts when the endpoint stops answering.

Before any traffic moves. Fix the heatmap tag's consent behaviour, because a server container inherits whatever consent state the browser sets, and the consent mode guide is where that state is wired. Stop the email reaching the affiliate network now, in the browser.

Illustrative example — not a real result

Vreiroth Saddlery: the cutover plan

WhenStepPasses when
NovemberEnhanced conversions on in the web container; heatmap consent fixed; 3 unnamed tags removed; affiliate email strippedDiagnostics read recording; tracking verification passes
DecemberServer on a first-party subdomain; developer named owner; publishing restricted to 2 peopleRequests reach the endpoint and the right clients claim them
JanuaryAnalytics stream sent through the server beside the browser tagsServer and browser events agree over a 2-week parallel run agreed with report readers
JanuaryMeta Conversions API tag, order number as the shared event IDServer purchases deduplicate against the pixel; until they do, the pixel carries conversions
FebruaryGoogle Ads conversion tag moved to the serverHashed data still arrives; until it does, the web tag keeps running
FebruaryBrowser copies removed one vendor at a time; previous container version recordedNo vendor counted twice; cutover dates annotated
March to MayNothing movesAny destination that failed stays in the browser until June

One destination at a time, with a way back. The go-live checklist treats each destination as a small cutover, so a failure usually holds that destination, not the project: a purchase counted twice through failed Deduplication would teach bidding to chase sales that never happened. The parallel run's end is agreed before it starts, the previous web container version can be published again, and each cutover date is annotated in analytics, Google Ads and Meta, so a change in reported conversions is not blamed on the campaigns. The agency's single release before the sale leaves room for none of this.

What it will not fix. A server container passes on only what reaches it: events wrong at the source stay wrong, and visitors who declined consent stay unmeasured.

Common mistakes

  • A server container as the route to enhanced conversions. The feature already works in the web container.
  • Moving tags before consent is fixed. The server inherits the browser's consent state, faults included.
  • Removing the browser tags on cutover day. Without a parallel run there is no baseline to show what was lost.
  • A silent cutover. An unannotated date turns a measurement change into a story about performance.

Pages this lesson applies

Terms used on this page

Also related

Related