Gamification Cloud

Creating a new achievement using the ZIQNI platform can be completed in a few simple steps. 

The user works through tabs at the top of the page, using the 'previous' and 'next' buttons. They will be able to move between tabs to amend any information as they create an achievement. All required information is marked with an asterisk. Once all information has been entered and the Achievement has gone live, only limited fields can be edited. 

The information below provides an overview how to create an achievement. To access the API for achievements please click here. 

From the dashboard page, scroll to Achievements and click.

Once the create button has been clicked, the page below will load.

Settings

The first step to creating an achievement in the ZIQNI system is to generate the settings. This is where the user inputs the basic information required for the Achievement.

• Name the Achievement. This is the only mandatory field on this page and is limited to 500 characters. Examples could be 20 Free Spins, XYZ Promotion.
• Group the Achievements using tags.  Tags can be selected from options that have already been created or you can type and add tags directly in the box. Multiple tags can be selected.
• Write a short description of the achievements This is for reference only and is an optional field. This is limited to 500 characters.
• Include the terms and conditions. These set out the instructions for the achievements.
• Choose an Icon or Banner to be displayed for the achievment. These must have already been uploaded into a folder in the CMS system.
• Add metadata to describe and extend the achievement, using a pair of values and keys.
• Once all information has been entered, click next.

Scheduling

This creates a timeframe for the Achievement. 

• Choose when the Achievement will be available. Use the drop-down menu to choose a date and time. 
• Decide on the end date for the Achievement, if no end date is chosen, the only way to end the Achievement will be to delete it.
  
• Using the drop-down menu, select when members can achieve. For example - Once, Repeatedly (each time the rules are meant until the achievement ends), Daily (can choose specific days), Weekly (can choose specific weeks), Monthly ( can choose specific months) .
  
• Use the toggle to decide if there will be a maximum number of times the Achievement can be awarded. If left off, the user can achieve an unlimited amount of times. If switched on, a limit can be set for the number of achievements a user will be able to claim.
  

 Entrants

This tab sets the criteria for the groups of members who can participate.

• Choose if members will need to manually opt in to participate.
  
• Use the toggle to choose whether all registered members can participate or just select groups. If the toggle is on, all registered members can participate. 
  
• Move the toggle to off to choose select groups. 
• Click  Select Member Tags and the page below will load.
• Check the boxes of the member groups that will have access to the Achievement. Once all member groups are chosen, click add. 

Once all member groups have been added, the following page will load. The user will select the dependencies for the member groups to participate using the must, should, must not rules. 

• Must-  for the member group to participate they must have this tag.
• Should -  for the member group to participate they should have this tag
• Must Not -  for the member group to participate they must not have this tag. 
• Ensure the minimum should match is correct - this sets out the minimum number of tags that have to match in order for a member to be eligible for the achievement.

Step 4: Dependent on

Dependent On is where the user creates rules linking different Achievements, therefore at least one other Achievement must already be created for this to occur. The dependency of the other Achievement is set out as a Must, Should, Must Not rule. Simply put there are Achievements ABC. A must be completed before you can achieve B.  If A or C has been achieved then B should be achieved. 

If it was a prize-giving competition, the user may state, that if A is achieved (a prize has been won) the B must not happen. (another prize cannot be won ). Using the Dependent on rules is an optional step.

• Click Dependent On and a list of previous achievements will appear,
• Check the Achievements that are to be included in the Dependent section and click Add.

The page below will load. The user will select the dependencies for the Achievements to be linked using the must, should, must not dependency rules. 

Rules

Using Ziqni's rule engine the user can create as many different rule combinations as required from simple to extremely complex. In Achievements the rules are the criteria that are set for how the member will access the Achievement. 

Please refer to the ZIQNI's Rule Engine articles for a more in-depth explanation and examples of how this can be used. 

• Choose how the rules will be structured - rules can be created using any are true statements or all are true.
• Click on the + sign to add further criteria to the rules.
• Complete the then statement to award the achievement to the member.

The action buttons in the top right-hand corner of the Rules page allow the user to access a number of features. 

• <> Displays the JSON string along the right-hand side of the screen.
• Reset allows the user to delete the rules and begin to create new ones.
• Save as template - a string of rules can be saved as a template for future use.
• Load as Template - load previously saved rule creations.
• Arrow Icon - Expands the page to allow easy creation of more complex rule structures. 

Rewards

Creating a reward in Achievements is optional. In Achievements a reward will be triggered based on the rule structure. Multiple rewards can be created for an Achievement.

• Select the reward icon.
• Give the Reward a name for example - Congratulations Badge
• Group the Reward using tags.  Begin typing into the tag field and the list of tags will appear. Multiple tags can be selected.
• Determine numerical the value of the reward. This number is the quantity of the reward. For example: How many badges?
• Decide the reward type from the drop-down menu. This will have to have been created in Settings --> Reward types. 
• Use the toggle to decide if set the point in time is on/ off. When on this allows the user to set a date for the reward to expire for all members. When set to off the user can decide on the period of time a member has to claim their reward, for example, 5 days.
• Create a time delay in minutes which will provide a number of minutes between the achievement being triggered and the reward being issued
• Select the period of time the member has to claim their reward until it is no longer valid, for example - must be claimed in 5 days.
• Write a short description of the reward.  This is for reference only and is an optional field. This is limited to 500 characters.
• Decide whether Acknowledgement is required for the reward- Does the member have to manually claim the reward or is it issued automatically?
• Set an issue limit - this is how many times the reward can be claimed. There is a direct relationship between the issue limit and the number of achievements. The reward issue limit cannot be more than the total number of achievements set. 
• Add metadata to describe and extend, using a pair of values and keys.

Add a Reward from Template

• Add a previously created reward to an Achievement using a template. 
  
• Click on Add from template. 
• The screen below will load. 

• Choose from the list of previously created rewards by checking the box next to the reward. 
• Click on the Add button. 
• The Edit page will load,  from here information can be edited if required. 
• Once all information is correct, click on create
• The reward has now been added to the competition/ contest.

Products

Products can be added to achievements, filters can be used so that only specific products are selected. 

• Use the toggle to choose whether all registered products will be inlcuded or just select groups. If the toggle is on, all registered produtcs will be available. 
  
• Move the toggle to off to choose select products. 
• Click  Select Indvidual  Products  or  Select Product Tags and the page below will load.
• Check the boxes of the individual products or the product tags that will be available in the Achievement. Once all are chosen, click add.

Once all individual products or product tags have been added, the page below will load. The user will select the dependencies for the products using the must, should, must not rules. 

Translations

The languages are pre-set and must already be added in the language settings. If these have not been added, translation will not function.

If additional languages are required, go to Settings → Languages and add a new language. 

• Select the language the fields are to be translated into.
• The text that can be translated is automatically pre-populated. The user must write the translation into the translation box. 
• Once all fields have been translated the language name will have a green check to show it has been successfully translated. Another language can then be chosen if required.
• If the translation has not been successful (something has been left out) the language will have a pink exclamation mark to let the user know there is an error.
• Click next once all translations have been completed.

Summary

This allows the user to preview all information that has been entered. 

• Use the arrow icon to open each section to preview the summary.
• If any edits are required, this can be done by moving between the tabs. All information can be edited at this stage. Once the reward is created, specific information will be locked and will no longer be able to be edited.
• When all information is correct, click on Finish and the Achievement has been created.
• A preview page will now load, from this page, information can be edited or deleted using the Action button.
• Once the edit page opens, only information with a white background will be editable.