At a glance: How ad networks integrate the Hubscale platform with AppsFlyer Probabilistic modeling. AppsFlyer sends attribution data to Hubscale for both install and in-app events.
To initiate the integration you need to send AppsFlyer:
- Your attribution link
- Your postback (for installs and in-app events)
Creating the attribution link
the attribution link consists of the below AppsFlyer base attribution link and additional macros added by the ad-network.
See below AppsFlyers base attribution link with a detailed explanation per macro:
AppsFlyer Base URL | Description |
---|---|
http://app.appsflyer.com |
AppsFlyer end point |
app_id |
Application unique ID – dynamic value changed per app promoted |
pid= |
Media source name concatenated with _int to identify integrated networks |
c= |
Campaign name |
See below what the complete attribution link should look like after you have added additional Hubscale macros:
http://app.appsflyer.com/com.appsflyer?pid=mediaName_int&clickid=
{transaction_id}&af_siteid={affiliate_id}&af_sub5={offer_id}af_ad_id=
{offer_file_id}&advertising_id={google_aid}&idfa={ios_ifa}" target="
_blank" rel="nofollow noopener noreferrer" data-is-link="http://
app.appsflyer.com/com.appsflyer?pid=mediaName_int&clickid={transaction_id}
&af_siteid={affiliate_id}&af_sub5={offer_id}af_ad_id={offer_file_id}
&advertising_id={google_aid}&idfa={ios_ifa}">
http://app.appsflyer.com/com.appsflyer?pid=mediaName_int&clickid=
{transaction_id}&af_siteid={pub_id}-{sub_pub_id}&advertising_id=
{google_id}&idfa={ios_ifa}
AppsFlyer complete list of parameters
Global postbacks for installs and in-app events:
Hubscale has global postbacks for installs and in-app events:
For installs:
http://companyname.156th.com/conv?transaction_id={publisher_ref_id}&ios_ifa={ios_ifa}
&google_id={google_aid}&app_version={app_version}&language={language}&ext_country_code={country_code}
&ext_city={city}&user_agent={user_agent}&user_ip={device_ip}&adv_revenue={revenue_usd}
For post-install events, Hubscale can record up to nine post-install events for the same Transaction ID. Nine global postbacks should be created as templates as shown below:
Event number | URL template |
---|---|
Event 2 (event 1 is the install) |
|
Event 3 |
|
Event 4 | ... |
... | ... |
Event 10 |
|
The Event tag is what is entered by the advertiser when mapping the events.
If the name of the partner using Hubscale is PARTNER, then the domain is normally: partner.156th.com.
Generic attribution link:
https://app.appsflyer.com/com.appsflyer?pid=partnername_int&clickid={transaction_id}&af_siteid={pub_id}-{sub_pub_id}&advertising_id={google_id}&idfa={ios_ifa}
Finalizing your registration
- If you currently have an integration with AppsFlyer contact us at partners@appsflyer.com
- If you do not currently have an integration with AppsFlyer, complete the ad Partners Registration application here.
Mapping of AppsFlyer parameters and hubscale macros
AppsFlyer Parameters | Hubscale Macros | Description |
---|---|---|
pid |
pub_id | Media source name - for integrated partners and should not be changed. More details. |
c |
campaign_name | Campaign name - provided by the advertiser. |
clickid |
transaction_id |
The Ad network unique click identifier |
af_siteid |
pub_id |
Ad Network publisher ID |
af_sub_siteid |
sub_pub_id |
Ad Sub-Network/Publisher ID |
af_c_id |
campaign_id |
Campaign ID - provided by the advertiser |
af_adset |
Adset Name - provided by the advertiser. Adset |
|
af_ad |
adv_name | Ad Name (see more) |
af_ad_id |
adv_id | Ad ID |
af_cost_model |
adv_payout_model | Cost model - CPI is currently the only supported model |
af_cost_currency |
adv_payout_currency | Currency code (example: USD) |
af_cost_value |
adv_payout_amount | Cost value |