Skip to content
  • There are no suggestions because the search field is empty.

Game Recommendations - Getting Started Via Playtech

Everything you need to know about third party integration via Playtech 

Overview

This guide walks you through enabling Amplifier AI’s Game Recommendations for operators whose sites are hosted by Playtech Managed Services. Amplifier AI personalises casino lobbies and journeys by ranking the most relevant games for each player. For Playtech operators, recommendations are requested from the player’s browser (validated against Playtech IMS webAPI), then fulfilled by Future Anthem and returned to the site.

Requirements

  • Active subscription to Amplifier AI — Game Recommendations.
  • Casino front end hosted by Playtech Managed Services with access to staging & production sites.
  • Ability to create a batch or real‑time event stream (Kafka) from Playtech data to Future Anthem.
  • Client certificates issued by Playtech for the recommendation middleware.
  • Test accounts (staging & production) and access to IMS web APIs for session validation.
  • Ability to call Amplifier AI endpoints from your CMS/front end.

Quick Start Checklist

Step 1 — Request module activation

Contact your Playtech technical account manager to coordinate access: request client certificates for the IMS LoginRequest webAPI and share Future Anthem IP addresses with PlayTech for whitelisting. Share brand/site domains and ensure staging & production access with test accounts.

 

Step 2 — Data feed setup


Create the batch or real‑time Kafka JSON feed to Future Anthem and validate the required field mappings (playerCode, username, gameId, roundId).

 

Step 3 — Integration & testing

Have Playtech Managed Services integrated to the Game Recommendation API (primary). Once the integration is complete, it should be possible to login with a test account, which will initiate an API request with the required parameters.

 

Step 4 — Go live & measure

Switch to production consumption and monitor target vs control KPIs.

 

Step‑by‑Step Setup

Step 1: Request activation with Playtech Technical Account Manager

Goal: Turn on the integration, security, and access.

  1. In order for Future Anthem Game Recommendations to be activated, contact your Playtech technical account manager to coordinate the required access:
    1. Request client certificates for the IMS LoginRequest API (lead time typically ~4 weeks).
    2. Provide PlayTech with Future Anthem IP addresses to be whitelisted for the LoginRequest API calls.
  2. Provide brand/site list and confirm domain conventions.
  3. Ensure access to staging and production websites and test accounts for each.

Outputs: Request raised with the Playtech technical account manager; client certificates for LoginRequest API in progress; IP whitelisting submitted; environment access (staging & prod) and test accounts assigned

 

Step 2: Data integration & validation

Goal: Enable the real‑time data feed and align required fields.

Data feed (per Playtech): Batch data or real‑time JSON event stream via Kafka from Playtech → Operator → Future Anthem, containing at minimum:

  • playerCode (Playtech userId token passed to Anthem as playerCode)
  • username (not ingested by Anthem, but required in game recommendation requests)
  • gameId (Playtech gameType)
  • roundId (Playtech windowSessionCode)
  • Date, Time
  • Site (any hierarchy on Network/ Operator/Site/Skin, etc.)
  • Balance Type Used (Free spin, Promo Spin, Account balance)
  • Jackpot Payout, Stake, Payout, Balance, Currency

Meta data we typically receive:

Amplifier AI utilises data about the available games, such as: Game id, game name, Game type (Slots, Instant win, Table Games, etc.), provider, launch date, RTP, Volatility, Theme, Win lines, Min bet, Max bet, Default bet, Jackpot type, Layout.

This data is needed to support Amplifier AI recommendations models in accurately categorising and analysing game similarities, game performance, and betting patterns.

Examples: See the Standard Data Integration Guide.

 

Step 3: Integration & testing

Goal: Exercise the recommendation flow end‑to‑end in staging and production.

Environments

  • Access to staging and production websites with test accounts for each.

Request path

  1. Upon login, the player’s browser initiates the API request with required parameters.
  2. Middleware validates the sessionToken with Playtech IMS webAPI.
  3. Upon success, recommendations are retrieved and returned on the original request.

 

Step 4: Go live & performance monitoring

Goal: Serve recommendations to players and validate impact.

  • Target vs Control: Start with a 90/10 split (recommended) to measure uplift.
  • KPIs: Recommendation hit rate, games per player, and net revenue per player.

Receiving Recommendations

Use the Game Recommendation API via PlayTech Managed Services middleware.

  • Endpoint: GET
    https://{prodOrDevEnv}.{clientReference}.future-anthem-lz-pr.com/V3/api/Player2FutureAnthem
  • Authentication: Client certificates; Future Anthem IP whitelisted by Playtech, session validated with Playtech IMS webAPI.
  • Request example:
  {
"username": "0123456789",
"sessionToken": "s-tcwkg3sDvyl0H5Qgexxx_oXhlCa4DH3ziT1PxOnpeZ1Xuo4OQcb3w", "ipAddress": "1.1.1.1",
"clientType": "casino",
"clientPlatform": "web",
"casino": "stg.betanthem",
"playerCode": "12345678",
"recommendationType": "recommended_for_you" 
}     

 

  • Response Example: 
  {
   "data": [
     {
       "player": {
         "player_id": "12345678",
         "control_group": true
       },
       "categories": [
         "all",
         "slots"
       ],
       "recommendations": [
         {
           "category": "all",
           "recommendation": [
             {
               "gameId": "gpas_wdeadiw_pop",
               "gameName": "The Walking Dead™ Scratchcard"
             },
             {
               "gameId": "bfbl_liveslots",
               "gameName": "Buffalo Blitz™ Live"
             },
             {
               "gameId": "pop_58e99c1b_eye",
               "gameName": "Football LuckyTap™"
             },
             {
               "gameId": "pop_ac3b3fad_eye",
               "gameName": "Irish Luck"
             },  
{
               "gameId": "pop_aa375159_isb",
               "gameName": "Ocean Hunter"
...     
  • The API returns a minimum of 20 recommendations per category per player.

 

 

Architecture (high‑level)

Playtech Real‑Time Data (Kafka JSON) → Future Anthem (ingestion, models & scoring) → Front end (browser) generates request → P3S middleware (IMS validation + client certs) → Future Anthem APIs → CMS/Lobby/App (carousels & placements).

 

FAQs

Do we need client certificates?
Yes. Certificates are issued by and need to be requested from Playtech (lead time ~4 weeks).

Which endpoint and method are used?
GET https://{prodOrDevEnv}.{clientReference}.future-anthem-lz-pr.com/V3/api/Player2FutureAnthem.

What parameters are required?
username, sessionToken (fresh per request), ipAddress, clientType, clientPlatform, casino, playerCode, recommendationType; optional parameters are supported. languageCode defaults to EN.

How many recommendations are returned?
A minimum of 20 per recommendationType per player.

How are Control‑group players handled?
By default, players in the control group do not receive recommendations; this behaviour is configurable. Depending on configuration, response codes may include 404 for “player not found” or “player part of Control Group”.

How fresh are recommendations?
Models update daily to near real‑time based on new activity.

How do we measure impact?
Run a target vs control test and track KPIs such as hit rate, games per player, and net revenue per player. A typical starting split is 90/10 (target/control).

 

How do I get support or make a feature suggestion?

Visit our 'here to help' form and we will respond accordingly.