A Visit is a non-transactional interaction record — it captures that a customer was present at a location without necessarily making a purchase. Visits are separate from Transactions and are used to track footfall, in-store engagement, and service interactions.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.
When to use Visits
| Use case | Why a Visit, not a Transaction |
|---|---|
| Customer browsed but did not purchase | No transaction to record |
| In-store service appointment (alterations, styling) | Service rendered, no product sale |
| Event attendance | Customer was present at a brand event |
| Click and collect pickup | Fulfillment visit distinct from the online order |
| Store loyalty card scan at entry | Physical location check-in |
Creating a Visit in CX Manager
Staff can manually log a visit against a customer profile:- Open the profile in CX Manager or Clienteling
- Navigate to the Interactions tab
- Select New Visit
- Set the location, date, and any notes
- Save
Visits and Reactions
Visits can trigger Reactions, which makes them powerful for visit-based incentive programs:- Visit Achievement — increment an achievement count on every visit
- Visit reward — issue a reward after a customer reaches a visit threshold
- Visit notification — send a post-visit follow-up message
visit.created
Visit frequency reporting
Visits contribute to the profile’s interaction history and can be used in CX Manager reporting to understand:- How often known customers visit without purchasing
- Which stores have the highest visit-to-purchase conversion
- Whether service interactions correlate with higher future spend
Visit frequency reports and aggregation fields for visit count may vary by Omneo instance configuration. Confirm with your Omneo team which aggregation attributes are available.
Visits vs Transactions
| Visit | Transaction | |
|---|---|---|
| Requires a purchase | No | Yes |
| Creates a financial record | No | Yes |
| Triggers reward calculations | Only via reaction | Automatically (if configured) |
| Contributes to Tier spend | No | Yes |
| Visible on profile timeline | Yes | Yes |