Flagship programme

Event Contract Lab

A working group for people who own analytics instrumentation. You will freeze a slice of your event dictionary, test it on staging, and write a release gate your engineering manager can actually enforce.

Developer looking at code on a laptop

What you leave with

  • A versioned contract covering at least twelve events from your own product.
  • A replay script and a fail/pass log for one golden journey.
  • Language for a release note: certified vs uncertified events.
  • A short identity map: anonymous id, user id, and where they break.

Informational fee

£1,890

Includes live sessions, recorded recaps, and two office-hour slots. No checkout on this site — request a seat via contact.

Modules

  1. Dictionary archaeology. Export names from GTM, the warehouse, and the product wiki. Mark collisions.
  2. Contract syntax. Required vs optional properties, enumerations, and what “null” is allowed to mean.
  3. Golden journeys. Pick one path (browse → cart → pay) and write expected hits in order.
  4. Duplicate and retry logic. Payment redirects, double-submit, and event_id discipline.
  5. SPA and delayed hydration. Route changes, stale titles, and phantom page_view.
  6. Consent coupling. Denied state must change the payload, not only the banner.
  7. Warehouse replay. Land the same journey in a table and join it to the contract.
  8. Release gate writing. What shipping uncertified events does to a forecast.

Instructor

Portrait of Priya Calder

Priya Calder

Measurement lead at Query Layerbase. Previously sat with catalogue and checkout teams in UK retail, arguing about whether add_to_cart should fire on wish-list. Teaches from the Blackcraig desk on Tuesdays and Thursdays.

Who it is for

Analysts, tagging specialists, and product engineers who already ship events. It is not an introduction to GA4’s interface.

Limitation

We do not certify vendor-specific “enhanced ecommerce” presets as a substitute for your contract. If your stack cannot export raw hits from staging, warehouse replay will be demonstrated on our sample pack rather than your production tables — that is a real gap, not a footnote.

Questions we hear before week one

Do I need engineering time?

Yes. Without a staging build you can still write a contract, but you cannot complete replay. Book this after a freeze, not during one.

Is the fee refundable?

See the refund notice. Recorded recaps are not a substitute for the live lab if you miss more than three sessions.

Will you fix our GTM container for us?

No. The lab teaches you to write the ticket and the test. Implementation stays with your team.

From recent cohorts

Module six on consent coupling showed our CMP firing ads_storage granted while the UI still said rejected. That is now a release blocker.

Marcus L., tagging specialist — Manchester

The office hours helped, but Priya will not debug your private GitHub from the group call. Fair, slightly inconvenient if you hoped for unpaid consultancy.

Anonymous product manager, marketplace