Unibo requires complete game and player list. This information is essential for setting up Unibo campaigns effectively.
GDPR ComplianceUnibo adheres to GDPR regulations and does not store any personally identifiable information (PII) such as names or email addresses. All stored information is solely used for player segmentation and campaign management.
Integration
Unibo supports the following methods for data integration:
Event Stream:
Player and game data are sent by the platform through 🔀Event Feed requiring:
Initial seed once Unibo is enabled for Casino, so we have every registered player and available game.
Incremental updates to reflect changes (new games, new players, changes in tags/categories/any_relevant_fields)
Dedicated API:
The platform implements an endpoint(s) to enable Unibo to fetch all required player and game data.
Get all players/games (so we can initialize our empty database and sync once a day just in case we miss something)
Get players created/updated within the last 5 minutes (so we can check every 10-60 seconds for new/updated players/games)
Data examples
Player
Title
Title
Title
Field (* = mandatory)
Data Type
Additional info
id *
String
Unique identifying value
currency *
String[]
ISO-4217 currency code
country *
String
2 letter ISO 3166-1 country code
registrationDate *
String
ISO-8601, UTC
gender *
String
"M" = Male
"F" = Female
"O" = Other
status *
String
Any of "ACTIVE", "BLOCKED", "FROZEN" or "INACTIVE"
affiliateName
String
playerTags
String[]
Game
Title
Title
Title
Field (* = mandatory)
Data Type
Additional Info
gameId *
String
Example: "4399 or btg/bonanza"
gameName *
String
Example: "Bonanza"
gameProvider *
String
Example: "Big Time Gaming"
gameCategory *
String
Example: "table-games"
gameSubCategory
String
Example: "blackjack"
The above can be adjusted depending on your use case and will be discussed during the kickoff meeting.