Web product analytics
Knowing what people actually do — a defined event schema, instrumented and consent-gated.
What we build
A funnel event schema defined before anything is instrumented (so the data answers questions rather than accumulating), the events themselves, and consent gating so analytics respects the choice a visitor made. Decline this if you do not intend to act on the numbers. In-app product events are this service's whole scope — joining marketing spend to revenue (attribution, ad-platform integration, cost per customer) belongs to the analytics warehouse & dashboards service.
What you get
- A written event and funnel schema, signed off before instrumentation
- Every event in the schema firing and visible in the analytics dashboard on production
- Analytics suppressed until consent is given, verified with consent declined
How the work unfolds
- Define the funnel event schema
- Instrument the events
- Wire consent-gated analytics
How an engagement starts
This work builds on Web core feature build, so scope, boundaries and constraints are agreed before anything is built.
Teams often combine it with: