task Active users & engagement · medium
Checkout review 1: establish the baseline
Harbor Market is investigating checkout reliability. First build a daily session baseline: session_date, sessions, distinct shoppers and returning_sessions. A returning session is any session numbered greater than 1 for that shopper in this observation dataset.
what to return
- Columns
session_datesessionsshoppersreturning_sessionsin this order- Rows
- 2 rows · in the order asked
- Watch for
- This stage starts from the original event tables in a fresh database. Recompute any intermediate results; nothing is carried over from earlier stages.
- Deduplicate globally by event_key, keeping the smallest id; a retry may have a conflicting payload.
- Use (occurred_at, id) as the total event order; equal timestamps follow id order. All times are UTC.
- A shopper starts a session at the first canonical event or after a gap strictly greater than 30 minutes from their previous canonical event. Exactly 30 minutes stays in the same session; midnight alone does not split it.
- Session numbers start at 1 per shopper and include every event type, including heartbeat and purchase-only sessions.
- Assign the whole session to the UTC date of its first event, even if it crosses midnight. Order by session_date.
- Skill
- Establish the daily population before interpreting checkout performance. Refresher: Sessionize an event stream →
expected result
Your query should return exactly these columns and values. Run it and compare.
expected result2 rows · in this order
| session_date | sessions | shoppers | returning_sessions |
|---|---|---|---|
| 2025-05-01 | 12 | 8 | 4 |
| 2025-05-02 | 4 | 4 | 1 |
all 2 rows
data you can query
Sample rows from each table. Each column shows its type underneath; → marks a link to another table.
market_web_events7 columns · 38 rows
| idinteger · key | event_keytext | shopper_idinteger → shoppers | occurred_attext | event_typetext | channeltext | cart_idtext |
|---|---|---|---|---|---|---|
| 1 | a1 | 1 | 2025-05-01 09:00:00 | view | A | |
| 2 | a2 | 1 | 2025-05-01 09:05:00 | checkout | direct | A |
| 3 | a3 | 1 | 2025-05-01 09:10:00 | purchase | direct | A |
| 4 | a3 | 1 | 2025-05-01 09:10:00 | purchase | direct | A |
| 5 | b1 | 1 | 2025-05-01 10:00:00 | view | search | B |
showing 5 of 38 rows
solution.sql
Hints and the answer are always available. Using them counts the question as solved with help.