Events deliver structured, near real-time data that allows publishers to monitor and respond to critical activities such as player logins, store interactions, and payment processing.
For a detailed guide on configuring the event webhook, refer to the Events Guide.
Login events track player authentication and navigation through the login flow.
Includes:
Login Land
Login Method Selected
Login Canceled
Login Resolved
Shop Land
These events capture player interactions with offers in the Webstore.
Includes:
Offers Loaded
Offers Shown
Approval Request Displayed
Approval Request Closed
Error events provide technical insights to identify and troubleshoot issues.
Includes:
Invalid Property Error
Order events track the full lifecycle of orders, from creation to completion or cancellation.
Includes:
Order Created
Payment Intent Success
Payment Intent Failed
Order Completed Success
Order Completed Failed
Order Canceled
Dispute events manage post-purchase activities, such as refunds and chargebacks.
Includes:
Order Refunded
Order Dispute Open
Order Dispute Won
Order Dispute Lost
If the Events Webhook fails to deliver an event due to a server-side error on the publisher’s end, Appcharge retries delivery up to 3 times. Each retry occurs after a 5 minute delay.
A Session ID identifies the player’s current session. A session begins when the player logs in or returns to the web store, and it ends after 30 minutes of inactivity or when the player logs out. If the player opens the web store in different browsers or on separate devices at the same time, each instance generates a unique Session ID. However, opening the store in multiple tabs within the same browser will use the same Session ID.
You can use the Session ID to track and analyze player activity. This supports both behavioral analysis and debugging.