Skip to main content
Omneo provides two mechanisms for labelling profiles: Tags and Statuses. Both are classification tools, but they serve different purposes and behave differently.

​
Tags

Tags are short, freeform labels that can be assigned to any profile. They are used for ad hoc categorisation, operational notes, or segmentation. Examples:
  • christmas-campaign-2024
  • handle-with-care
  • influencer-referral
  • vip-waitlist
Tags are case-sensitive strings. A profile can have zero or many tags. Tags are available in reaction conditions via the flattened_tags array, making them useful as filtering criteria in automation logic. Tags can be:
  • Applied manually in CX Manager or Clienteling
  • Set programmatically via the API
  • Bulk-updated via the import tool
  • Used as conditions in reactions and claimable benefit JSON logic

​
Statuses

Statuses are a special class of label that represent a defined relationship between a profile and the brand. Unlike tags, statuses are configured in CX Manager as named definitions with structured properties. Examples:
  • Staff: internal employees who receive staff discounts
  • VIP: high-value customers with elevated entitlements
  • Influencer: customers with social media reach
  • Stylist: in-store advisors linked to client profiles
  • Media: press and media contacts

​
How statuses work

A profile can have zero, one, or multiple statuses applied simultaneously. Statuses can be:
  • Customer-facing or internal: configurable per status definition
  • Ranked: determining precedence when a customer holds multiple statuses and only one “best” status is needed
  • Grouped: statuses can be organised into logical or functional groups (for example, grouping all trade-related statuses together)
  • Time-limited: statuses can be assigned an expiry date, after which they are automatically removed from the profile
  • Manually assigned: by admin or manager users in CX Manager, or by store staff in Clienteling
  • Programmatically applied: via API or integration logic (for example, linking an Instagram account with 10k+ followers triggers “Influencer” status)
  • Bulk-updated: as part of implementation or ongoing data operations
Adding a status the wrong way removes a profile’s other statuses. The profile import and a PUT to the profile endpoint both replace the entire status set: they detach any status not present in the payload. To add a status while keeping the ones a profile already holds, use the additive batch status endpoint. See Statuses (dev guide).

​
Custom fields and metadata

Status definitions can carry custom fields, metadata, and internal or public-facing content. This information travels with the status and is accessible to any logic or presentation system that has access to the profile, including Reactions, Target templates, and consumer-facing surfaces like Profile Portal and Omneo Wallet. This makes statuses a flexible vehicle for delivering contextual content or configuration to different parts of the platform.

​
Statuses in incentive logic

A profile’s status can modify incentive entitlements:
  • VIP status: 30 extra days on rewards and benefits
  • Staff status: 40% off benefit on all full-price items
  • Influencer status: double Tier Points on all purchases
  • Media status: free delivery benefit on online orders
Statuses are available in reaction conditions and target templates via the flattened_statuses array.