Attribution flow
The following flow explains how player activity is attributed between your game and Appcharge.Publisher side
When a player performs an in-game action, such as a purchase:- Send an in-app event, like the Purchase event (
af_purchase
), to AppsFlyer. This event must include the player’s CUID (player ID). - AppsFlyer sends an in-app event to Appcharge as a postback that includes:
- Publisher ID
- AppsFlyer ID
- CUID You can configure which in-app events trigger postbacks in your AppsFlyer dashboard. Learn how to configure postbacks.

Appcharge side
When a player performs an action in the web store or checkout, such as making a purchase or requesting a refund, Appcharge:- Identifies the player using the CUID.
- Maps the CUID to the AppsFlyer ID.
- Sends the event and AppsFlyer ID to AppsFlyer for attribution and reporting.
ac_af_purchase
: Sent when a player successfully completes a purchase.ac_af_refund
: Sent when a refund is completed.

Setup
Follow these steps to configure the integration:- Log in to your AppsFlyer HQ account, or create one if needed.
- Follow the instructions in AppsFlyer’s integration guide to set up the integration on the AppsFlyer side.
- Create or retrieve your S2S (server-to-server) token.
Note: You must be an AppsFlyer account admin to view or manage tokens.
- Send the S2S token to your Appcharge account manager. This token allows Appcharge to send attributed events to AppsFlyer on your behalf. Once the token is received, Appcharge will finalize the configuration.