The order matters more than the tooling. A company that starts spending before the measurement layer exists will get numbers — just not numbers that can be acted on. Three dashboards will report three different truths, and the argument about which one is right will outlast the campaign.
Design the taxonomy before the tags
Most analytics implementations are archaeology: events added by different people over several years, named inconsistently, measuring subtly different things. Nothing can be compared to anything, so every question becomes a project.
The fix is unglamorous. Write the event taxonomy down first — one naming model, one definition per event, one owner. The tag container implements that document. It does not get to invent events, and neither does a well-meaning marketer in a hurry.
Consent is a data decision, not a legal chore
A banner that loads the tags anyway is both a compliance problem and a data problem: you now have a dataset you cannot defend and cannot fully trust. Done properly, nothing non-essential loads before a choice, refusing is as easy as accepting, and the stored consent state genuinely controls what runs on the next page view.
Consent Mode v2 changes the shape of the problem rather than removing it. Denied consent still sends signals; it does not stop the request. If that distinction is not understood during implementation, the resulting model will be wrong in a way that is very hard to see later.
Count the outcome, not the gesture
A form submission is a gesture. A qualified enquiry is an outcome. In any business with a sales cycle longer than a session, counting submissions rewards whatever produces the most low-quality leads, and the optimisation loop faithfully makes it worse.
- Count a conversion once, when the server has durably accepted it — not on the click.
- Carry the attribution identifiers with the submission on the server side.
- Keep names, emails and phone numbers out of the browser data layer entirely.
- Record what kind of enquiry arrived, so quality is measurable and not anecdotal.
What good looks like
One container. One event taxonomy, written down. Conversions defined by the business, not by the platform’s defaults. A consent state that actually gates execution. And a single answer to the question "where did this enquiry come from" that every department accepts, because it was agreed before anyone had a result to defend.