These notes refer to programmes on this site — Consent Measurement Studio, First-Party Signal Lab, PDPA Analytics Clinic, and Tag Governance Intensive. Attribution styles differ because people asked to be named differently.
★★★★☆
Verified learner · Consent Measurement Studio
“Week three’s load-order lab is the reason our TikTok pixel no longer starts before the CMP returns a state. I wanted more time on Looker Studio calculated fields that exclude non-consent traffic; that part was only sketched.”
Platform note · submitted after cohort 8
“Kanya made us print the vendor list and strike anything we could not justify to a PDPA officer. Two agencies were unhappy. The taxonomy still holds.”
Ploy Rattanakul, analytics manager · Bangkok
“The First-Party Signal Lab stopped us stuffing every form field into a user property ‘just in case.’ We now collect three fields on the waitlist and nothing else until accept.”
Somsak · Phuket
Client in hotel booking: “Tag Governance Intensive was drier than the Studio. That is what we paid for. Daniel refused to restore a ‘soft reject’ that still sent hashed emails. Our media buyer still argues with us. The container is cleaner.”
“I came in thinking consent-based tracking analytics meant installing a prettier banner. The PDPA Analytics Clinic disabused me of that in the first hour.”
Niran, Chiang Mai · product ops
“Recordings of the Bangkok evening clinics are clear. Audio on one Thursday dropped for twelve minutes; they posted a recap the next morning. Not glamorous. Adequate.”
Anonymous · in-house counsel sitting with the analytics desk
A growth team in Bangkok had a CMP that stored “pending” as if it were accept. Purchase and add-to-cart still left for three ad platforms. During Studio week two they rebuilt the callback so pending loaded only essential cookies. Week four’s limitation note went to the CMO: paid social reporting would drop, and that drop was not a tracking bug.
Three months later they report opted-in purchase as a separate view. They still miss the old vanity totals. They have not quietly re-enabled the pixels.
Told with permission · company unnamed by request
Four properties, one shared GTM, a vendor who insisted the booking engine “required” a fingerprinting script. Residency hours were spent reading the engine’s actual contract, not arguing on Slack. The script was not required. It was removed. First-party booking events now wait for analytics consent and still reach the hotel’s own warehouse.
The residency did not fix their attribution model. They said so in the closing note. It did stop an unlawful tag from riding every reservation.
Client in hospitality · Chiang Mai + Bangkok properties