Create a Mission

Missions focus on rewarding and providing feedback on ideal behavior. Missions are created for an individual or a group where everyone participating has the same goal for mission completion. Consider your program strategy as you create missions.

Before creating a mission:
- Create actions
- Create your program imagery
- Create groups (if you plan to limit who can participate in the mission)
Open Nitro Studio > Motivate > Missions.

Click New.

Use the Details modal/tab to add or edit the mission details.

Field	Description
Name	The unique mission name. The mission name displays to users if no Display Name is set.
Display Name	The non-unique mission name to display to users. When set, the display name shows in place of the mission name.
Party Type	Select what type of action the mission will need to complete it: User - Action(s) logged for a user. The mission will be awarded to individual users. Group - Action(s) logged for a group. The mission will be awarded to a group.
Description	The mission description. This field does not support encoded characters such as bullets.
Browse for an Image	The icon to show for this mission. If the mission awards a badge, typically the badge image is used here. Icons can be added or edited in the header section using the edit ()button.
Background Image	The image to display as the background of the mission tile in Impact or a custom build. The background image is not used by web components or Bunchball Go. You can upload an image or link to an image on a server that Nitro can access. Note: The file name cannot contain parenthesis.
Action Phrase	The message to show in the Events web component once the mission is completed. This is generally an acknowledgment of the mission completion. The action phrase can contain tokens.
URL	Add a URL to show a "Do The Mission" link in the Missions web component. Typically, URLs are set in the mission's rules to link to the specific task, but you can use this as a link to additional information. Popup blockers must be disabled for the link to open the URL on mobile devices.
Importance	Select an importance to influence how the mission is ordered.
Featured	Select to set the mission as featured. Featured missions display in the Featured section in Impact and first in the mission order within Nitro Studio and the Missions web component.
Labels	Click the Add label () button to assign one or more labels to the mission. Labels can be used to filter missions in Nitro Studio, Impact, and the Missions web component.
Hidden Mission	Select to hide the mission until a user or group completes it.
Custom Data	Your custom data that is returned in API responses such as /users/{userId}/challenges/{challengeId}/progress. Common uses are enriching the end user experience with more contextual information, filtering, sorting, or passing additional information to other applications.

Use the Availability tab to add or edit the mission availability.

Field	Description
Start Date and End Date	Select to limit the mission to a specific date/time range. When backdating a mission, any previously logged actions will not count toward mission completion. Only actions logged going forward will apply. If you need to backdate a mission and log backdated actions, learn more here. Note: The date/time registers according to the time in your browser/computer's timezone. If an administrator in New York sets the mission to start at 9:00am EST, the mission will start for users in California at 6:00am PST.
Search for a timezone	Select a timezone to show when the mission will start/end in a timezone different from the administrator's timezone. This is for Nitro Studio display only; the mission's date/time is sent to the platform as a UNIX timestamp and does not have any associated timezone.
Repeatable Mission	Select to allow users to complete the mission more than once. Each time the user completes the mission it unlocks and they can start it again. Mission progress does not roll over when a repeatable mission is completed; it resets to zero. Do not set a quiz mission as repeatable. The mission would continue to show as an eligible mission, but the quiz would be unavailable once completed. Changing a mission from repeatable to non-repeatable may cause issues in your program. Once you choose to make a mission repeatable or non-repeatable, do not change this setting.
Daily Achievement Limit	Select how many times a day a user can complete a repeatable mission. Unlimited - The mission can be completed multiple times per day. Limited to - The mission is only available the defined number of times per day. Note: This limit does not have backdating support. It uses the current date/time (in Pacific Standard Time) when the action comes in.
Total Completion Limits	Select if this mission is limited or unlimited: Unlimited - The mission can be completed by an unlimited number of users. Limited to - The mission is limited to a set number of completions. Once the mission is completed the set number of times, it's no longer available. To keep the mission active after a limit is reached, set a limit on the mission's reward. If you add additional missions, the mission will reactivate and additional users can complete it. Any actions logged for this mission when it was inactive (after the limit was reached and before the limit was increased) will not count toward mission completion.

Use the Participants tab to define who can participate in the mission.

Field	Description
Group	Select one or more groups and define the inclusion or exclusion status. Included - Limits the mission to users within a selected group. Excluded - Users in a selected group cannot participate in the mission. Note: If you're creating a mission for a quiz that has a limited number of attempts, you need to manually add a prerequisite if you did not automatically create a mission for the quiz when the quiz was created. This prerequisite will make the mission unavailable if the user does not pass the quiz before the set number of attempts is reached. Add an exclusion for the group named quiz_[quizId]_ineligible.
Group Class	Select one or more group classes and define the inclusion or exclusion status. Included - Limits the mission to users within a selected group class. Excluded - Users in a selected group class cannot participate in the mission.
Mission	Select one or more missions and define the inclusion or exclusion status. Included - Limits the mission to users who have completed a selected mission. Excluded - Users who have completed a selected mission cannot participate in the mission.
Level	Limits the mission to users in a selected level. This level and above -Limits the mission to users within the selected level and any levels above the selected level. This level ONLY - Limits the mission to users who are in the selected level. This level and below - Limits the mission to users who are in the selected level and any levels below the selected level.
Country	Select one or more countries and define the inclusion or exclusion status. The Country attribute is set in programs integrated with the Global Rewards Marketplace. Included - Limits the mission to users in the selected countries. Excluded - Users in the selected countries cannot participate in the mission.
User Verification	Limits the mission to users who match the selected verification status. A user's verification status is set in programs integrated with the Global Rewards Marketplace.
Must meet ALL prerequisites and Must meet at least ONE prerequisite	Select to define how prerequisite tiles are linked. Prerequisites within the same tile assume an OR relationship. For example, you could set up a mission using two tiles to allow users in groupA OR groupB OR groupC AND level 3 to participate in the mission.

Use the Rules tab to define what users must do to complete the mission.

Field	Description
Rule Type	Select the type of rule to create. Number of Actions - The number of times a user must perform the action(s). For example, watch 10 videos. Action Value - The value for the action that a user must achieve. Value is logged with the action and can be used for rules that have numeric goals associated with them. For example, obtain a score of at least 90. Note: An action value can be a decimal. Value Range - The number of times a user must log an action with a value that falls within the specified range. Use the Value Range fields to set the range that the value must be within, and Completed x times to set how many times that must occur. Using Value range with no minimum or maximum values is the same as using the Number of Actions rule type. Running Total - The total value a user must accumulate. Nitro tracks the action value within each action that you log with the same name, adds the values, and completes the mission when the user reaches the goal. For example, if you have a sales goal of 1 million dollars, the action values will be added until the 1 million goal is met. This may take one user 4 sales of 250k each or another user one sale of 1 million. Time Window - The number of times a user must perform the action within the specified time frame. For example, watch 5 videos within 2 days. Once a user completes the first action, the time window begins. When the user completes the required number of actions, the mission completes (and restarts if repeatable). If the user doesn't complete the required number of actions within the time window, the user's progress is cleared and the mission restarts. Show me how time window works with repeatable missions When a time window rule is used for a repeatable mission, the mission does a lookback to count all the actions in the time window and award the mission whenever the goal is met. The action count is cumulative and does not reset when completed. For example, you have a repeatable mission with a time window rule to complete action A 2 times in one day. If a user completes action A 3 times within a day, they will complete the mission twice. 1. Action A is logged the first time (8:00am). 2. Action A is logged the second time (12:00pm). The user is awarded the mission. 3. Action A is logged a third time (4:00pm). The mission looks back 24 hours, counts the actions logged within that window (4:00pm and 12:00pm), and the user is awarded the mission again. Quiz - The quiz outcome (passed or failed) that's required for the rule to complete. Self Reporting - Users can self-report that the task has been completed.
Rule Description and Rule URL	A description of the task that must be done to complete the rule and the URL where the user should go to complete the task. For example, if the task is to complete a training course, the URL can link to that course on your training site. The description displays in the mission detail's task list. To link to a page in Bunchball Go, use the format: #/[page name]. For example, #/community To link to a quiz in Bunchball Go, select the quiz and then click Copy Quiz URL to auto-populate the URL. To link to a quiz in Impact, you do not need to add a URL. Impact automatically opens the selected quiz. To link to a quiz in the Quiz web component (non-Bunchball Go), add the call to the .html code. See setup here Popup blockers must be disabled for the URL to open on mobile devices.
Subtask Description and Subtask URL	Additional information or links for tasks within the rule. For example, you have a rule that requires users to review training material with three options for accessing the content. You can set the rule description and URL to a website, and then set subtask descriptions and URLs to alternate formats such as a PDF or video. Subtasks use an OR structure which means the user could visit the website, read the PDF, or watch the video to complete the rule.
Action Criteria and Metadata	The actions that are required for the rule to complete. If you add multiple actions to the same rule, they assume an OR relationship and any combination of the selected actions will contribute toward completing the rule. Show me an example You have Number of Actions as your rule type and set the number of actions to be More than or equal to 5. Then you select WATCH_VIDEO as one action and READ_ARTICLE as a second action. A user can complete the rule by watching 5 videos, reading 5 articles, or watching 2 videos and reading 3 articles. Metadata allows you to define other contextual information for the action. See Metadata for rules, details, and recommendations. If multiple metadata requirements are added to one action, they assume an AND relationship and all metadata names and values must be logged with the same action to count toward the rule. When you save a self-reporting rule, metadata is automatically added or updated for that rule.
Select Quiz	The quiz required for the rule to complete. If your mission is to take any quiz, use the Number of Actions rule type with the QUIZ_COMPLETED action instead of using the Quiz rule type. This allows your mission to be non-quiz specific.
Must complete ALL of the following and Must complete ANY of the following	Select to define how rules are linked. Elements within the same tile assume an OR relationship.

Use the Rewards tab to define how to reward users who complete the mission.

Field	Description
Reward Type	Select a point category or Badge as the reward type.
Upload Image	Upload the badge to award.
Amount	The number of points to award from the selected point category.
Reward Limits	Select if this reward is limited or unlimited: Unlimited - The reward can be earned by an unlimited number of users. Limit total amount - Limit the reward to a specific number of points. Once the set point threshold is reached, the mission will continue but users will not earn this award. See Point Awards and Limits for instances where your total amount may be exceeded. Limit by time - Limit the reward to a specific number of days. Once the date is reached, the mission will continue but users will not earn this award. The mission's start date is used to calculate the reward limit's end date.
Who will receive this reward?	Select who will earn this reward. Note: Reward segmentation is only available for user missions. You cannot segment rewards on group missions. All participants - The reward can be earned by all users. Only participants in selected Groups - Limit the reward to users in a specific group(s). When you add multiple groups, they have an OR relationship. Therefore, if the user is in any of the selected groups, they will be included or excluded from the reward. See Point Award Limits to learn how users might earn duplicate rewards. Only participants in selected Levels - Limit the reward to users in: This level and above -Only users within the selected level and any levels above the selected level can earn the reward. This level only - Only users who are in the selected level can earn the reward. This level and below - Only users who are in the selected level and any levels below the selected level can earn the reward. Only participants in selected Countries - Limit the reward to users in specific countries. When you add multiple countries, they have an OR relationship. Therefore, if the user is in any of the selected countries, they will be included or excluded from the reward. The Country attribute is set in programs integrated with the Global Rewards Marketplace.
Multiply all point rewards by the action value	Select to multiply the award amount by the action value. This option is only available if your mission has a single rule with the Action Value rule type. Show me how this works If a user completes an exam and the score is passed as the action value, you can award the user more points for a higher score. So if the reward Amount is set to 1 and user A scores an 80 on the exam, they earn 80 points for the mission. However, if user B scores a 95 on the exam, they earn 95 points.

Use the Bill Codes tab to override global bill codes for this mission. Bill code information will only show if you have custom global values set that can be overridden.
1. Click Edit this instance for the custom value you want to change.
2. Enter the new value and click Save.
In the mission header, click Make Active to activate the mission.

The mission is active for all users unless you set restrictions on the Participants tab. Once the mission is active, users can make progress toward achieving the reward.

When logging actions that happened in the past, a mission must be active before logging a backdated action.