Note
For information from Button, please see here.
Features and limitations
There is unfortunately no integration between Button and Awin.
Integration is done on a case by case basis between Strategic Partnership, Button and client.
Deep-linking is supported.
Integrating Awin tracking
Integrating Button
Button has been provided with the Awin postbacks for installs and in-app purchase event which they customize on a case by case basis.
Attribution is based on last click and attribution settings are implemented by the provider.
Button provides Awin with a tracking link which needs to be enabled for the test partner as a mobile prefix.
The Button tracking link https://r.bttn.io/ is customized with parameters listed below.
The provider will run the tests and once it’s successful the mobile prefix will be enabled to all or selected partners.
Sale-based tracking
Setup commission group on Awin for APP_DEFAULT.
Adding &type=ap into the tracking calls allows Awin reports to identify in-app activity without the need for app based commission groups.
Button should pass back the following:
https://www.awin1.com/sread.img?tt=ns&tv=2&merchant=6091&ch=aw&testmode=0&amount=19.99&parts=APP_DEFAULT:19.99&ref=383028169256&cr=GBP&cks=3797_1535473580_501804673273d9b1926be9dcd560e9f1&type=apInstall-based tracking
Setup commission group on Awin for APP_INSTALL.
Add &type=ai into the tracking calls.
Button should pass back the following:
https://www.awin1.com/sread.img?tt=ns&tv=2&merchant=6091&ch=aw&testmode=0&amount=19.99&parts=APP_INSTALL:1.00&ref={GPS_ADID}&cr=GBP&cks=3797_1535473580_501804673273d9b1926be9dcd560e9f1&type=aiDynamic parameters
!!!merchanturl!!! - The unencoded destination URL of the user.
!!!merchanturlcm!!! - The encoded destination URL of the user.
!!!redirecturl!!! - Populates an encoded version of the destination URL including all relevant prefixes and appends.
Final testing link
https://r.bttn.io/?btn_url=!!!redirectURL!!!&btn_pub_ref=!!!awc!!!&btn_ref=org-70d3021cf848725a&btn_desktop_url=!!!redirectURL!!!&btn_fallback_exp=interstitial&btn_mobile_url=!!!redirectURL!!!&btn_reach_pub=!!!affid!!!&networkref=Parameters within the Button Tracking Link:
Tracking parameter | Description | Usual Awin setup | Notes |
|---|---|---|---|
btn_url= | This is the (encoded) intended destination of the user. For example: https://www.advertiser-example.com/uk/c/home-and-living/bedding/blankets-and-throws | !!!redirectURL!!! | This populates an encoded version of the destination URL including all relevant prefixes and appends which is why it’s the |
btn_pub_ref= | This is the reference we want Button to maintain through to the confirmation page. In our case, this is the AWC parameter, our unique identifer per click. | !!!awc!!! | This value is also used to extract Advertiser ID. |
btn_ref= | This is Button’s identifier for who the source of the traffic is. | org-70d3021cf848725a | Static value for Awin campaigns. |
btn_desktop_url= | This is the destination URL for when the user is on a desktop. | !!!redirectURL!!! | This populates an encoded version of the destination URL including all relevant prefixes and appends which is why it’s the |
btn_fallback_exp= | This is Button’s identifier to decide what they should do when the user doesn’t have the app. | interstitial | In almost all cases, Button will push for this to be an interstitial that prompts for app download but an advertiser could decide that straight to mobile web is a better experience when the app is not installed. |
btn_mobile_url= | This is the destination URL for when the user is staying on mobile web (and not going into the app). | !!!redirectURL!!! | This populates an encoded version of the destination URL including all relevant prefixes and appends which is why it's the |
networkref= | This pushes the un-encoded destination URL into an unused parameter. | Left blank as it will populate on the click. | |
btn_reach_pub= | Awin partner identifier | !!!affid!!! |
Testing your app tracking
Once you’ve completed the installation of your app tracking, please get in touch with your assigned Awin technical point of contact for more information on how to test your tracking.
For a more general overview of the testing process, please review our Testing your Integration article.