AppsFlyer integration setup
Follow these steps to configure the AppsFlyer integration on both Appcharge and AppsFlyer’s side.Configure in AppsFlyer
To configure the integration in AppsFlyer:- Log in to your AppsFlyer HQ account, or create one if needed.
-
Follow the instructions to go to the token page, and then follow the steps to create a new S2S (server-to-server) token or retrieve an existing one.
You must be an AppsFlyer account admin to view or manage tokens.
- Copy and save the S2S token for later.
-
Follow AppsFlyer’s documentation on how to set up the integration with Appcharge. As part of this setup:
- Set up integrations for all your AppsFlyer apps that you want to integrate with Appcharge, and save all the app IDs for later.
- In the in-app event postbacks section, add all your game login events and make sure each includes the player’s CUID (player ID) and AppsFlyer ID. When a player logs in, AppsFlyer sends this data to Appcharge to identify the player. Appcharge uses the most recent AppsFlyer ID to identify each player, so attribution is always tied to the last device they logged in on.
Attribution is only recorded when a player logs in. If a player is already logged in, Appcharge won’t receive their AppsFlyer ID until they log in again.
Configure in Appcharge
To configure the integration in Appcharge:-
Go to the Publisher Dashboard. In the sidebar menu, go to Management > Settings > Developer Settings.
If you have a Game Portal, follow the same steps in your Game Portal project.
- Scroll to AppsFlyer S2S Integration, and click Open Settings.
-
Complete the following sections:
- AppsFlyer S2S Integration: Toggle on to enable the integration.
- AppsFlyer S2S Token: Enter the S2S token saved from AppsFlyer. This token allows Appcharge to send attributed events to AppsFlyer on your behalf.
- Application ID: Enter the ID of your AppsFlyer app. Click + Application ID to add additional app IDs as needed.
-
Event Name Configuration: Set the event names that Appcharge will use when sending events to AppsFlyer.
- Purchase Event: The event name to send to AppsFlyer when a player completes a purchase on the Appcharge platform. Defaults to
appcharge-billing-payment. - Refund Event: The event name to send to AppsFlyer when a player receives a refund through Appcharge. Defaults to
appcharge-billing-refund.
- Purchase Event: The event name to send to AppsFlyer when a player completes a purchase on the Appcharge platform. Defaults to
- In the top right corner, click Save to save your changes.
