2022 Q3: Event as Criteria in Reward Campaign – Chatbot test

Summary 🚀
Details ☀
API-based criteria vs Event-based criteria
Mandatory events and property schema to be compatible with Setel Rewards
How to get started 🧭
Release Plan 🧭

Interface	Setel Admin / Platform
Release version (Android)	1.104
Release version (iOS)	1.104
Team	Gamification / Experience

Summary

Introducing Event as Criteria in 1.104.0! Setel Admin can now setup variety of reward campaigns on Admin Portal with events (backend) as action criteria to grant rewards & badges.

Exclude from Release Notes; not consumer front-facing feature

Details

Reward campaigns in the past require each team to make direct API calls to reward service to grant badges and rewards. This means, when ever any teams ships a feature, and wants to gamify it, additional development is required to make API calls to reward service - we call this API-based criteria.

https://setelnow.atlassian.net/wiki/spaces/PER team has since enhanced the reward service to also accept Event-based criteria. This means, your team investment on implementing Events to track user analytics (Mixpanel), and engagement (Braze) can now also be used to issue badges and rewards (Setel Rewards).

To fully leverage, Event-based criteria capabilities, read further on how to implement events in a schema that complies with Setel Rewards here

API-based criteria

API-based criteria has been the default way to start gamifying your feature interaction.

Scope

Description

Focal

Implementing user action as criteria via API calls to reward service

Requires integration and enhancement from both teams to add new criteria

Feature teams: send relevant payload/data to api-rewards, integration to rewardSDK
- Reference: action payload
Experience: enhance Reward Campaign using the data received from payload

Respective use case owner teams
Experience

Updating reward service to include new criteria in campaign mechanics

Update new criteria in listing of supported reward criteria on Reward Campaign

Experience

Event-based criteria

With Event-based criteria teams will have the option to either connect your services to reward service by using Events already built for analytics and engagement. This saves you time from additional investment to make direct API calls.

Team scope

Description

Focal

Defining event(s) to be utilised in Reward Campaign as criteria

Setting of events and its properties
Sending of backend events to api-analytics (i.e. MixPanel or Braze)
- Reference: analytics event as criteria

Integration of payload to rewardSDK or api-rewards no longer required by respective teams

Newly added events require +/- 2 days to be updated in reward campaign

Respective use case owner teams

API-based criteria vs Event-based criteria

With both API and Events available for you to gamify your feature, refer to this section to understand further the circumstances where we would recommend one over the other.

		API-based criteria	Event-based criteria
1	General
2	Backtracking of user action (e.g. action prior to campaign launch also counted as progress)	Supported for most criteria Have the option to grant user rewards/badges based on action done before campaign is launched	Unsupported Only grants based on action after campaign is launched
3	Adding a new user action criteria to gamify	Requires new API call implementation	Not required if already have backend events sent
4	Update to existing user action to be more specific (e.g. new top-up method)	Require enhancement from relevant teams.	Enhancement required to add new property in existing events
5	Reward criteria
6	Can be used with other main and supporting criteria Limit to first x users Remaining time (days) Max reward amount		Available as of `ETA: 1.118 (end March 2023)`
7	Fixed cashback
8	Mesra points
9	Percent of cashback		Supported Number Integer Double Unsupported Timestamp Boolean i.e. `setelMember = true` String i.e. `twenty` Enhancement to convert event property if numeric value detected `ETA: 1.118 (end March 2023)`

Mandatory events and property schema to be compatible with Setel Rewards

Description	Compatible	Unsupported
Events	Events from backend E.g. `fuel_process_order_complete`	Events from mobile app e.g. `app_ads_pin_click` Events starting with symbols e.g. `$ae_session` or `%account_login`
Properties	String Example: String `Youbuy Online Sdn Bhd` Boolean Example: Boolean `true` or `false` Datetime Example: Datetime `2022-12-15T23:59:59` Integer Example: Integer `12345678` (card number) Decimal Example: Decimal `10` (Ringgit)	Object Example: Object `{"name": Youbuy Online Sdn Bhd", "reference": PO-00255102"}` Array/Struc Example: Array/Struc `["GARDENIA DELICIA CREAM ROLL-JAGUNG", ["CORNETTO HERSHEYS EX 85G""]` JSON Example: JSON [ { "id": "app_fuel_subsidy", "option": "fuel_subsidy", "order": 1 } ]
Event payload	Every event payload should have a unique reference id (`aggregateID`) along with `userID` `DistinctID`: represents user who is performing the action `AggregateID`: represents the unique id for that event. i.e. `wallet_success` = transaction ID Failing to set unique `aggregateID`, will result in only one (1) action recorded and being overwritten every time action triggered for the relevant action. Refer to Guide for Event as criteria for technical breakdown
Event payload	Event selected: `fuel_order_process_complete` distinctId: userId aggregateId: orderID	Event selected: `fuel_order_process_complete` distinctId: userId aggregateId: userId