Adjust Validator

Introduction

The Adjust Validator is used when your game relies on Adjust for revenue tracking, attribution, and UA optimization.

This validator ensures that only validated purchases are reported to Adjust as revenue, preventing invalid or fraudulent transactions from polluting Adjust dashboards and UA network learning.

Receipt validation logic is centralized through LionSDK, while Adjust serves as the destination for trusted revenue events, not as a gameplay or reward authority.


Setup

Based on the game status, the requirements differ:

  • Contact your Product Manager so the app can be set up on the Adjust dashboard.


What the Adjust Validator Does

When the Adjust Validator is enabled:

  • Every purchase is logged as an inapp_purchase event to Lion Analytics.

  • Receipt validation is performed as part of the LionSDK IAP Validation flow.

  • Only if the receipt is validated successfully:

    • A native iap_purchase event is fired to Adjust.

  • If the receipt is invalid, duplicated, or fails validation:

    • No revenue event is sent to Adjust.

    • The purchase is still recorded internally with a corresponding ValidationStatus.

This ensures that Adjust revenue metrics and UA optimization are based only on trusted purchase data.


Validation Outcomes

Depending on the validation result, the following behaviour applies:

  • Valid receipt

    • inapp_purchase event is logged with ValidationStatus = Success

    • Adjust receives the iap_purchase revenue event

  • Invalid or fraudulent receipt

    • inapp_purchase event is logged with ValidationStatus = Failure

    • No Adjust revenue event is fired

  • Validation error (store or network issue)

    • inapp_purchase event is logged with ValidationStatus = Error

    • No Adjust revenue event is fired

These outcomes allow internal analytics to retain full visibility while preventing invalid transactions from impacting Adjust dashboards and UA learning.

Last updated

Was this helpful?