Overview

This webhook is triggered for events related to player authentication, providing details about login attempts, selected methods, cancellations, and resolution outcomes. It logs specific events that occur during player login but does not capture real-time browsing or interaction details.

Webhook Endpoint

• URL: https://{publisher-server}/events
• Method: POST

Event Data Structure

The following data will be included in the report:

• event (string): The type of authentication-related event. Possible values are:
  • login_land: When the login page is displayed.
  • login_method_selected: When a login method is chosen.
  • login_canceled: When the login process is canceled.
  • login_resolved: When the login process concludes, successfully or unsuccessfully.
• timestamp (number): The Unix timestamp when the event occurred.
• loginMethod (string, optional): The selected login method. Possible values are:
  • facebook
  • google
  • apple
  • userPassword
  • userToken
  • otp
• platform (string): The device platform of the user.
• countryCode2 (string): The two-letter country code of the user.
• sessionId (string): The session ID for Appcharge.
• result (string, optional): The result of the login_resolved event, if applicable.
• reason (string, optional): The reason for a failed login_resolved event.

Example Payload

Here is an example of what the payload might look like:

data {
  timestamp: 1728973034967,
  event: 'login_resolved',
  platform: 'web',
  countryCode2: 'IL',
  sessionId: 'e8d33998-0b9a-4168-aead-b74869ca7da7',
  loginMethod: 'userToken',
  result: 'success'
}