Flagship course

Consent Signal Architecture

A live programme for people who already ship tags and still cannot explain what the numbers mean after a visitor taps Reject.

Collaborators reviewing a laptop in a bright room

You will rebuild one production-like property: consent states, essential versus optional collection, fallback events that do not impersonate identifiers, and a reporting contract signed by a fictional (or real) counsel.

Informational pricing: open cohort £1,180 · in-house group from £6,400. No payment is taken on this website.

Ask about the next cohort

Modules

  1. Prompt as interface. Latency, dark-pattern audits we refuse to teach, and copy that does not hide analytics inside “personalisation”.
  2. Consent snapshots. Modelling granted, denied, unknown, and withdrawn without rewriting yesterday’s facts.
  3. Event dictionary hygiene. Splitting product questions from vendor default hits.
  4. Fallback instrumentation. First-party, non-tracking signals that survive a reject.
  5. Warehouse contracts. Column-level consent, late CMP responses, and duplicate suppression.
  6. Reporting that names its holes. Exec dashboards that label coverage instead of smoothing it away.
  7. Experimentation limits. Sample-ratio distortion when cookies never set.
  8. Critique. You present a redacted taxonomy; the group marks consent gaps in public.

Learning outcomes

  • Write a consent-aware event schema your warehouse can enforce.
  • Separate essential operational logs from optional analytics without pretending they are the same feed.
  • Brief GB stakeholders on what PECR-aware collection can and cannot cover.
  • Produce a one-page reporting contract that product, data, and legal can initial.

Instructor

Portrait of instructor Rowan Hale

Rowan Hale taught measurement in agency and in-house roles before opening Releaseflowhub. Sessions mix critique with short lectures; Rowan does not demo vendor UIs as if they were the curriculum.

What past participants said

Module four on fallback events is the piece I still open. We had been stuffing server logs into the same BigQuery table as client hits; the course made that look as sloppy as it was.

Sam, Cardiff · product analytics

★★★★☆

Clear on architecture. The live critique is blunt. I wanted more time on mobile WebViews; that sits outside the eight evenings and you should know that before you book.

Verified note on the studio board

Questions we actually get

Do you certify a vendor implementation?

No. We teach design. If your CMP or tag manager is misconfigured, the course will surface it; we will not become your implementation partner during class hours.

Is this legal advice for the United Kingdom?

No. We discuss PECR-aware collection as practitioners. Counsel remains yours. Governing law for studio contracts is covered on the terms page.

What is a real limitation of this course?

We do not cover native app ATT/SKAN plumbing in depth. Web and server-side collection are the centre of gravity. App teams join, then usually need a separate clinic.

How large is a cohort?

Twelve seats in the open run so critique stays specific. Recordings exist; unsubmitted homework is not marked.