The Event Census

Before Kindled trusts a single funnel percentage, the growth lead wants to see what the tracking actually captured. The events table records one row per action a shopper took, and the four kinds of action are the steps of the funnel: arriving, looking at a product, putting it in a basket, buying. A tally of the raw rows is the sanity check — if a step records suspiciously few rows, the problem may be the tracker rather than the shoppers.

events — one row per tracked action. user_id points at a row in users. event_type is one of signup, view_product, add_to_cart and purchase. event_date is the day the action happened. Nothing guarantees a person produces all four kinds, or any particular number of rows.

The table already exists in the database — there is nothing to create or load.

Task: Write a query that returns one row per kind of action, with columns event_type and n, n being how many rows of that kind the table holds. Most frequent first; kinds on the same count are listed alphabetically by event_type.

Example output — shape only, on invented tallies. The event_type labels are the real stored ones: