CRM Templates Placeholders

1. Introduction

This list provides a comprehensive guide to the dynamic placeholders available within the Gamanza Engage CRM. These placeholders allow operators to personalize communications (Email, SMS, On-Site Notifications, and Web-Push) by pulling real-time data from the player’s profile, gamification progress, and transactional history.

Usage Note: Placeholders should typically be wrapped in double curly braces (e.g., {{rank_up.CurrentRankExternalName}}) depending on the specific editor being used in the Gamanza back-office.

---

2. Gamification Events

2.1 Rank Up (Event)

Triggered when a player accumulates enough Experience Points (XP) to move to a new Rank Tier.

Placeholder	Description
rank_up.PlayerId	Unique identifier of the player.
rank_up.CurrentLevel	The numeric level reached within the new rank.
rank_up.CurrentRankExternalName	The public-facing name of the new Rank (e.g., "Gold Pro").
rank_up.CurrentRankExternalDescription	The marketing description defined for the new rank.
rank_up.XpBalance	The player’s total XP balance at the moment of ranking up.
rank_up.Timestamp	Date and time the rank-up occurred.
rank_up.RewardExternalDescription	Details of the reward granted for reaching this rank.

2.2 Level Up (Event)

Triggered when a player advances a level within their current rank.

Placeholder	Description
level_up.PlayerId	Unique identifier of the player.
level_up.CurrentLevel	The specific level number the player just attained.
level_up.RemainingPendingLevels	Number of levels remaining until the next Rank milestone.
level_up.CurrentRankExternalName	The name of the rank the player currently belongs to.
level_up.XpBalance	Total XP balance after the level-up.
level_up.RewardExternalDescription	Description of the bonus or perk awarded for the level-up.

2.3 Mission & Mission Bundles

Triggered upon completion of specific challenges or sets of challenges.

Placeholder	Description
mission_completed.MissionId	Internal ID of the completed mission.
mission_completed.RewardExternalName	The name of the prize won (e.g., "50 Free Spins").
mission_completed.RemainingPendingMissions	How many missions are left in the current active bundle.
mission_completed.MissionBundleExternalName	The name of the group/campaign this mission belongs to.
mission_bundle_completed.MissionBundleId	Internal ID of the completed bundle.
mission_bundle_completed.RewardExternalName	The "Grand Prize" name for finishing the entire bundle.

---

3. Loyalty Shop & Purchases

3.1 Product Purchase (Event)

Triggered when a player spends Tokens in the Gamanza Reward Shop.

Placeholder	Description
product_purchase.ProductExternalName	The name of the item purchased.
product_purchase.OrderStatus	Current state of the order (e.g., Pending, Fulfilled).
product_purchase.Price	The cost of the item in Tokens.
product_purchase.TokensBalance	The player’s remaining Token balance after purchase.
product_purchase.ProductType	Category of the item (Physical, Virtual, or Bonus).
product_purchase.RecipientAddress	Shipping address provided by the player (for physical goods).
product_purchase.ExternalURL	Link to a digital voucher or third-party tracking page.
product_purchase.ProductRemainingStock	Remaining inventory of the item (useful for "limited edition" alerts).

---

4. Financial Transactions

These placeholders are used for transactional receipts regarding deposits and withdrawals.

Placeholder Group	Key Fields	Description
money_deposit_successful	.amount, .currency, .paymentMethod, .realMoneyBalance	Sent after a successful top-up.
money_deposit_rejected	.amount, .transactionId, .paymentProvider	Sent if a deposit fails; used for recovery messaging.
money_withdraw_completed	.amount, .cardType, .date, .transactionStatus	Sent when a withdrawal is approved and processed.

Note: All money events support .bonusMoneyBalance to show the player their total playable funds.

---

5. Tournament Data

Used for automated lifecycle messaging for Gamanza Tournaments.

Placeholder	Description
tournament_starts_in_few_minutes...TournamentExternalName	Name of the upcoming tournament.
tournament_starts_in_few_minutes...Industry	The game vertical (e.g., Casino, Sports, Live Dealer).
tournament_winner_announcement.LeaderboardPosition	The final finishing position of the player (e.g., 1st, 15th).
tournament_winner_announcement.Rank	The rank tier achieved within that specific tournament.
tournament_winner_announcement.XpPointsBalance	Tournament-specific points earned during the session.

---

6. Global Player & Loyalty Information

These placeholders are "Global," meaning they can be used in almost any template regardless of the trigger event.

6.1 Player Profile (PlayersData)

Placeholder	Description
PlayersData.FirstName	The player’s first name as registered.
PlayersData.LastName	The player’s last name.
PlayersData.Email	The player’s registered email address.
PlayersData.CustomData.IsKycVerified	Boolean (True/False) indicating account verification status.
PlayersData.CustomData.RiskLevel	Internal segmentation score (e.g., Low, Medium, High).
PlayersData.CustomData.FavoriteGame	The game title most played by the player.

6.2 Global Loyalty & Balances

Placeholder	Description
VirtualCurrency.TokensBalance	Current spendable "Shop Tokens" balance.
Ranks.CurrentLevel	The player's current level in the loyalty program.
Ranks.XpBalance	Total lifetime Experience Points.
realMoneyBalance	The current withdrawable cash balance.
bonusMoneyBalance	The current non-withdrawable bonus balance.

---

7. Compliance: Opt-In / Opt-Out

Used for confirming changes to gamification preferences.

Placeholder	Description
gamification_optout.Timestamp	When the player deactivated gamification features.
gamification_optin.Timestamp	When the player reactivated gamification features.
gamification_optin.CurrentLevel	Confirms the level the player returns to upon re-joining.

---

Best Practices for Operators

1. Fallback Values: Always ensure your CRM tool has a "fallback" (e.g., "Player" if FirstName is empty).

2. Formatting: For money_deposit.amount, ensure the currency symbol is either hardcoded or pulled via the .currency placeholder.

3. Testing: Use the "Send Test" function in Gamanza Engage to ensure placeholders resolve correctly before activating a live campaign.