Benefits are a mechanic similar to a coupon or promotion that has some type of conditional logic associated. For example:
- 25% off Pants
- $15 off your second item
- Free shipping on your first order
- A gift pack
The following sections of this guide contain further explanation of Benefits, their use, examples, and deployment. Any bolded term in the guide notates a term that is defined in the Omneo Terminology Glossary.
A Benefit is created and 'issued' to a Profile.
A Benefit's properties are defined by the Benefits Definition which is a required reference in order to create the Benefit.
A Benefit is claimed via a Redemption, subject to the properties of the Benefit (e.g. expiry, maximum redemptions, etc) and the conditions that are assessed by the redeeming system (e.g. POS assessing the item/order qualifies).
Benefits are generally implemented as a secondary mechanic to complement Points or Rewards as the primary mechanic of a program. They can be created as campaign/occasional and/or as event triggered offers.
Some examples of how Benefits could be implemented to a program:
Attribute Related Events
- Join Anniversary
- Tier Anniversary
- Tier Qualification
Activity Related Events
- Product or Category Purchase
- Product Review
- Satisfaction Submission
- Profile Attribute Update
- Communications Subscription
- Achievement Level Qualification
- Lapsing or Recency Status
- Events such as VIP Night
- Media Channel Campaign
- Seasonal Promotion
- New Category Promotion
The process of creating a Benefit differs between current & legacy versions of Omneo. However in both versions, a Benefits Definition must be created first before a Benefit can be created (as the definition sets the properties of the Benefit).
See below for further explanation.
New Omneo Instances
The addition of Authentication Roles and the Rules Engine to Omneo results in a best practice deployment whereby:
- Benefits Definitions are created within the Omneo CX Manager admin UI; &
- Creating a Rule in the Rules Engine that issues Benefits;
- Benefit issuing is triggered by a creating or updating an Interaction or Transaction and the Rules Engine executes the Benefit creation.
This workflow of creating an Interaction or Transaction, which triggers the Rules Engine to create a Benefit provides context and audit references to the record.
Within the Omneo CX Manager, an Administrator can provide a token greater endpoint scope to create these objects via API directly. However this is not recommended in most use cases - refer to Authentication Roles for detailed information.
Legacy Omneo Instances
Rules Engine and Omneo CX Manager admin UI are not available in legacy Omneo Instances. Therefore the Benefits Definition and Benefits API endpoints are the only means available to create a Benefit.
In Omneo a Definition is a set of properties that are applied when an object record such as a Benefit is created. Below are the properties of a Benefits Definition:
|Id||The ID of the Benefits Definition|
|Name||A name or title of the Benefit|
|Handle||A unique handle of the Benefits Definition|
|Period||The number of days that the issued Benefit can be redeemed|
|Description||A description of the Benefit|
|Notes||A note associated with the Benefit|
|Extendable||Defines if an issued Benefit expiry can be updated/extended|
|Reassignable||Defines if an issued Benefit can be re-assigned to another Profile|
|Max Redemptions||Sets the maximum possible redemptions of the issued Benefit|
A Benefits Definition can be created by an Administrator in the Omneo CX Manager. Developer documentation can be found at Benefits Definition endpoint.
A Benefit is issued to a Profile and has the following additional properties:
|Id||The ID of the Benefit|
|Expires||The expiry date of the Benefit|
|Issued||The date the benefit was created|
|Definition Id||The Benefit Definition associated to create this Benefit|
|Profile Id||The Profile Id this Benefit is issued to|
+ the properties of the Benefits Definition.