Kiosk events
The anonymous events a store's screens send to head office, what each means, what it drives, how they are batched, and what is never in them.
As shoppers use the screens, each screen records anonymous events and sends them to head office. Events drive insights, lost demand, trend velocity, concept votes, fit learning, the sales loop and device health. No event carries a name, contact, face or photo.
Sending events
POST /api/launch/v1/retail/events
Authorization: Bearer <kiosk key>
{ "batchId": "…", "events": [ … ] }- Up to 500 events or 256 KB per batch, and 20 batches a minute per key.
- A batch sent twice is stored once.
- Each event's time must carry a time zone, be no more than seven days old, and no more than five minutes ahead.
- Ateliq's screens send a batch every 30 seconds, or sooner when 200 events are waiting, and retry with growing gaps (5 seconds, 30 seconds, 2 minutes, then every 10 minutes). Events not sent within 24 hours are dropped.
Event types
| Event | Sent when | Carries |
|---|---|---|
visit | A visit starts | An anonymous visit id |
tryon | A piece is tried on | The product and, when known, the size label |
look_main | A look is built around a piece | The product |
accept | The shopper adds a suggested add-on or step-up | The product |
decided | The shopper picks one after a side-by-side | The product |
view | A piece is viewed | The product |
miss | A search finds nothing | The phrase, up to 80 characters. Phrases that look like an email address or phone number are dropped. |
size_out | A size the shopper wanted is out of stock | The product and size |
size_suggested | The stylist shows or says a size | The suggested size or sizes, evidence, confidence, chart and source. Never the shopper's own stated size, brand or fit preference. |
offer_shown | A live offer is shown | The offer id |
vote | A shopper votes on a design concept | Up or down |
purchase | A purchase completes on the screen | Total, discount, currency and products |
stylist_call | A shopper calls a stylist | The call id. Never the shopper's note. |
stylist_answered | An associate answers | The call id, the associate's code and the wait in seconds |
heartbeat | Every minute | Feed version, app version, feed age, events waiting, and up to eight screens' layout, camera and voice |
What they drive
| Feature | Events |
|---|---|
| Insights | visit, tryon, look_main, purchase, offer_shown, miss |
| Lost demand | miss, size_out |
| Trend velocity | tryon |
| Concept tallies | tryon, vote |
| Sales loop | stylist_call, stylist_answered |
| Fit learning | tryon sizes, joined to paid hand-offs |
| Devices | heartbeat |
| The agents | miss, tryon, purchase (as counts and screened phrases) |
Offline
When a store's connection drops, visits, try-ons and concept votes queue on the screen (up to 500 events or 24 hours) and are sent with their original times when it returns. See Offline behaviour.
Kiosk events are kept for 400 days. See Data retention.
Something missing or unclear? Write to pb@ateliq.co and we will answer and fix this page. Last reviewed 12 November 2026.