Step 1: Data Connector
To utilise Yapster’s KPI Games module, an EPOS data connector will need to be established. This can be established directly from your EPOS provider or your internal reporting tools.
Here are Yapster’s daily data transfer options in order of preference:
CSV files are put to our SFTP (which is public-key only auth)
We will share host and location details and request your SSH-public key, once we apply this to the account you’ll be ready to start transferring files.
get CSV files from your SFTP
You will share host and location details for us to access.
CSV files stored on one of our S3 buckets shared with you
We'll need to share account, bucket and role details.
CSV files stored on one of your S3 buckets shared with us
You'll need to share account, bucket and role details)
Step 2: Game Data
So what should you be including in the files you share with us?
You can decide which measures are to be used in a game - it can be anything really but should have some suitable scaling factor (e.g. the number of staff, previous year's figure, total sales) so that smaller sites can compete fairly against larger sites.
Once a measure has been determined then we will need a CSV with fields for (at least):
timestamp (ideally ISO8601)
participant-id (we’ll need to confirm this matches the ids in Yapster)
KPI measure
scaling-factor measure
Please find more detailed data requirements in our Business Data/EPOS Data Specification Article.
Here are some example competitive-measure / scaling-factors :
beer-sales / all-drinks-sales
anti-reflective-lenses / all-lenses
average-transaction-value / target
dessert-sales / covers
additional fields which make the CSV more human and readable can make life easier include:
site name
measure name (e.g Pina Colada sales)
scaling factor name (e.g total cocktail sales)
We'll need the rows in the CSV to be provided at a finer temporal granularity than our game period intervals - so e.g. if we are running daily game update intervals then we would need daily or finer reports (we'll then aggregate from whatever we get to the game period interval).
Step 3: Game Configuration
Game configuration relates to the specific setup details for the games such as:
Season/Tournament Name
Start Date
Number of Rounds
Participants
Gamification format - Knockouts or Leagues
etc.
Please Note as the Leagues have recently been released, we have temporarily suspended support of the knockout format - For more information, please contact your Yapster Account Manager |
For more configuration options, please see our KPI Gamification - Leagues Article
Step 4: Practice Game
Where a wider group of stakeholders need to 'see' a game unfold before approval is given to roll out, we will run the game at the same pace as a live game. This is a practice game with the real participants data but will only be visable to the relevant shareholder. This ideally will be run on live data so this can be used as an opportunity to test the data feed and the for the sponsor to confirm the config options but historical customer data can be used if needed - This will be exactly what live users will see except that the live users will not be included in the conversations.
What we need from you at this stage in addition to the configuration details for the real game:
Watchers list (this may include any executive stakeholders necessary for sign off).
Date to start the Practice Game - no less than T-1-week from proposed go-live date, to allow adequate time for any config amendments to be flagged and implemented.
Step 5: Kick Off
Once the above steps have been taken and you've confirmed the practice game is configured correctly, you need to re-confirm all is in order for the kick-off date and to prepare your leadership team to boost and engage with the games, ready for your team to excel!