There are several pre-defined Facts that are readily available in your 99minds account. For example, customer name, billing address, etc., are examples of some of the facts. Each of these facts are associated with Entities like Customer Session, User Profile, Loyalty Points, Order Details and so on. In simple terms, an Entity is a group of Facts bundled together. While the User Profile is an entity, user name, date of birth etc., are the facts that belong to the User Profile entity.
Facts and entities are very powerful elements of the 99minds app. Make sure that they are created correctly by your technical team and correctly mapped to your integration. These facts and entities can be used when building the rules for your campaigns and can be added to rules according to your requirement.
The primary entities of 99minds loyalty engine are -
- Campaigns - Rules, Coupons and Referrals
- Customer Profiles
- Customer Sessions
99minds API receives the requests from the connected applications such as e-commerce applications. The application connects to the API and sends updates about the customer information. Each application is defined by the Application Key, Currency and Time zone.
Campaigns - Rules, Coupons and Referrals
Campaigns are nothing but the combination of rules and actions that are created by marketers. Rules are conditions that must be satisfied in order for the action phase to execute. For example, a rule can be defined as "When the order value is greater than $100, and the customer has shopped at the Broadway store". Once a match is found for the rule condition, the corresponding action will be taken. Actions are the steps that are performed when a rule match is found. An action can be defined as "Provide 10% discount to customer AND add 10% of order total as loyalty points". Similarly, different actions can be taken such as sending customer emails/notifications, send requests to external Webhooks or other APIs, and so on. Every campaign is defined by the Start and End date, Campaign Budget and Campaign Attributes. A campaign can contain multiple rules, coupons and referrals. Every rule is defined by Rules and Actions.
Coupons are defined by the Coupon Value, Coupon Validity and Coupon Usage Limit. Coupons also belong to the campaign. Coupons can be personalized and specific to a customer, specific to a store or a region. When the customer redeems the coupon, the coupon value will be automatically deducted, and the usage limit will be increased by 1 at the end of the session.
Referrals are also defined by Value, Usage Limit and Validity. Unlike coupons, referrals work in a slightly different way. Once the referral code is redeemed, both the customer (the one who uses the referral code) as well as the referrer (the one who provides the referral code; also known as the Advocate) will receive the rewards respectively. The referral codes will be redeemed when the "Redeem Referral Code" action is triggered by a rule in the campaign. Similar to coupons, the referral code value will be automatically deducted, and the usage limit will be increased by 1 at the end of the session.
When the application integrates with 99minds API, the application sends the customer information in the form of FACTS such as customer names, email address, home address, phone numbers, etc. Every customer profile requires a unique ID. It is very important that you define the unique ID correctly in order to be able to refer the user in the system. The unique id should remain stable for the user. For instance, mobile number and email id are not the right candidates for unique id as there are more chances for users to change them.
Customer session refers to the time the customer has been active within the application. In simple terms, it is the time from when the items are scanned till the time the customer makes the order finalized. Once the order has been finalized, no updates can be done to the session unless you want to cancel the session. Once the payment is done, the customer session is termed to be complete.
Similar to customer profiles, every session requires a unique ID. Some of the most common session ID's that can be used are session start time, customer order number, etc.,
Every customer session will have multiple user actions. Every action gets recorded as an event and sent to the API. For instance, when the customer adds an item to the cart, a specific event will be triggered to the API corresponding to the action. You can also create custom events based on the user activities. Say, a user visits a hot selling product, you can trigger an event specific to this user activity and offer a reward or an incentive to the customer.