Button
- 20 Feb 2025
- DarkLight
Button
- Updated on 20 Feb 2025
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
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
1. Button has been provided with the Awin postbacks for Installs and In-App purchase event which they customise on a case by case basis
2. Attribution is based on last click and attribution settings are implemented by the provider
3. Button provides Awin with a tracking link which needs to be enabled for the test publisher as a mobile prefix
4. The Button tracking link https://r.bttn.io/ is customised with parameters listed below
5. The provider will run the tests and once it is successful the mobile prefix will be enabled to all or select publishers
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 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!!! - The encoded destination URL of the user with all 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.etsy.com/uk/c/home-and-living/bedding/blankets-and-throws | !!!redirectURL!!! | This should have all relevant appends and prefixes which is why it's the redirectURL and not the merchanturl dynamic parameter. |
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 idenitifer 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 should have all relevant appends and prefixes which is why it's the redirectURL and not the merchanturl dynamic parameter. |
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 should have all relevant appends and prefixes which is why it's the redirectURL and not the merchanturl dynamic parameter. |
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 publisher 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.
Was this article helpful?