Winclap Analytics integration with AppsFlyer

For:
Marketers
Last update:

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

 Important!

Some media sources restrict sharing data with third parties. Therefore, postbacks for restricted events won't be sent to this partner, regardless of the configured selection for sending postbacks.

Setting up Winclap

The setup is done from the Active Integrations page, but to find the partner you must first go to the marketplace. 

 Note

Before setting up an integration, make sure you contact the partner and open an account with them.

To activate the integration:

  1. From the top menu of any AppsFlyer page, click Marketplace. 
  2. Search for the partner and select it.
  3. Click Set up integration. You’re directed to the integration setup page.
  4. In the Integration tab, select the app for the integration and turn Activate partner on.
    Note: The toggle must be on (activated) for as long as you work with the partner.
  5. Complete the configuration using the relevant tabs, as described below.

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 must toggle ON the Activate Partner toggle to enable the 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.

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 integration - default postbacks

For installs, select:

  • (Default) This partner only for events coming only from users attributed to Winclap.
  • All media sources, including organic to send postbacks for any user that downloads the app to Winclap.

For reengagements, the postbacks can be sent for This partner only.

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 analytics - in-app event postback configuration
  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. Click Add Event to add an SDK Event to the list.
  4. 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 by Winclap.
    Get from Winclap the corresponding ID for each of the events you want to report to them, and enter in this field.
    Sending option Select the sending option for the event:
    This partner only for events coming only from users attributed to this partner
    All media sources, including organic to have your entire user base available to be reported to the partner
    Send event data
    • No values & no revenue: sends only the event itself without the event value.
    • Values & no revenue: sends all the parameters excluding the revenue value.
    • Values & revenue: sends all the event parameters, including the revenue value (if exists in the event).
  5. 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.