# User profile properties The list below represents the full catalog of user profile properties that Smartico supports. A few things to note: * Smartico supports not just Casino & Sport products but also Forex, Lottery, Retail/E-Commerce, Taxi, and more. If you are looking for properties specific to these products, please contact Smartico personnel. * Almost every Platform we are integrating with has properties that are not on the list provided below. In such cases, we create custom properties to meet the business's needs. * Most properties have no semantics on the Smartico side, which means they can be used for Segmentation and tag replacement (e.g., 'Hello {{state.first\_name}}'), but they don't include any logic on the Smartico side. Those that have semantics are highlighted and explained below. * There are many properties managed by Smartico's internal logic, e.g., core\_user\_last\_time\_online. You shouldn't worry about updating them from your Platform. ## "Core" properties managed fully by Smartico logic. Smartico's internal logic manages the following properties and shouldn't be updated outside. The "Core" here means that such properties are not related to Casino, Sport, or any other specific product | Name / Technical name | Comments | | -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Core: Behavioural segments (behaviour\_ids) | Hold list of [behavioural segments](https://help.smartico.ai/welcome/products/crm-automation/segmentation/behavioral-segments) user belongs to. | | Core: CSV & Common case segments (in\_manual\_upload\_segments) | Holds all [CSV](https://help.smartico.ai/welcome/products/crm-automation/segmentation/imported-segments) & '[Common cases](https://help.smartico.ai/welcome/products/crm-automation/segmentation/common-cases-segments)' segments user belongs to | | Core: JS markers (core\_public\_tags) | [JS markers](https://help.smartico.ai/welcome/products/general-concepts/user-markers-tags#core-js-markers-core_public_tags) of users | | Core: Mail Last Click Date (mail\_last\_clicked\_date) | The date/time when user clicked last time on any link in the mail sent by Smartico | | Core: Mail Last Open Date (mail\_last\_open\_date) | The date/time when user opened last time any mail sent by Smartico | | Core: Push Last Click Date (push\_last\_clicked\_date) | The date/time when user clicked last time on any link in the push notification sent by Smartico | | Core: Push Notification Last Open Date (push\_last\_open\_date) | The date/time when user have seen last time any push notification sent by Smartico | | Core: RFM segment (core\_rfm\_segment) | [RFM (Recency, Frequency, Monetary) ](https://help.smartico.ai/welcome/products/ai-models/rfm-analysis)segmentation is a marketing technique that categorizes customers based on how recently they made a deposit (Recency), how often they make deposit (Frequency), and how much money they spend (Monetary). It helps identify valuable customer segments for targeted marketing strategies and retention efforts. | | Core: RFM segment (previous) (core\_rfm\_segment\_prev) | Previous value of [RFM](https://help.smartico.ai/welcome/products/ai-models/rfm-analysis) segment, e.g. user migrated from "Loyal Customers" to "At Risk". This property will preserve his previous RFM segment type | | Core: RFM segment, frequency (core\_rfm\_frequency) | F, Frequency value in [RFM](https://help.smartico.ai/welcome/products/ai-models/rfm-analysis) logic | | Core: RFM segment, monetary (core\_rfm\_monetary) | M, Monetary value in [RFM](https://help.smartico.ai/welcome/products/ai-models/rfm-analysis) logic, | | Core: RFM segment, recency (core\_rfm\_recency) | F, Recency value in [RFM](https://help.smartico.ai/welcome/products/ai-models/rfm-analysis) logic | | Core: SMS Last Click Date (sms\_last\_clicked\_date) | The date/time when user clicked last time any SMS sent by Smartico | | Core: State based segments (core\_live\_segments) | Virtual propery that provides possibility to reference segment from another segment | | Core: Unread Inbox Message Count (core\_inbox\_unread\_count) | Count if [inbox message](https://help.smartico.ai/welcome/products/crm-automation/communication-channels/inbox) that user has as unread | | Core: all campaigns user have ever entered in control group (user\_all\_cg\_campaigns) | All campaigns user have ever entered in control group (IDs) | | Core: browser type (core\_user\_last\_session\_browser) | Type of browser user was logged in last time, E.g. Chrome, Safari etc | | Core: campaigns user ever entered (IDs) (user\_all\_campaigns) | All campaigns user have ever entered. You can use for segmentation, e.g. to exclude users who were part of campaign A & B | | Core: churn ratio (core\_ai\_churn\_ratio) | Daily churn probability score assigned to each player, with a value between 0 and 1, where 0 represents the lowest probability of churn and 1 represents the highest. | | Core: churn risk rank (core\_ai\_churn\_rank) | Categorizes a player into a specific risk group (e.g., Low, Medium, High, Critical) for a more straightforward interpretation of their [churn](https://help.smartico.ai/welcome/products/ai-models/churn-and-ltv-prediction) probability. | | Core: churn risk rank change (core\_ai\_churn\_rank\_delta) | Signifies a change in a player's [churn](https://help.smartico.ai/welcome/products/ai-models/churn-and-ltv-prediction) rank, which occurs when they migrate from one risk category to another, for instance, from "Low" to "High" risk. | | Core: favorite product (core\_fav\_product\_type) | If you are operating multiple products, e.g. Sport, Casino, Lottery, this property holds indication like "More Casino, Less Sport" as part of [Favorite product](https://help.smartico.ai/welcome/products/ai-models/favorite-product-game-game-type-and-game-provider) estimation | | Core: favorite product, Casino % (core\_fav\_product\_casino\_p) | % value of user preference in Casino comparing to other Products in [Favorite product logic](https://help.smartico.ai/welcome/products/ai-models/favorite-product-game-game-type-and-game-provider) | | Core: favorite product, Lottery % (core\_fav\_product\_lottery\_p) | % value of user preference in Lottery comparing to other Products in [Favorite product logic](https://help.smartico.ai/welcome/products/ai-models/favorite-product-game-game-type-and-game-provider) | | Core: favorite product, Sport % (core\_fav\_product\_sport\_p) | % value of user preference in Sport comparing to other Products in [Favorite product logic](https://help.smartico.ai/welcome/products/ai-models/favorite-product-game-game-type-and-game-provider) | | Core: first login country (core\_user\_first\_seen\_country) | The country code user first logged in | | Core: internal user id (user\_id) | ID of user in Smartico system | | Core: is SMS opted out (Smartico) (core\_is\_sms\_disabled) | Is SMS opted-out by the user while using Smartico opt-out flow or from Smartico Backoffice | | Core: is email opted out (Smartico) (core\_is\_email\_disabled) | Is email opted-out by the user while using Smartico opt-out flow or from Smartico Backoffice | | Core: is online (user\_is\_online) | Current status of user from online/offline perspective. | | Core: label id (label\_id) | ID of label in Smartico system, one and the same value for all users under same Label | | Core: language (core\_user\_language) | Language of the user in ISO 639-1 format (EN,BG,IT). Note that for PT-BR, the value should be BR. For other cases please refer to the [custom codes table](https://help.smartico.ai/welcome/front-end-integration#custom-language-codes). | | Core: last device used (core\_user\_last\_device\_type) | Last type of device user used, e.g. Mobile, Desktop | | Core: last link click country (core\_last\_visit\_country) | The country code of user when he click on any link sent in communication from Smartico (except popup and inbox) | | Core: last link click date (core\_last\_visit\_date) | The date/time when user clicked on any link in any type of communication sent to user (except popups and inbox) | | Core: last login country (core\_user\_last\_login\_country) | The country code of user when he last logged in | | Core: last login date (core\_user\_last\_login\_date) | The date/time when user last logged in. Don't confuse with another propery - core\_user\_last\_time\_online. The login date is reported once per session, while online can be reported more often, e.g. when user does refresh of page or navigating between pages | | Core: last login entry point (core\_last\_login\_entry) | Custom value that can be set from the front-end javascript, to indicate the type of page from where user logged-in - | | Core: last marketing SMS send date (last\_marketing\_sms\_sent\_date) | Date/time when last SMS was sent, only campaigns of category "Marketing" are counted | | Core: last marketing email send date (last\_marketing\_email\_sent\_date) | Date/time when last Email was sent, only campaigns of category "Marketing" are counted | | Core: last marketing popup send date (last\_marketing\_popup\_sent\_date) | Date/time when last Popup was sent, only campaigns of category "Marketing" are counted | | Core: last marketing push send date (last\_marketing\_push\_sent\_date) | Date/time when last Push notification was sent, only campaigns of category "Marketing" are counted | | Core: last time online (core\_user\_last\_time\_online) | Last time user were seen online | | Core: last website visited (core\_user\_last\_web\_host) | Last web site user visited, the value holds only domain and not the full URL of page | | Core: logins count ever (core\_user\_login\_count) | Incremental value that is increasing every time when user loggins | | Core: my smartico other brands (core\_sm\_my\_other\_brands) | Indicates other brands where user also exists. Note that logic of [matching users cross brands](https://help.smartico.ai/welcome/use-cases/crm-automation/cross-sell.-match-users-on-different-brands) depends on integration. Contact support team to define such logic if needed. | | Core: player class value (Churn model) (core\_ai\_player\_class\_id) | The class of player value evaluated by [Churn/LTV](https://help.smartico.ai/welcome/products/ai-models/churn-and-ltv-prediction) model as Low, Medium, VIP. | | Core: push enabled, user has at least one device (isPushEnabled) | Indicates if user has at least one device with [push notifications](https://help.smartico.ai/welcome/products/crm-automation/communication-channels/how-to-create-a-push-resource) enabled. | | Core: push status of last session (user\_last\_session\_push\_state) | [Push status](https://help.smartico.ai/welcome/products/crm-automation/communication-channels/how-to-create-a-push-resource) of last user session. Can be one of: ALLOWED - Player gave already permissions, ASK - Browser supports push notifications, permissions are not granted yet, BLOCKED - Permissions are blocked, BROWSER\_NOT\_SUPPORTED - Browser doesn't support. | | Core: smartico brand (core\_sm\_brand\_id) | ID of Brand in Smartico system. | | Core: smartico email status (internal) (user\_email\_status) | The [status of the user's email](https://help.smartico.ai/welcome/products/crm-automation/communication-channels/opt-out-and-communication-statuses) is used to check if emails can be sent or if the email is valid. Possible statuses are None, New, Verified, Bounced, Blocked, Spam Reported, and Broken. Status is managed by the Smartico system based on the mail delivery responses from gateways. | | Core: smartico phone status (internal) (user\_phone\_status) |

None/Broken - The phone didn't pass Google phone validation, New - The phone passed Google verification, Verified - The phone was verified by click or other method, Failed to Deliver - We got failed to deliver SMS from Gateway, Not Mobile - Google have recognised that the number is not mobile one.
Part of the phone & mail verification logic

| | Core: time zone offset (core\_user\_last\_session\_tzoffset) | Time zone offset of last user session in minutes, e.g "-180". The time-zone offset is the difference, in minutes, between UTC and local time. Note that this means that the offset is positive if the local timezone is behind UTC and negative if it is ahead. The value is used in different mechanics in Smartico, usually in context of sending communication in specific time according to user local time zone, or restricting user is doing specific actions in the Gamification, e.g. to play mini-game only once in a day | | Core: user external id (user\_ext\_id) | External ID of user, in case of multi-brand setup will be prefixed with ID of brand | | Core: user markers (core\_tags) | User-level markers can be set from the user profile or as part of the campaign. It can be used to build segments or inside the campaign to see if the user was marked. | | Core:: visitor\_id in acquisition label (core\_acq\_visitor\_id) | Works in combination with [Acquisiton](https://help.smartico.ai/welcome/technical-guides/front-end-integration/acquisition-mode) label, to highlight the ID of visitor that later converted to the user. | | Core: AFP parameter from TAP (core\_aff\_afp) | AFP parameter from TheAffiliatePlatform in case was configured for synchronisation | | Core: front-end version (core\_tracker\_version) | Used in iOS/Android native integrations to report version of mobile app that user used last | ## "Core" properties that can be provided from the Integrated Platform These properties can be supplied by an integrated Platform (e.g., Replica DB, Kafka/RabbitMQ, or an API). Please pay attention to the highlighted properties, as they have essential semantics on the Smartico side.
Name / Technical nameComments
falseCore: BTag (core_btag)BTag or "Banner tag", the unique ID used to track user from acquisition source
falseCore: External Account status (core_external_account_status)Account status in the external system
falseCore: External VIP level (core_external_vip_level)VIP level of the user in the external system
falseCore: External mail status (core_external_mail_status)Mail status in the external system
falseCore: External phone status (core_external_phone_status)Phone status in the external system
trueCore: Is email opted out on integrated PAM (core_is_email_disabled_by_platform)User is opted out from mail communication on the Product side.
Check for details here
trueCore: Is push opted out on integrated PAM (core_is_push_disabled_by_platform)User is opted out from push communication on the Product side
Check for details here
trueCore: Is sms opted out on integrated PAM (core_is_sms_disabled_by_platform)User is opted out from sms communication on the Product side
Check for details here
falseCore: KYC Completed Date (core_kyc_completed_at)Date when user completed KYC process
falseCore: KYC Started Date (core_kyc_started_at)Date when user started KYC process
falseCore: KYC status (core_kyc_status)Status of the user in KYC process
falseCore: Post Code (user_post_code)Postal code of user
falseCore: Referral code (core_ref_code)The referral code that can be used by the meaning of the integrated platform
falseCore: UTM Campaign (core_utm_campaign)UTM Campaign marker
falseCore: UTM Content (core_utm_content)The utm content parameter is used to differentiate similar content or links within the same campaign. It's most commonly used in A/B testing and ad variations.
falseCore: UTM Medium (core_utm_medium)UTM Medium marker
falseCore: UTM Source (core_utm_source)UTM Source marker
trueCore: account status (core_account_status)Status of account in the Smartico system. If the account is not ACTIVE, Smartico system will not execute any marketing activities for such an account. The default value for a newly created account is Active.
Check for details here
falseCore: account verified (core_is_acc_verified)Flag indicating that the user account is verified. The meaning and logic of verification is controlled on the operator side
falseCore: affiliate Id (numeric) (core_affiliate_id)Affiliate ID from affiliate system in case such ID is of type numeric
falseCore: affiliate Id (string) (core_affiliate_str)Affiliate ID from affiliate system in case such ID is of type string
falseCore: birthdate (user_birthdate)Birth date of user
falseCore: city (core_reg_city)City of the user
falseCore: custom property 1 (core_custom_prop1)Free text property that can be used for general purpose
falseCore: custom property 2 (core_custom_prop2)Free text property that can be used for general purpose
falseCore: custom property 3 (core_custom_prop3)Free text property that can be used for general purpose
falseCore: custom property 4 (core_custom_prop4)Free text property that can be used for general purpose
falseCore: custom property 5 (core_custom_prop5)Free text property that can be used for general purpose
falseCore: custom property 6 (core_custom_prop6)Free text property that can be used for general purpose
falseCore: custom property 7 (core_custom_prop7)Free text property that can be used for general purpose
falseCore: custom property date/time 1 (core_custom_prop_dt1)Date/time property that can be used for general purpose
falseCore: custom property, numeric 1 (core_custom_prop_num1)Numberic property that can be used for general purpose
falseCore: date when account is verified in PAM (core_acc_pam_verified_dt)
falseCore: date when email verified in PAM (core_pam_email_verified_dt)
falseCore: date when phone verified in PAM (core_pam_phone_verified_dt)
falseCore: email (user_email)In case Smartico Data Guard is setup, the mail is encrypted and cannot be accessed from Smartico CRM. In case mail is submitted via API, it should be encrypted on Integrated system
falseCore: email confirmed by PAM (core_email_confirmed)Flag indicating that user has email confirmed
falseCore: exclude from marketing (core_exclude_from_marketing)Flag indicating that user should be excluded from all marketing communications. Doesn't have operational impact in Smartico system and should be used by the marketer in the segmentation
falseCore: external markers (core_external_markers)User-level markers can be set from the external system via API. https://help.smartico.ai/welcome/products/general-concepts/user-markers-tags
falseCore: external markers 2 (core_external_markers_2)User-level markers can be set from the external system via API. https://help.smartico.ai/welcome/products/general-concepts/user-markers-tags
falseCore: external segment (core_external_segment)Can be used to integrate with external segmentation system
falseCore: first name (user_first_name)
falseCore: gender (core_user_gender)
trueCore: is IVR opted out on integrated PAM (core_is_ivr_disabled)Check for details here
trueCore: is Push opted out on integrated PAM (core_is_push_disabled)Check for details here
trueCore: is WhatsApp Opted Out (core_is_whatsapp_disabled)Check for details here
trueCore: is test account (core_is_test_account)If account is marked as test or real. Test accounts are excluded by default from most of BI reports. Note: depending on product integration, this flag can be controlled by external system, changing it in Smartico CRM can be later overridden with next synchronization with external system.
falseCore: last name (user_last_name)
falseCore: lifecycle state (core_lifecycle)State of the lifecycle for user
falseCore: lifecycle state update date (core_lifecycle_update_dt)The date/time when state of the lifecycle for user is changed
falseCore: mail domain (core_mail_domain)Domain of the user mail address
falseCore: main device type (core_main_device_type)
falseCore: organization (core_organization)Organization to which user belongs
falseCore: parent affiliate Id (numeric) (core_affiliate_parent_id)Parent Affiliate ID from affiliate system/TAP
trueCore: phone (user_phone)Full encrypted phone number of user, used to deliver SMS, Viber, WhatsApp and IVR engagements
falseCore: phone HLR status (user_phone_hlr_status)None - The phone didn't pass Google phone validation, HLR Requested - When HLR is used, in the middle of verification process, HLR Invalid - When HLR is used, HLR failed the number, we will not send SMS, HLR Valid - When HLR is used, HLR passed, we will send SMS, HLR Failed - When HLR is used, call to HLR has failed
false
falseCore: phone confirmed by PAM (core_phone_confirmed)Flag indicating that user phone is confirmed
falseCore: phone country (user_phone_country)Country code based on user phone
falseCore: preferred product by PAM (core_pref_product)Type of product user prefers. E.g. sport, casino etc, reported from the integrated system
falseCore: registration country (user_country)2 symbols, user registration country, e.g. UK
trueCore: registration date (core_registration_date)The date/time when user is registered. When the property is populate, the system will trigger event 'Core: profile ready'. Note that this property cannot be changed once it is set.
It is important to have ALL users in the system with registration date populated
falseCore: registration platform (core_registration_platform)Registration platform from where user was registered
falseCore: risk rank (core_risk_rank)Risk rank that can be used by the meaning specific for the platform
falseCore: state (core_reg_state)State of the user
falseCore: time of day preference (core_time_of_day_pref)
falseCore: user type (core_user_type)Type of user in the integrated platform
falseCore: username (core_username)Username or nickname
trueCore: wallet currency (core_wallet_currency)Currency of the user wallet. Note that once set this value cannot be changed for user.
All the "money" related properties in the system should be treated according to this currency
## Accounting properties | Name / Technical name | Comments | | ----------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Accounting: Bonus Abuser (acc\_bonus\_abuser) | Flag indicating if the user is bonus abuser or blocked from getting bonuses | | Accounting: Bonus to deposit ratio (acc\_bonus\_to\_dep\_ratio) | | | Accounting: Document Status (acc\_documents\_status) | Current status of documents in the KYC process. | | Accounting: FTD Amount (acc\_ftd\_amount) | Amount of the first deposit | | Accounting: FTD Date (acc\_ftd\_date) | The date of the first deposit. The value is automatically set by Smartico based on the first transaction. If the Integrated product is able to deliver its own FTD date, it can be passed and will override the value defined by Smartico. | | Accounting: FWD Amount (acc\_fwd\_amount) | Amount of the first withdrawal | | Accounting: First approved withdrawal date (acc\_fwd\_date) | The date of first approved withdrawal | | Accounting: Last Deposit Amount (acc\_last\_deposit\_amount) | Deposit amount in the player currency | | Accounting: Last Deposit Date (acc\_last\_deposit\_date) | The date of last deposit | | Accounting: Last approved bonus date (acc\_last\_bonus\_date) | Date/time when the bonus was approved | | Accounting: Last approved withdrawal date (acc\_last\_withdrawal\_date) | The date of last withdrawal | | Accounting: Last complete bonus date (acc\_last\_bonus\_complete\_date) | Date/time when the bonus was approved | | Accounting: Total Withdrawal Amount (acc\_total\_withdrawal\_amount) | Total withdrawal amount in the user currency | | Accounting: Total Withdrawal Cancelled amount (acc\_total\_withdrawal\_cancelled\_amount) | Total Withdrawal Cancelled amount | | Accounting: Total Withdrawal Cancelled count (acc\_total\_withdrawal\_cancelled\_cnt) | Total count of cancelled withdrawals | | Accounting: Total Withdrawal Count (acc\_total\_withdrawal\_count) | Number of withdrawals that user did | | Accounting: Total Withdrawal Pending Amount (acc\_total\_withdrawal\_pending\_amount) | | | Accounting: Total Withdrawal Pending count (acc\_total\_withdrawal\_pending\_cnt) | Total count of pending withdrawals | | Accounting: Total approved bonuses amount (acc\_total\_approved\_bonuse\_amount) | An amount of approved bonuses that the user got ever. The value is automatically accumulated by Smartico based on the acc\_bonus\_approved transactions - every time a new acc\_bonus\_approved comes, Smartico will increase the amount. If the Integrated product is able to deliver its own acc\_total\_approved\_bonuses\_amount, it can be passed and will override the value defined by Smartico. | | Accounting: Total approved bonuses count (acc\_total\_approved\_bonuses\_count) | A number of approved bonuses that the user got ever. The value is automatically accumulated by Smartico based on the acc\_bonus\_approved transactions - every time a new acc\_bonus\_approved comes, Smartico will increase the count by 1. If the Integrated product is able to deliver its own acc\_total\_approved\_bonuses\_count, it can be passed and will override the value defined by Smartico. | | Accounting: Total lost amount (acc\_total\_lost\_amount) | Total lost amount in the user currency | | Accounting: Total turnover (wagering / bets) (acc\_total\_turnover) | Total Turnover in the user currency | | Accounting: Total win amount (acc\_total\_win\_amount) | Total win amount in the user currency | | Accounting: Withdrawal Amount (acc\_last\_withdrawal\_amount) | Amount of with last withdrawal in the user currency | | Accounting: bonus balance (acc\_bonus\_balance) | Bonus money balance in the user currency. Recommended to be updated after every monetary operation that is changing bonus balance with the state of balance after transaction | | Accounting: bonus score (acc\_bonus\_score) | The bonus score calculated by PAM or by operator managed analytical function | | Accounting: deposit last fail date (acc\_last\_deposit\_fail\_date) | The date of last failed deposit | | Accounting: last active currency (acc\_last\_active\_currency) | In case of multi-wallet accounts, should indicate currency of the current active wallet | | Accounting: preferred deposit method (acc\_pref\_deposit\_method) | Preferred deposit method of user. Calculated either by Integrated product or by Smartico analytical models | | Accounting: preferred deposit week day (acc\_pref\_deposit\_week\_day) | Preferred day of week for deposit. Calculated either by Integrated product or by Smartico analytical models | | Accounting: real balance (acc\_real\_balance) | Real money balance in the user currency. Recommended to be updated after every monetary operation that is changing real balance with the state of balance after the transaction | | Accounting: real balance, landbase (acc\_land\_balance\_real) | | | Accounting: total balance (acc\_total\_balance) | Real + bonuse money balance in the user currency. Recommended to be updated after every monetary operation that is changing real/bonus balances with the state of balance after the transaction | | Accounting: total balance, landbase (acc\_land\_balance\_total) | | | Sweepstake: gold coins balance (acc\_gc\_balance) | Gold coins balance | | Sweepstake: gold coins balance (real) (acc\_gc\_real\_balance) | Gold coins real balance | | Sweepstake: gold coins bonus balance (acc\_gc\_bonus\_balance) | Gold coins bonus balance | | Sweepstake: regular coins balance (acc\_sc\_balance) | Regular coins balance | | Sweepstake: regular coins bonus balance (acc\_sc\_bonus\_balance) | Regular coins bonus balance | | Sweepstake: regular coins real balance (acc\_sc\_real\_balance) | Regular coins real balance | ### **General Casino properties** | Name / Technical name | Comments | | -------------------------------------------------------------- | ---------------------------------------------- | | Casino: Last Bet Date (casino\_last\_bet\_dt) | Date/time of the last bet | | Casino: Last Real Money Bet Date (casino\_last\_bet\_real\_dt) | Date/time of the last bet done with real money | ### **General Sport properties** | Technical name | comments | | ------------------------------------------------------------ | ----------------------------------------------- | | Sport: First Bet Date (sport\_first\_bet\_date) | Date of the first sport bet | | Sport: Last Bet Date (sport\_last\_bet\_date) | Date of the last sport bet | | Sport: Last Real Money Bet Date (sport\_last\_bet\_real\_dt) | Date of the last sport bet done with real money | ## Aggregation Properties for Casino & Sports Smartico supports a wide range of aggregation properties for Casino and Sports products. For example **"**Sport: Last 90 days GGR", "Accounting: Last 30 days average deposit amount" etc. We **strongly recommend** that these properties be updated based on source data — that is, provided directly by the integrated Platform. This approach ensures the data remains accurate and fully aligned with the actual values maintained on the Platform side. Such updates can be performed via API using the `update_profile` event. The data can be sourced from the Platform’s internal systems, such as the Replicate database, or via streaming platforms like Kafka or RabbitMQ. The update schedule is defined by the Platform, but in practice, a **daily update cycle** is typically sufficient for operational needs. Example of event for updating such properties ```jsonp { "eid": "9352cc76-3d09-44ec-a5df-7fcc0f0356a8", "event_date": 1751100537610, "ext_brand_id": 55, "user_ext_id": "test98635568", "event_type": "update_profile", "payload": { "sport_yesterday_bet_amount": 45.12, "sport_yesterday_bets_count": 3 ... } } ``` ### Supported aggregation properties Note: all "money" related properties are of type "Multi-currency", which means that the value kept inside should be treated in combination with "core\_wallet\_currency". E.g., a value of 10 in Total GGR for one user could mean USD, and for another, CAD. Smartico is providing efficient tools for segmenting and targeting users based on different currencies. #### GGR
NameTechnical name
Accounting: Total GGRacc_total_ggr
Accounting: Last 90 days GGRacc_last_90_days_ggr
Accounting: Last 60 days GGRacc_last_60_days_ggr
Accounting: Last 30 days GGRacc_last_30_days_ggr
Accounting: Last 7 days GGRacc_last_7_days_ggr
Accounting: Last month GGRacc_last_month_ggr
Accounting: Last week GGRacc_last_week_ggr
Accounting: Yesterday GGRacc_yesterday_ggr
Casino: Total / Lifetime GGRcasino_total_ggr
Casino: Last 90 days GGRcasino_last_90_days_ggr
Casino: Last 60 days GGRcasino_last_60_days_ggr
Casino: Last 30 days GGRcasino_last_30_days_ggr
Casino: Last 7 days GGRcasino_last_7_days_ggr
Casino: Last month GGRcasino_last_month_ggr
Casino: Last week GGRcasino_last_week_ggr
Casino: Yesterday GGRcasino_yesterday_ggr
Sport: Total GGRsport_total_ggr
Sport: Last 90 days GGRsport_last_90_days_ggr
Sport: Last 60 days GGRsport_last_60_days_ggr
Sport: Last 30 days GGRsport_last_30_days_ggr
Sport: Last 7 days GGRsport_last_7_days_ggr
Sport: Last month GGRsport_last_month_ggr
Sport: Last week GGRsport_last_week_ggr
Sport: Yesterday GGRsport_yesterday_ggr
#### **NGR** | Name | Technical name | | -------------------------------- | --------------------------- | | **Accounting: Total NGR** | **acc\_total\_ngr** | | Accounting: Last 90 days NGR | acc\_last\_90\_days\_ngr | | Accounting: Last 60 days NGR | acc\_last\_60\_days\_ngr | | Accounting: Last 30 days NGR | acc\_last\_30\_days\_ngr | | Accounting: Last 7 days NGR | acc\_last\_7\_days\_ngr | | Accounting: Last month NGR | acc\_last\_month\_ngr | | Accounting: Last week NGR | acc\_last\_week\_ngr | | Accounting: Yesterday NGR | acc\_yesterday\_ngr | | **Casino: Total / Lifetime NGR** | **casino\_total\_ngr** | | Casino: Yesterday NGR | casino\_yesterday\_ngr | | Casino: Last week NGR | casino\_last\_week\_ngr | | Casino: Last month NGR | casino\_last\_month\_ngr | | Casino: Last 7 days NGR | casino\_last\_7\_days\_ngr | | Casino: Last 30 days NGR | casino\_last\_30\_days\_ngr | | Casino: Last 60 days NGR | casino\_last\_60\_days\_ngr | | Casino: Last 90 days NGR | casino\_last\_90\_days\_ngr | | **Sport: Total NGR** | **sport\_total\_ngr** | | Sport: Last 90 days NGR | sport\_last\_90\_days\_ngr | | Sport: Last 60 days NGR | sport\_last\_60\_days\_ngr | | Sport: Last 30 days NGR | sport\_last\_30\_days\_ngr | | Sport: Last 7 days NGR | sport\_last\_7\_days\_ngr | | Sport: Last month NGR | sport\_last\_month\_ngr | | Sport: Last week NGR | sport\_last\_week\_ngr | | Sport: Yesterday NGR | sport\_yesterday\_ngr | #### Deposits & Withdrawals | Name | Technical name | | ----------------------------------------- | ------------------------------ | | Accounting: Net Deposit Amount (lifetime) | acc\_net\_deposit\_amount | | Accounting: Withdrawal Amount (lifetime) | acc\_total\_withdrawal\_amount | | Accounting: Average Withdrawal Amount () | acc\_avg\_withdrawal\_amount | | Name | Technical name | | ----------------------------------------------- | ----------------------------------------- | | Accounting: Median Deposit Amount | acc\_median\_deposit\_amount | | Accounting: Lifetime average deposit amount | acc\_avg\_deposit\_amount | | Accounting: Last 90 days average deposit amount | acc\_last\_90\_days\_avg\_deposit\_amount | | Accounting: Last 60 days average deposit amount | acc\_last\_60\_days\_avg\_deposit\_amount | | Accounting: Last 30 days average deposit amount | acc\_last\_30\_days\_avg\_deposit\_amount | | Accounting: Last 7 days average deposit amount | acc\_last\_7\_days\_avg\_deposit\_amount | | Accounting: Last month average deposit amount | acc\_last\_month\_avg\_deposit\_amount | | Accounting: Last week average deposit amount | acc\_last\_week\_avg\_deposit\_amount | | Accounting: Yesterday average deposit amount | acc\_yesterday\_avg\_deposit\_amount | | Name | Technical name | | --------------------------------------- | ------------------------------------ | | Accounting: Total Deposit Amount | acc\_total\_deposit\_amount | | Accounting: Last 90 days deposit amount | acc\_last\_90\_days\_deposit\_amount | | Accounting: Last 60 days deposit amount | acc\_last\_60\_days\_deposit\_amount | | Accounting: Last 30 days deposit amount | acc\_last\_30\_days\_deposit\_amount | | Accounting: Last 7 days deposit amount | acc\_last\_7\_days\_deposit\_amount | | Accounting: Last month deposit amount | acc\_last\_month\_deposit\_amount | | Accounting: Last week deposit amount | acc\_last\_week\_deposit\_amount | | Accounting: Yesterday deposit amount | acc\_yesterday\_deposit\_amount | #### Total bets amounts and counts (sport + casino + any other products) | Name | Technical name | | -------------------------------- | ----------------------------------- | | acc\_last\_90\_days\_bets\_count | Accounting: Last 90 days bets count | | acc\_last\_60\_days\_bets\_count | Accounting: Last 60 days bets count | | acc\_last\_30\_days\_bets\_count | Accounting: Last 30 days bets count | | acc\_last\_7\_days\_bets\_count | Accounting: Last 7 days bets count | | acc\_last\_month\_bets\_count | Accounting: Last month bets count | | acc\_last\_week\_bets\_count | Accounting: Last week bets count | | acc\_yesterday\_bets\_count | Accounting: Yesterday bets count | | acc\_last\_90\_days\_bet\_amount | Accounting: Last 90 days bet amount | | acc\_last\_60\_days\_bet\_amount | Accounting: Last 60 days bet amount | | acc\_last\_30\_days\_bet\_amount | Accounting: Last 30 days bet amount | | acc\_last\_7\_days\_bet\_amount | Accounting: Last 7 days bet amount | | acc\_last\_month\_bet\_amount | Accounting: Last month bet amount | | acc\_last\_week\_bet\_amount | Accounting: Last week bet amount | | acc\_yesterday\_bet\_amount | Accounting: Yesterday bet amount | #### Casino bets, wins, counts | Name | Technical name | | ------------------------------------- | ----------------------------------- | | Casino: Total / Lifetime bet amount | casino\_total\_turnover | | Casino: Total bets count | casino\_total\_bets\_count | | Casino: Total free bets count | casino\_total\_free\_bets\_count | | Casino: Total / Lifetime win amount | casino\_total\_win\_amount | | Casino: Last 90 days bet amount | casino\_last\_90\_days\_bet\_amount | | Casino: Last 90 days bets count | casino\_last\_90\_days\_bets\_count | | Casino: Last 90 days win amount | casino\_last\_90\_days\_win\_amount | | Casino: Last 60 days bet amount | casino\_last\_60\_days\_bet\_amount | | Casino: Last 60 days bets count | casino\_last\_60\_days\_bets\_count | | Casino: Last 60 days win amount | casino\_last\_60\_days\_win\_amount | | Casino: Last 30 days bet amount | casino\_last\_30\_days\_bet\_amount | | Casino: Last 30 days bets count | casino\_last\_30\_days\_bets\_count | | Casino: Last 30 days win amount | casino\_last\_30\_days\_win\_amount | | Casino: Last 7 days bet amount | casino\_last\_7\_days\_bet\_amount | | Casino: Last 7 days bets count | casino\_last\_7\_days\_bets\_count | | Casino: Last 7 days win amount | casino\_last\_7\_days\_win\_amount | | Casino: Last month bet amount | casino\_last\_month\_bet\_amount | | Casino: Last month bets count | casino\_last\_month\_bets\_count | | Casino: Last month win amount | casino\_last\_month\_win\_amount | | Casino: Last week bet amount | casino\_last\_week\_bet\_amount | | Casino: Last week bets count | casino\_last\_week\_bets\_count | | Casino: Last week win amount | casino\_last\_week\_win\_amount | | Casino: Yesterday bet amount | casino\_yesterday\_bet\_amount | | Casino: Yesterday bets count | casino\_yesterday\_bets\_count | | Casino: Yesterday win amount | casino\_yesterday\_win\_amount | | Casino: Average real money bet amount | casino\_avg\_bet\_amount\_real | **Sport bets, wins, count** | Name | Technical name | | --------------------------------------------- | ---------------------------------- | | Sport: Total / Lifetime bets count | sport\_total\_open\_bets | | Sport: Total / Lifetime bet amount (wagering) | sport\_total\_turnover | | Sport: Total win amount | sport\_total\_win\_amount | | Sport: Last 90 days bet amount | sport\_last\_90\_days\_bet\_amount | | Sport: Last 90 days bets count | sport\_last\_90\_days\_bets\_count | | Sport: Last 90 days win amount | sport\_last\_90\_days\_win\_amount | | Sport: Last 60 days bet amount | sport\_last\_60\_days\_bet\_amount | | Sport: Last 60 days bets count | sport\_last\_60\_days\_bets\_count | | Sport: Last 60 days win amount | sport\_last\_60\_days\_win\_amount | | Sport: Last 30 days bet amount | sport\_last\_30\_days\_bet\_amount | | Sport: Last 30 days bets count | sport\_last\_30\_days\_bets\_count | | Sport: Last 30 days win amount | sport\_last\_30\_days\_win\_amount | | Sport: Last 7 days bet amount | sport\_last\_7\_days\_bet\_amount | | Sport: Last 7 days bets count | sport\_last\_7\_days\_bets\_count | | Sport: Last 7 days win amount | sport\_last\_7\_days\_win\_amount | | Sport: Last month bet amount | sport\_last\_month\_bet\_amount | | Sport: Last month bets count | sport\_last\_month\_bets\_count | | Sport: Last month win amount | sport\_last\_month\_win\_amount | | Sport: Last week bet amount | sport\_last\_week\_bet\_amount | | Sport: Last week bets count | sport\_last\_week\_bets\_count | | Sport: Last week win amount | sport\_last\_week\_win\_amount | | Sport: Yesterday bet amount | sport\_yesterday\_bet\_amount | | Sport: Yesterday bets count | sport\_yesterday\_bets\_count | | Sport: Yesterday win amount | sport\_yesterday\_win\_amount | ### Realtime aggregations Smartico supports a few properties that are handled in real time. Withdrawals related: * **acc\_total\_withdrawal\_count** - incremented as count on **acc\_withdrawal\_approved** event * **acc\_total\_withdrawal\_amount** - incremented on the amount value on **acc\_withdrawal\_approved** event * **acc\_total\_withdrawal\_cancelled\_cnt** - incremented as count on **acc\_withdrawal\_cancelled** event * **acc\_total\_withdrawal\_cancelled\_amount**- incremented on the amount value on **acc\_withdrawal\_cancelled** event Deposits related: * **acc\_total\_deposit\_count** - incremented as count on **acc\_deposit\_approved** event * **acc\_total\_deposit\_amount** - incremented on the amount value on **acc\_deposit\_approved** event Bonuses related: * **acc\_total\_approved\_bonuses\_count** - incremented as count on **acc\_bonus\_approved** event * **acc\_total\_approved\_bonuse\_amount**- incremented on the amount value on **acc\_bonus\_approved** event {% hint style="warning" %} Important to note that these properties are sensitive to the quality of the integration. If the events are not reported or are reported as duplicates, the values won't be reliable. We do recommend disabling real-time calculations in the label settings and updating these properties from the integrated platform. You can find the respective label setting called "Calculate total values on Smartico side" {% endhint %}
### FAQ for Aggregated properties **Q: If platform is providing aggregated properties for Casino related activities through Kafka/Database or API, should it still provide per-bet transactions?** A: Short answer - yes, it should be provided. The aggregations and per-bet transactions are serving different needs. * Aggregations are used in the segmentation, for example to define segment "Users with casino\_last\_7\_days\_win\_amount > 200 EUR". * Per-bet transactions - providing possibility to build realtime activities (campaigns, automation rules, missions, tournaments etc). For example - "Give a mini-game attempt for every 100 bets" or mission "Make 100 EUR bets during 3 days on Gonzo Quest". Per-bet transactions are also used in the analytical models like Best time for communication, Favorite games etc. **Q: How we should treat "day" when providing data for properties like casino\_last\_7\_days\_bet\_amount. Should we do calculation in the midnight by UTC-0 and include exactly last 7 days transactions?** A: Its fully up to your preferences: * How often you do calculations - you can build them once in a day or few times or any other logic you decide. We will consume data close to realtime from Kafka or DB whenever the changed data is provided, or whenever you push such changes over Smartico Rest API * At what time and timezone to calculate them - again, you can do calculations whenever its preferable and makes more sense for your operation * You can put your own definition in any of the properties, for example you can treat casino\_last\_7\_days\_bet\_amount as "sliding window 7 days" and calculate them every how, and count transactions of "last 7x24 hours back" from the moment of calculation. Or you can do it once in a day and take 7 full days back according to the your operational timezone or maybe even timezone of player. Smartico is agnostic to the meaning you put in such properties, time and frequency of calculations.