Skip to content
English
More support
Gamoshi.com
  • There are no suggestions because the search field is empty.

AppsFlyer Integration Guide for Gamoshi DSP

How to integrate AppsFlyer App conversion tracking with your Gamoshi DSP account.

Content

1. Overview

2. Required URL templates

3. Configuration Steps

4. End to end validation

5. Troubleshooting and best practices

 

1. Overview

This article provides a step-by-step walkthrough for integrating AppsFlyer app conversion tracking with your Gamoshi DSP account. This setup allows Gamoshi to attribute app installs and in-app events (like purchases or registrations) back to specific clicks and campaigns for optimization.

The integration follows a standard server-to-server (S2S) attribution flow consisting of two main parts:

  1. Click Tracking: Gamoshi sends users to the App Store or Play Store via an AppsFlyer tracking link embedded with Gamoshi macros.

  2. Conversion Tracking: When a tracked event occurs (e.g., an install), AppsFlyer sends a postback (callback) to Gamoshi using the click identifier provided earlier.

Integration Flow

  1. Gamoshi: Create a Conversion and a Goal to generate tracking IDs.

  2. Gamoshi: Build and apply the AppsFlyer Click URL in your conversion setup.

  3. AppsFlyer: Configure the Conversion Callback URL using Gamoshi IDs.

  4. Validation: Test the end-to-end flow.

 

2. Required URL Templates

Gamoshi Conversion Callback (Postback)

AppsFlyer must trigger this URL when a conversion event happens:

https://rtb.gamoshi.io/conversion/ss-web-h?conv_id=CONVERSION_ID&goal_id=GOAL_ID&conv_value=CONVERSTION_VALUE&ifa={Android Device ID}&order_id={AppsFlyer ID}&user_id={Customer user ID}&click_id={Click ID}



AppsFlyer Click URL

Use this as the destination or tracking URL in the Gamoshi platform, replace the macro of app_id with the the advertised app identifier in AppsFlyer (without the brackets).

https://app.appsflyer.com/{app_id}?pid=gamoshiid_int&af_siteid=[PUBLISHER_ID]&af_c_id=[CAMPAIGN_ID]&af_ad_id=[AD_ID]&af_ad_type=[AD_TYPE]&af_channel=[INVENTORY_ID]&clickid=[REQ_ID]&advertising_id=[IFA]&af_model=[DEVICE_MODE]

  • For iOS, {app_id} should be the App Store ID in the format id123456789.

  • For Android, {app_id} should be the package name, such as com.company.app.

     

Example for iOS:

https://app.appsflyer.com/id123456789?pid=gamoshiid_int&af_siteid=[PUBLISHER_ID]&af_c_id=[CAMPAIGN_ID]&af_ad_id=[AD_ID]&af_ad_type=[AD_TYPE]&af_channel=[INVENTORY_ID]&clickid=[REQ_ID]&advertising_id=[IFA]&af_model=[DEVICE_MODE]

Example for Android:

https://app.appsflyer.com/com.company.app?pid=gamoshiid_int&af_siteid=[PUBLISHER_ID]&af_c_id=[CAMPAIGN_ID]&af_ad_id=[AD_ID]&af_ad_type=[AD_TYPE]&af_channel=[INVENTORY_ID]&clickid=[REQ_ID]&advertising_id=[IFA]&af_model=[DEVICE_MODE]

 

 

3. Configuration Steps

Step 1: Create a Conversion in Gamoshi

In the Gamoshi platform, in the Advertisers module -> Conversions screen define the high-level conversion. In order to do that you will need to create an Advertiser first or use an exsting one

  • Conversion Name: Use a clear business name (e.g., Mobile App Install).

  • Advertiser : Choose the relevant Advertiser from the select box

  • Type: Choose 'App'

  • Click URL: Insert the Appsflyer click URL link from the previous section in this article and replace the app_id macro with the advertised app identifier in AppsFlyer.

  • Create: Press the 'Create' button to create the conversion and generate a Conversion ID.

Step 2: Create a Goal in Gamoshi

Goals represent specific events under a conversion. Gamoshi uses Goals for reporting and algorithmic optimization.

  • A default goal of 'Click to Install' is automatically being created on creation of the conversion 

  • Add more goals per AppsFlyer event (e.g., Registration, First Deposit) you can use predefined events from the select box or choose Custom.

  • Action: Press 'Save' to create the goal and generate a Goal ID. 

Step 3: Configure the Postback in AppsFlyer

In the AppsFlyer dashboard, go to Active Integrations, search for Gamoshi (or use the custom partner setup), and configure the postback for your events.

Mapping the Postback URL: Replace CONV_ID (conversion id) and GOAL_ID with the values obtained in Steps 1 and 2. You can also replace the Conversion Value macro if needed.

Example Mapping:

  • Gamoshi Conversion ID: 1001

  • Gamoshi Goal ID: 2005

  • Conversion Value: $1

  • Resulting URL:

    https://rtb.gamoshi.io/conversion/ss-web-h?
      conv_id=1001&
      goal_id=2005&
      conv_value=1&
      ifa={Android Device ID}&
      order_id={AppsFlyer ID}&
      user_id={Customer user ID}&
      click_id={Click ID}

     

Step 4: Associate the conversion in your Gamoshi DSP account with the relevant creatives

In you Gamoshi DSP account create or edit in the advertiser Module the relevant creatives for the conversion you have setup. Go to the  Advertiser module -> Advertiser setup -> Creatives tab or Creatives screen. 

  • On the 'Conversion and Tracking' section of the creative choose the 'Select Conversion' radio button option and select the relvant conversion from the select box.

  • Activate the 'Use Conversion target URL' switch in order to use the conversion target URL.

  • Create relevant campaigns for the advertiser and associate them with the relevant creatives.

 

4. End-to-End Validation

Before scaling your campaign, verify the integration using the following checklist:

  1. Click Check: Click the ad. Does it redirect to the correct App Store page?

  2. Macro Check: In Gamoshi reports, verify that [REQ_ID] and [IFA] are being passed correctly in the click logs.

  3. Postback Check: Trigger the conversion event on a test device.

  4. Reporting Check: Confirm that the conversion appears in the Gamoshi dashboard under the correct Campaign and Goal.

 

5. Troubleshooting & Best Practices

Common Issues

  • No Conversions in Gamoshi: Verify that clickid in the Click URL exactly matches the parameter used to pass click_id back in the Postback URL.

  • Attribution Discrepancies: Ensure {app_id} is correct. For iOS, it must include the id prefix (e.g., id123456789). For Android, use the full package name (e.g., com.example.app).

  • Missing Device IDs: Ensure the [IFA] macro is included in the click URL to help AppsFlyer with deterministic matching.

Best Practices

  • One Goal per Event: Maintain a 1:1 relationship between AppsFlyer events and Gamoshi Goals for granular optimization.

  • Consistent Naming: Match your Gamoshi Goal names to your AppsFlyer event names to avoid confusion during audit sessions.

  • Test Real Devices: Always perform a live test with a real device to ensure the redirect and postback trigger correctly across different OS versions.