Loading problem...
A commerce analytics team is building a "quick return" user signal from raw transaction logs.
Table: Users
Data quality notes:
Definition of active user:
Task: Return the IDs of all active users.
Output requirements:
Supported submission environments:
Users:
| user_id | item | created_at | amount |
|---------|-------------------|-------------|--------|
| 5 | Smart Crock Pot | 2021-09-18 | 698882 |
| 6 | Smart Lock | 2021-09-14 | 11487 |
| 6 | Smart Thermostat | 2021-09-10 | 674762 |
| 8 | Smart Light Strip | 2021-09-29 | 630773 |
| 4 | Smart Cat Feeder | 2021-09-02 | 693545 |
| 4 | Smart Bed | 2021-09-13 | 170249 |[
{"user_id":6}
]User 6 has purchases 4 days apart, so user 6 is active. User 4 has a gap of 11 days, while users 5 and 8 have only one purchase each.
Users:
| user_id | item | created_at | amount |
|---------|-----------------|----------------------|--------|
| 10 | Espresso Maker | 2024-01-01 08:00:00 | 320 |
| 10 | Coffee Grinder | 2024-01-08 08:00:00 | 210 |
| 20 | Router | 2024-01-01 08:00:00 | 90 |
| 20 | WiFi Extender | 2024-01-08 08:00:01 | 45 |[
{"user_id":10}
]User 10 qualifies at the exact 7-day boundary. User 20 misses by one second and is excluded.
Users:
| user_id | item | created_at | amount |
|---------|---------------|----------------------|--------|
| 40 | Gaming Mouse | 2024-05-10 09:30:00 | 79 |
| 40 | Gaming Mouse | 2024-05-10 09:30:00 | 79 |
| 50 | Desk Lamp | 2024-03-01 10:00:00 | 20 |
| 50 | Desk Lamp | 2024-03-20 10:00:00 | 20 |[
{"user_id":40}
]Duplicate timestamps still represent separate rows, so user 40 qualifies with a 0-day gap. User 50 has a 19-day gap and does not qualify.
Constraints