Achievements (Badges)
An achievement is a graphical reward given when a User has performed a certain number of defined tasks. Usually represented as an icon graphic with a name and description.
Challenges
A challenge is similar to an Achievement but is usually easier to earn. Challenges normally award points.
Points
A numeric reward or currency that can be awarded to a User when they have performed a certain number of defined tasks.
Leaderboard
A leaderboard is a visual ranking of Users based on Points, Level or Achievements earned.
Partner
A Partner represents an account in our system. It represents a specific business or website which is interacting with IActionable’s services and features.
User
A User represents an individual who interacts with your website or service.
Profile Type
A Profile represents a User, Group or Entity that performs events and earns rewards within the IActionable system. A Profile can be assigned multiple types of identifiers. Custom Profile Types can be created with the system and are represented by their ProfileTypeKey.
Examples: Users, Players, Teams, Groups
Profile ID
A unique value which identifies a specific Profile interacting with your website or application. An ID Type value is required whenever a Profile ID is provided in an API call.
Profile ID Type
A value which describes the type of Profile ID provided in a service call.
Examples: Email, Facebook, Twitter, PhoneNumber, OpenID, GUID, Username, Custom
Event
Events represent an action performed by a Profile on your website. They are identified by a value called the EventKey. Only Letters, Numbers and _ are acceptable values.
Example: UploadedPhoto
Attributes
Attributes are additional information about a specific Event which has occurred. Attribute data can be used when creating rules within the IActionable system.
Example: PhotoID=5, Size=Large
Condition
A condition is a specific task with a numeric criteria that must be met. Conditions are evaluated when a Profile (User) performs an action associated with the requirements. Conditions can configured to behave like SQL queries. Functions such as Count, GroupBy, Distinct and Sum are supported.
Requirement
A requirement behaves similar to a condition. It determines whether the visibility and whether progress can be made for a reward. This is typically used when chaining related rewards together.
Action
An action is something that is performed when all the conditions of a rule have been met. Rewards such Achievements and Points are two types of actions. Other actions such as Email, WebHook and Notifications will be available soon.