Visits in Omneo record a customer’s physical presence at a location — separately from a purchase transaction. A visit captures the fact that a customer was at a store or appointment, regardless of whether they made a purchase.Documentation Index
Fetch the complete documentation index at: https://docs.omneo.io/llms.txt
Use this file to discover all available pages before exploring further.
Visit vs Transaction
| Concept | Description |
|---|---|
| Transaction | A completed purchase — the customer bought something |
| Visit | A presence record — the customer was there, with or without a purchase |
- Service businesses — recording appointments, consultations, and alterations
- High-engagement retail — tracking store visits to understand visit-to-purchase conversion
- Staffed experiences — capturing that a specific staff member served a customer
Visit fields
| Field | Description |
|---|---|
profile_id | The profile being visited |
location_id | The store or location of the visit |
staff_id | The staff member who served the customer |
occurred_at | Date and time of the visit |
type | Visit type (configurable per brand) |
notes | Optional notes about the visit |
duration | Visit duration |
Use cases
- Booking and appointment management — record that a customer attended an appointment booked via a scheduling tool
- Consultation tracking — capture that a customer visited for a styling consultation before their purchase
- Footfall attribution — understand which marketing activities drive store visits, not just transactions
- Staff performance — track how many customers a specific staff member serves
Visits in reactions
Visit events (visit.created, visit.updated) are available as reaction triggers. Brands can fire reactions on visit events — for example, issuing a benefit after a customer’s third in-store appointment.