Before developers add tracking, write a measurement plan: the business questions, the events and parameters that answer them, and which events are key events.
Rules that save rework:
- Use Google's recommended events when one fits, such as
generate_lead, sign_up, login, search and the ecommerce set (view_item, add_to_cart, begin_checkout, purchase), with their parameters. Reports and integrations understand them.
- Custom event names use letters, numbers and underscores, start with a letter, and can't use the reserved prefixes
ga_, google_ and firebase_. Names are case-sensitive.
- Facts about a user (a tea club member or not) belong in a user property, registered as a user-scoped custom dimension. Facts about one action belong in event parameters.
- Products belong in the
items array of ecommerce events, not in separate parameters.
- A standard property can register up to 50 event-scoped custom dimensions; spend them on questions someone will ask.
Larkspur is launching a wholesale price list: cafés leave their details to receive it.