Event tracking

Some Pain Point

Problems

  • Data team is not familiar with implementation details
  • Dev team lacks guidance on metrics
  • Project owners cannot easily explore the collected data

Maintainability

  • Raw string in code base
  • Not easy to modify

Standardization

  • No document
  • No spec

Solution

Standardize it

Current Progress

basic workflow

  • data team & project owner: define metrics & specs with product owners

  • data team: write events and specs into code (config) for FE to reference

  • FE dev: use the specs to implement

  • FE dev & data team: send PR and data team review

  • data team: set up funnels/dashboards etc and send them to project owner

Ecommerce

Document it

Falcon, Junchen, Yujie, Me

Feels good

Future plan

Event tracking library

Details

3 parts

Spec, Library, IR

Spec

  • Human readable configuration file
  • Event name
  • Description
  • etc.

Library

  • A Gem library for backend
  • A Js library for frontend

IR

  • Intermediate representation
  • Generate from spec and feed it to the library
  • Compression intent mostly
  • Evaluate if we really need it

Ideal Workflow

  • Growth/Data team write the spec file
  • Convert the spec into ir
  • Put it into bobcat
  • Start adding tracking event using the library

Event Tracking @ Strikingly

By Weiyüen Wu

Event Tracking @ Strikingly

  • 735