From 88 to 73 tags, every event tested

GotPhoto makes software for school and sports photographers, who sell their photos to parents through GotPhoto.
Software for school and sports photographersgotphoto.com

Built with

  • Google Tag Manager
  • Server-side GTM
  • GA4
  • Cookiebot
  • HubSpot
  • Microsoft Clarity
  • Google Tag Manager
  • Server-side GTM
  • GA4
  • Cookiebot
  • HubSpot
  • Microsoft Clarity

By the numbers

events in the measurement plan
21
tags removed
17
data layer parameters
55

The problem

GotPhoto runs measurement on gotphoto.com through Google Tag Manager. The container had grown to 88 tags. Among them were tags for purchases, webinars and onboarding that were no longer in the measurement plan. Variable names followed no fixed spelling. And every GA4 event goes out through the browser and the server, so every mistake counted twice.

GotPhoto's GTM container: from 88 to 73 tags, with the 17 removed tags listed

What we did

The starting point was the measurement plan: 21 events, each with parameters, priority and test status. All 55 parameters in the plan now have a data layer variable in GTM with exactly the same name. We removed 17 tags and added the event for external clicks, in the browser and on the server. Then we checked all 21 events on gotphoto.com with GTM Preview and our own event tester.

Data layer: the push for trial_click and the 55 parameters from the measurement plan, each with its own variable in GTM

What it delivers

13 of the 21 events are confirmed and measure what the plan describes. The other eight are named, with the reason: broken, not finished yet or no matching feature on the site. 22 GA4 events go through the browser and the server container. Both hits carry the same event ID, so the streams can be matched. Cookiebot loads first and sets consent to denied by default outside the US.

Measurement plan with 21 events and their test status: 13 confirmed, 4 not working, 3 not done yet, 1 without a feature

Highlights

One plan, 21 events

Parameters, priority and test result for every event in one table.

55 parameters, one name

Every parameter in the plan has a data layer variable in GTM with the same name.

Browser and server

22 GA4 events go out both ways and share one event ID.

Consent first

Cookiebot Consent Mode v2 loads before the other tags and denies everything by default outside the US.

More visuals

Route of an event: data layer, Cookiebot Consent Mode v2, GTM, then GA4 in the browser and through the server container
Photographer at work during a shoot on a sports field

Which process costs your team the most time right now?

Describe it in one message. We calculate what it currently costs you in licences and manual work and tell you honestly whether custom software is worth it. Even if the answer is no.