Winclap Analytics integration with AppsFlyer

Introduction

Winclap Analytics, an AppsFlyer integrated partner, uses AppsFlyer attribution data for BI and post-attribution analytics. 

To configure campaigns using Winclap ad network, read this guide.

 Important!

The terms of service of some media sources prohibit sharing user-level data with third parties. In compliance with this, AppsFlyer does not provide user-level data of users acquired through these media sources with third-party platforms or services. Installs from such media sources are sent to third parties as organic.

For more details and tue list of media sources that restrict sharing data with third parties, click here.

Setting up Winclap

In AppsFlyer, go to Configuration > Integrated partners.

Enter "Winclap Analytics" in the search field.

Click Winclap Analytics.

winclap-analytics-integration.png

Winclap Analytics configuration makes use of the Integration tab only.

For a detailed description of the Partner Configuration Window Header, click here.

Integration tab

The Integration Tab is divided into different sections as described below.

Activate partner

On the first visit here, you will need to at the Activate Partner toggle to enable setup of the integration tab's parameters. The toggle MUST be ON for as long as you work with the partner.
For more details about partner activation please click here.

General settings

Enter your winclap_advertiser_idIf you do not know yours, you can get it from your Winclap account manager. 

Default postbacks

AppsFlyer can send automatic postbacks to Winclap Analytics user installs and re-engagements. Use this section to define the source of the users that allow sending these postbacks.

winclap-analytics-default-postbacks.png

For installs, select:

  • (Default) Only events attributed to this partner for events coming only from users attributed to Winclap.
  • Events attributed to any partner or organic to send postbacks for any user that downloads the app to Winclap.

For reengagements, the postbacks can be sent Only for events attributed to this partner.

Click Save integration.

Once this configuration is saved, AppsFlyer sends the following data to Winclap Analytics for each install, both organic and non-organic:

  • Click ID
  • Campaign name
  • User-agent
  • Click time
  • IP
  • Country
  • City
  • Sub publisher
  • Device ID for Android & iOS
  • Carrier
  • Language
  • App ID
  • App version
  • App name
  • Install time

In-app events settings

In this section, you can map which in-app events to send to Winclap Analytics using postbacks:

winclap-iae-postbacks.png

  1. Switch the In-App Event Postbacks toggle to ON.
  2. Set the In-app event postback window, if required (read more about in-app event postback window configuration).
  3. Select the Sending Option for all SDK defined events.
    • Only events attributed to this partner for events coming only from users attributed to this partner
    • Events attributed to any partner or organic to have your entire user base available to be reported to the partner
  4. Click Add Event to add an SDK Event to the list
  5. Complete the following parameters:
Parameter Name Description
SDK Event Name The name of the event, as received by AppsFlyer either from the SDK integrated in your app, or from server to server events.
Tip: Don't see the event you are looking for? Type in its SDK Event Name, click Create custom, and map normally. Read more about custom event mapping.
Partner Event Identifier

The unique name or ID of each event as defined on Winclap's side.

Obtain the corresponding Event ID from Winclap and set in the text field.

Send Revenue When unchecked - AppsFlyer sends all the parameters of the rich in-app event to the partner, except for the revenue parameter, which is contained in the af_revenue parameter.
When checked - AppsFlyer sends all the parameters including the revenue value (if it exists in the event). 

Click Save.

Once this configuration is saved, AppsFlyer sends the following data to Winclap Analytics for each non-organic event:

  • Click ID
  • Event name
  • Event value
  • Event revenue
  • Event currency
  • Event revenue in USD
  • Campaign name
  • User-agent
  • Click time
  • IP
  • Country
  • City
  • Sub publisher
  • Device ID for Android & iOS
  • Carrier
  • Language
  • App ID
  • App version
  • App name
  • Install time

Attribution link tab

Attribution Links are not available for Winclap Analytics.
 

Cost tab

Cost data is not supported in the integration with this partner.

Ad revenue tab

Ad Revenue is not supported in the integration with this partner.

Permissions tab

Permissions are not available for Winclap Analytics.

 

Was this article helpful?
0 out of 0 found this helpful