An event triggered when the player successfully completes the login process and is authenticated.
Event Data
The time when the event occurred. Example: 1632345000
The type of player authentication event. In this case, login_resolved. Example: login_resolved
The device platform used by the player. Example: mobile
The interface through which the player accessed the login page. Supported values:
browser app
: Mobile or desktop browser.webview
: An in-app webview.homescreen bookmark
: A saved home screen shortcut or bookmark.The two-letter country code of the player. Example: US
The session ID of the player’s current session. Example: 345397c6-d963-4aa4-a0ba-2aaca6c3ee05
The authentication method selected by the player in the main login screen. Optional Values: facebook, google, apple, user_name, OTP. Example: facebook
The result of the login_resolved event. Example: success
Optional. The reason for the login_resolved failure. Example: invalid_credentials
Relevant only to Personalization API users, the player session metadata object received from the Personalization API. Example: { "metadata": "data" }
Identifies the source of your traffic. Optional Values: google, facebook, instagram. Example: google
Specifies the medium through which the traffic arrived. Optional Values: cpc, email, social, referral. Example: cpc
Identifies the marketing campaign associated with the traffic. Optional Values: spring_sale, retargeting, black_friday. Example: spring_sale