Actions

An action is a trackable activity performed by a user. They are the building block of all programs.

Some actions are automatically logged by Nitro for certain activities. See Bunchball Go Actions and Pages and Nitro Metadata for Nitro defined actions and metadata.

While there is no limit on the number of actions you can define, they generally fall into the following categories:

Category	Examples
Consuming Content	Watching a video Reading an article Taking a quiz
Creating Content	Uploading documents Creating or editing documents Commenting, reviewing, or rating
Tracking Performance	Making a sale of "x" amount Closing a case Completing training
Engagement Activity	Logging in Registering Signing up

Passive Actions

Passive actions are activities that are tracked on the user's behalf, but the activity cannot be completed in real-time. An example of this may be sending previous course completions or when the user receives a recognition.

Nitro tracks all action data (passive and active), but can remove passive actions when analyzing program success since those actions may not be considered activity resulting from the program. Passive actions also help provide a clearer picture of how many users are actively participating in the program as passive actions may be sent to Nitro for a user without that user interacting with the program. Note: Action data, including passive actions, logged for users will contribute toward your active user count.

Track Actions

Gamification is based on tracking actions. When an action is recorded, it triggers Nitro to process the action’s defined outcome. For example, an action may complete a mission that awards points, a badge, or adds an entry to an events feed. Actions can be triggered automatically (e.g., when a user clicks a button on your site) or can be manually logged by the administrator (e.g., a user attends a conference and the admin applies that action to the user ID). Actions are logged when data is sent to Nitro manually, via batch load, or using an API call.

You can:

Limit how often a user can get credit for completing a particular action.
Send metadata with an action to add specificity and allow you to use the same action for different tasks of the same type.
Send a value with actions that have numerical goals associated with them.
Retrieve a user's action history to understand what they've been doing on your site.