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

Performance Marketing › Expert

Checkpoint: Server-Side Tagging, Enhanced Conversions and Cutover

Scenario questions set in an invented wallpaper and paint retailer test the judgement behind the first expert performance marketing module. They cover what stays in the browser, which fix a Google Ads matching gap needs, the endpoint and publishing rights, client claims, enhanced conversions after the conversion tag moves, the side-by-side run and the way back when a cutover fails, with each answer explained.
CheckpointExpert levelModule 1: Moving conversion collection server-side4 minUpdated

What this checkpoint covers

Steilesko Wallcoverings, an invented online retailer of wallpaper, paint and decorating tools, has decided to move its measurement into a server container, and an agency has drafted the move. The questions test doing it without losing the numbers the paid programme bids and reports on; whether to build a server at all is not retested.

Illustrative example — not a real result

Steilesko Wallcoverings: the agency's cutover draft

ItemThe draft and the team's notes
Shop ordersAbout 2,100 a month
Google Ads purchasesAbout 1,450 a month; test orders show its base tag firing every time
MetaNo comparable gap
Product pages"Script-free": data layer, consent banner and web container removed
EndpointThe hosting provider's default domain
Server container publishers6 people, 2 of them agency staff who have left
ClientsThe analytics client and a gallery client for the sample-ordering widget, which preview shows taking some Google tag requests
Google Ads tagServer copy live and browser copy deleted the same day; diagnostics "after launch"
Side-by-side run"Until the numbers look similar"; finance's dashboard reads analytics purchases
Previous web container versionNot recorded

Task

  • Decide your action for each scenario and give the reason. Sound advice resting on a mistaken reason is scored as wrong.
  • Reread the page an explanation links whenever your answer missed.

Questions

  1. The agency promises product pages with no scripts at all once the server container decides consent. What do you tell them?
  2. The marketing manager wants the server project brought forward to close the Google Ads shortfall shown in the materials. What closes that gap, and does it wait for the server?
  3. The agency says the default domain and the publishing list can both be tidied after launch. Your call?
  4. The analytics destination is due to go live tomorrow, and the preview shows the widget's client claiming Google tag requests. What happens first?
  5. What do you change in the plan for the Google Ads conversion tag?
  6. What must be settled before the side-by-side run begins, and what is recorded on cutover day?
  7. The morning after cutover, analytics purchases have collapsed while shop orders look normal. The agency wants a few days to debug the server container where it stands. What do you do?

Answers explained

  1. Three things stay on the page. The data layer, because the server knows only what the browser sends; the consent banner and consent mode, because the visitor chooses in the browser and the server acts on the state it receives; and a script to send the events, whether the Google tag or the web container. See what moves to the server.
  2. Enhanced conversions, now, in the web container. A shortfall confined to Google Ads while the base tag fires is a matching gap, and the decision table gives it to the narrower fix, which uses first-party data the checkout already collects. Building a server for this alone buys running costs for something the existing container can do. See the decision table.
  3. Both before cutover. On the provider's default domain the server works on the day but gives up most of the first-party benefit, and moving the endpoint later means another side-by-side run. Publishing sits with a small group who apply the review, so the leavers lose access now. See separating edit from publish.
  4. The claim is fixed before any destination goes live. A client may take only its own requests, and any fault in the data flow group halts the move. Check in the server preview which client took each request, narrow the widget's client and confirm the analytics client takes the Google tag's. See reading which client claimed a request.
  5. Keep the browser tag until the server copy is proved. The conversion action's diagnostics and a tagged test order must show hashed data arriving through the server. Until then the browser tag carries Google Ads conversions; after that its copy goes, since two copies count twice. See reading the diagnostics tab.
  6. An end date, agreed with finance and every other report reader. A dashboard reading both streams shows doubled purchases during the parallel run, and fixing its length beforehand stops it being cut short when the first figures match. Cutover is ticked only once the destinations have passed for the whole run, and its date goes into analytics and both ad platforms as an annotation. See the go-live checklist.
  7. Roll back first, then investigate. Publish the previous web container version, confirm the browser tags are firing again and debug the server container in parallel, so the shop keeps measuring meanwhile. The draft recorded no previous version: close that gap before any cutover. See rolling back a published version.

Where to go next

Misses on the second, fifth or sixth question send you back to the riding equipment retailer exercise, which plans a cutover one destination at a time; for the signal work this module assumes, revisit the advanced performance marketing level. The next module opens with the conversion goal change checklist.

Pages this lesson applies

Terms used on this page

Also related

Related