Measurement
that waits
for a yes.
Metric Routecore trains product, growth, and analytics teams to design consent-based tracking analytics that still produce usable numbers. We start from Thailand’s PDPA and the messy reality of tags already in production — not from a slide about “privacy first.”
Consent Measurement Studio
The programme most teams come for. Six weeks of lawful signal design, banner-to-tag sequencing, and reporting that does not pretend withheld consent never happened.
Build a measurement map that only fires after permission.
You leave with a consent taxonomy, a server-side forwarding sketch that respects opt-out, and a written limitation note for stakeholders who still want “full funnel” numbers on day one.
Numbers that remain defensible when legal reads the tag list.
Consent-based tracking analytics is not a plugin. It is a way of deciding which events exist, which events wait, and which events you simply do not collect.
- A consent taxonomy, not a banner screenshot Purpose categories mapped to actual tags, vendors, and retention windows — the artefact legal and growth can both sign.
- Sequence before script Banner state, CMP callback, and container load order documented so a pixel cannot outrun a person’s choice.
- Reporting that names the gap Dashboards that show opted-in traffic honestly, instead of inflating conversion by ignoring withheld consent.
Clinic desks, not lecture theatres.
Each week opens with a short brief, then a live teardown of a real property — often a Thai retailer, hotel group, or marketplace stack. You work on your own tag map between sessions. Instructors annotate, they do not grade for “engagement.”
If your CMP is still a default WordPress plugin, we start there. If you already run a server container, we start there. The pedagogy is the same: permission first, then instrumentation.
What people actually say after the studio.
“The banner-to-container sequence in week three showed why our Facebook tag still fired on the thank-you page after reject. We fixed the load order the same night.”
Arun W., measurement lead · retail marketplace
“Useful, though the PDPA reading pack assumes you already know what a data controller is. I spent Sunday catching up. After that, the taxonomy worksheet made sense.”
Mira · Chiang Mai
Notes we publish when a client question repeats.
When consent is the measurement boundary
Why “we still need the number” is not a lawful reason to keep a tag alive after reject.
Reading PDPA for analytics teams
A working walk-through of the sections that actually change how you instrument a site.
If your tag map still outruns the banner, write to the studio.
We reply within two working days. If a cohort is closed, we will say so plainly and offer the next open seat or a one-off clinic.