User profile properties
The list below represents full catalog of user profile properties that is supported Smartico as on June 2025.
Few things to note:
Smartico support not just Casino & Sport products, but also Forex, Lottery, Retail/E-Commerce, Taxi etc. If you are looking for properties specific for these products, please contact Smartico personnel
Almost every Platform we are integrating with has properties our of the list provided below. In such cases we are creating custom properties according to the needs of business.
Most of the properties don't have any semantic on Smartico side, means that they can be used for Segmentation and tag replacement (e,g, 'Hello {{state.first_name}}'), but they don't have any logic on Smartico side. Those that have semantic are highlighted and explained below
There are many properties managed by Smartico internal logic, e.g. core_user_last_time_online. You shoudn't worry about updating them from your Platform.
"Core" properties managed fully by Smartico logic
Following properties are managed by Smartico internal logic and shouldn't be updated outside.
The "Core" here means that such properties are not related to Casino, Sport or any other specific product
Core: Behavioural segments (behaviour_ids)
Hold list of behavioural segments user belongs to - https://help.smartico.ai/welcome/products/crm-automation/segmentation/behavioral-segments
Core: CSV & Common case segments (in_manual_upload_segments)
Holds all CSV & 'Common cases' segments user belongs to - https://help.smartico.ai/welcome/products/crm-automation/segmentation/imported-segments and https://help.smartico.ai/welcome/products/crm-automation/segmentation/common-cases-segments
Core: JS markers (core_public_tags)
JS markers of users - https://help.smartico.ai/welcome/products/general-concepts/user-markers-tags
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) 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. https://help.smartico.ai/welcome/products/ai-models/rfm-analysis
Core: RFM segment (previous) (core_rfm_segment_prev)
Previous value of RFM 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 logic, https://help.smartico.ai/welcome/products/ai-models/rfm-analysis
Core: RFM segment, monetary (core_rfm_monetary)
M, Monetary value in RFM logic, https://help.smartico.ai/welcome/products/ai-models/rfm-analysis
Core: RFM segment, recency (core_rfm_recency)
F, Recency value in RFM logic, https://help.smartico.ai/welcome/products/ai-models/rfm-analysis
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)
Coun if inbox message that user has as unread https://help.smartico.ai/welcome/products/crm-automation/communication-channels/inbox
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. https://help.smartico.ai/welcome/products/ai-models/churn-and-ltv-prediction
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 probability. https://help.smartico.ai/welcome/products/ai-models/churn-and-ltv-prediction
Core: churn risk rank change (core_ai_churn_rank_delta)
Signifies a change in a player's churn rank, which occurs when they migrate from one risk category to another, for instance, from "Low" to "High" risk. https://help.smartico.ai/welcome/products/ai-models/churn-and-ltv-prediction
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". https://help.smartico.ai/welcome/products/ai-models/favorite-product
Core: favorite product, Casino % (core_fav_product_casino_p)
% value of user preference in Casino comparing to other Products. https://help.smartico.ai/welcome/products/ai-models/favorite-product
Core: favorite product, Lottery % (core_fav_product_lottery_p)
% value of user preference in Lottery comparing to other Products. https://help.smartico.ai/welcome/products/ai-models/favorite-product
Core: favorite product, Sport % (core_fav_product_sport_p)
% value of user preference in Sport comparing to other Products. https://help.smartico.ai/welcome/products/ai-models/favorite-product
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 casese, please consult with Smartico support
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 - https://help.smartico.ai/welcome/technical-guides/front-end-integration/extended-integration#last-login-entry-point
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 depends on integration. Contact support team to define such logic if needed. https://help.smartico.ai/welcome/use-cases/crm-automation/cross-sell.-match-users-on-different-brands
Core: player class value (Churn model) (core_ai_player_class_id)
The class of player value evaluated by Churn/LTV model as Low, Medium, VIP. https://help.smartico.ai/welcome/products/ai-models/churn-and-ltv-prediction
Core: push enabled, user has at least one device (isPushEnabled)
Indicates if user has at least one device with push notifications enabled. https://help.smartico.ai/welcome/products/crm-automation/communication-channels/how-to-create-a-push-resource
Core: push status of last session (user_last_session_push_state)
Push status 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. https://help.smartico.ai/welcome/products/crm-automation/communication-channels/how-to-create-a-push-resource
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 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. https://help.smartico.ai/welcome/products/crm-automation/communication-channels/opt-out-and-communication-statuses
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. https://help.smartico.ai/welcome/products/crm-automation/communication-channels/opt-out-and-communication-statuses
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. https://help.smartico.ai/welcome/products/general-concepts/user-markers-tags
Core:: visitor_id in acquisition label (core_acq_visitor_id)
Works in combination with Acquisiton label, to highlight the ID of visitor that later converted to the user. https://help.smartico.ai/welcome/technical-guides/front-end-integration/acquisition-mode
Core: AFP parameter from TAP (core_aff_afp)
AFP parameter from TheAffiliatePlatform in case was configured for synchronisation
"Core" properties that can be provided from Integrated Platform
These properties can be provided from integrated Platform (from Replica DB, Kafka/RabbitMQ or API).
Pay attention to the highlighted properties, as they have important semantic on Smartico side.
Core: BTag (core_btag)
BTag or "Banner tag", the unique ID used to track user from acquisition source
Core: External Account status (core_external_account_status)
Account status in the external system
Core: External VIP level (core_external_vip_level)
VIP level of the user in the external system
Core: External mail status (core_external_mail_status)
Mail status in the external system
Core: External phone status (core_external_phone_status)
Phone status in the external system
Core: 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
Core: 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
Core: 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
Core: KYC Completed Date (core_kyc_completed_at)
Date when user completed KYC process
Core: KYC Started Date (core_kyc_started_at)
Date when user started KYC process
Core: KYC status (core_kyc_status)
Status of the user in KYC process
Core: Post Code (user_post_code)
Postal code of user
Core: Referral code (core_ref_code)
The referral code that can be used by the meaning of the integrated platform
Core: UTM Campaign (core_utm_campaign)
UTM Campaign marker
Core: 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.
Core: UTM Medium (core_utm_medium)
UTM Medium marker
Core: UTM Source (core_utm_source)
UTM Source marker
Core: 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
Core: 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
Core: affiliate Id (numeric) (core_affiliate_id)
Affiliate ID from affiliate system in case such ID is of type numeric
Core: affiliate Id (string) (core_affiliate_str)
Affiliate ID from affiliate system in case such ID is of type string
Core: birthdate (user_birthdate)
Birth date of user
Core: city (core_reg_city)
City of the user
Core: custom property 1 (core_custom_prop1)
Free text property that can be used for general purpose
Core: custom property 2 (core_custom_prop2)
Free text property that can be used for general purpose
Core: custom property 3 (core_custom_prop3)
Free text property that can be used for general purpose
Core: custom property 4 (core_custom_prop4)
Free text property that can be used for general purpose
Core: custom property 5 (core_custom_prop5)
Free text property that can be used for general purpose
Core: custom property 6 (core_custom_prop6)
Free text property that can be used for general purpose
Core: custom property 7 (core_custom_prop7)
Free text property that can be used for general purpose
Core: custom property date/time 1 (core_custom_prop_dt1)
Date/time property that can be used for general purpose
Core: custom property, numeric 1 (core_custom_prop_num1)
Numberic property that can be used for general purpose
Core: date when account is verified in PAM (core_acc_pam_verified_dt)
Core: date when email verified in PAM (core_pam_email_verified_dt)
Core: date when phone verified in PAM (core_pam_phone_verified_dt)
Core: 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
Core: email confirmed by PAM (core_email_confirmed)
Flag indicating that user has email confirmed
Core: 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
Core: 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
Core: 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
Core: external segment (core_external_segment)
Can be used to integrate with external segmentation system
Core: first name (user_first_name)
Core: gender (core_user_gender)
Core: is IVR opted out on integrated PAM (core_is_ivr_disabled)
Core: is Push opted out on integrated PAM (core_is_push_disabled)
Core: is WhatsApp Opted Out (core_is_whatsapp_disabled)
Core: 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.
Core: last name (user_last_name)
Core: lifecycle state (core_lifecycle)
State of the lifecycle for user
Core: lifecycle state update date (core_lifecycle_update_dt)
The date/time when state of the lifecycle for user is changed
Core: mail domain (core_mail_domain)
Domain of the user mail address
Core: main device type (core_main_device_type)
Core: organization (core_organization)
Organization to which user belongs
Core: parent affiliate Id (numeric) (core_affiliate_parent_id)
Parent Affiliate ID from affiliate system/TAP
Core: phone (user_phone)
Core: 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
Core: phone confirmed by PAM (core_phone_confirmed)
Flag indicating that user phone is confirmed
Core: phone country (user_phone_country)
Country code based on user phone
Core: preferred product by PAM (core_pref_product)
Type of product user prefers. E.g. sport, casino etc, reported from the integrated system
Core: registration country (user_country)
2 symbols, user registration country, e.g. UK
Core: 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
Core: registration platform (core_registration_platform)
Registration platform from where user was registered
Core: risk rank (core_risk_rank)
Risk rank that can be used by the meaning specific for the platform
Core: state (core_reg_state)
State of the user
Core: time of day preference (core_time_of_day_pref)
Core: user type (core_user_type)
Type of user in the integrated platform
Core: username (core_username)
Username or nickname
Core: 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
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
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
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
{
"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
...
}
}
Calculating Aggregations Within Smartico
Smartico also offers the ability to compute these aggregations internally, using raw transactional data (bets, wins, deposits, withdrawals). However, the accuracy of these internal calculations depends heavily on the quality of the integration. Inaccuracies may arise in the following situations:
Missing Transactions: Certain transactions are not reported to Smartico due to technical issues.
Duplicate Transactions: Transactions are sent more than once.
Untracked Business Logic: Some platform-side operations (e.g., canceled deposits, reversals, corrections) impact the data but are not reflected in the raw transaction stream.
These discrepancies become particularly problematic for properties with long time windows. For example, if a single bet is missed, the total lifetime bet amount will remain permanently inaccurate.
Recommendations for Aggregation Updates
Despite these limitations, Smartico can still calculate aggregations with a daily rebuild schedule. The calculation time can be tailored to match the operational hours of the Platform. For instance, if your business operates in a specific time zone (e.g., UTC+3), Smartico can perform calculations accordingly.
Keep in mind that the time required to complete these recalculations depends on the size of your user base. Therefore, it is important to plan your usage of these properties in accordance with the time they become fully updated.
Supported aggregation properties:
Note: all "money" realated properties are of type "Multi-currency", means that value kept inside should be treated in combination with "core_wallet_currency". E.g. value 10 in Total GGR for one user could mean USD and for other CAD.
Smartico is providing efficient tools to do segmentation and targeting of users based on the different currencies.
GGR
Accounting: Total GGR
acc_total_ggr
Accounting: Last 90 days GGR
acc_last_90_days_ggr
Accounting: Last 60 days GGR
acc_last_60_days_ggr
Accounting: Last 30 days GGR
acc_last_30_days_ggr
Accounting: Last 7 days GGR
acc_last_7_days_ggr
Accounting: Last month GGR
acc_last_month_ggr
Accounting: Last week GGR
acc_last_week_ggr
Accounting: Yesterday GGR
acc_yesterday_ggr
Casino: Total / Lifetime GGR
casino_total_ggr
Casino: Last 90 days GGR
casino_last_90_days_ggr
Casino: Last 60 days GGR
casino_last_60_days_ggr
Casino: Last 30 days GGR
casino_last_30_days_ggr
Casino: Last 7 days GGR
casino_last_7_days_ggr
Casino: Last month GGR
casino_last_month_ggr
Casino: Last week GGR
casino_last_week_ggr
Casino: Yesterday GGR
casino_yesterday_ggr
Sport: Total GGR
sport_total_ggr
Sport: Last 90 days GGR
sport_last_90_days_ggr
Sport: Last 60 days GGR
sport_last_60_days_ggr
Sport: Last 30 days GGR
sport_last_30_days_ggr
Sport: Last 7 days GGR
sport_last_7_days_ggr
Sport: Last month GGR
sport_last_month_ggr
Sport: Last week GGR
sport_last_week_ggr
Sport: Yesterday GGR
sport_yesterday_ggr
NGR
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
Accounting: Net Deposit Amount (lifetime) (acc_net_deposit_amount)
Accounting: Withdrawal Amount (acc_last_withdrawal_amount)
Accounting: Average Withdrawal Amount (acc_avg_withdrawal_amount)
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
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
Casino bets, wins, counts
Casino: Total / Lifetime bet amount
casino_total_turnover
Casino: Total bets count
casino_total_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
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
Last updated
Was this helpful?