Home Integrations

Integrations

Integrate UCLIQ with external tracking, analytics, and advertising platforms. Simplify workflow automation and improve campaign performance seamlessly.
By Azema
3 articles

AppsFlyer Integration

First, create your offer in the UCLIQ Manager portal. Include relevant targeting details and daily caps. Define your postback goals clearly in UCLIQ. Common goals include: - INSTALL - CPS (Cost per Sale) - Re-attribution Also set appropriate payouts for each goal. Advertiser Link Setup Use your Appsflyer OneLink or device-specific URLs (Android or iOS) as your advertiser link in UCLIQ. You can find details about parameters and macros directly in Appsflyer's guide. Your Appsflyer link typically looks like: https://app.appsflyer.com/com.appsflyer?pid=yourmediaid&clickid={click_id}&af_c_id=2&af_siteid={source}&advertising_id={sub1} Key Macros: - clickid – UCLIQ-generated click ID - af_c_id – Offer ID (constant or publisher-provided) - af_siteid – Source identifier from the publisher - advertising_id – Publisher advertising ID (optional) UCLIQ Publisher Tracking Link Your publisher tracking link in UCLIQ sends crucial campaign data to Appsflyer: Example: http://yournetworkid.afflnx.com/c/YourCampaignKey?sub1=advertising_id Replace advertising_id with the macro provided by your advertising platform. Postback Configuration Appsflyer needs postbacks to relay event data back to UCLIQ. Installation Postbacks Configure distinct postbacks for iOS and Android installations: - iOS Install Example: https://yournetworkid.utrfk.com/pb/YOURSECURITYKEY?click_id={clickid}&goal=INSTALL_IOS&ext={idfa}&tid={eventtime} - Android Install Example: https://yournetworkid.utrfk.com/pb/YOURSECURITYKEY?click_id={clickid}&goal=INSTALL_ANDROID&ext={android_id}&tid={eventtime} Value-Driven Event Postbacks For PPS or CPS events with dynamic payouts: - iOS Event Example: https://yournetworkid.utrfk.com/pb/YOURSECURITYKEY?click_id={clickid}&goal=PPS_IOS&ext={idfa}&tid={eventtime}&sum={event_value}&ext2={event_name}&currency={currency} - Android Event Example: https://yournetworkid.utrfk.com/pb/YOURSECURITYKEY?click_id={clickid}&goal=PPS_ANDROID&ext={android_id}&tid={eventtime}&sum={event_value}&ext2={event_name}&currency={currency} Fixed Value Postbacks If you prefer setting fixed values independently of Appsflyer: - iOS Event Fixed Example: https://yournetworkid.utrfk.com/pb/YOURSECURITYKEY?click_id={clickid}&goal={event_name}&ext={idfa}&tid={eventtime} - Android Event Fixed Example: https://yournetworkid.utrfk.com/pb/YOURSECURITYKEY?click_id={clickid}&goal={event_name}&ext={android_id}&tid={eventtime} Always ensure event names exactly match those configured in Appsflyer. After completing these steps, thoroughly test your integration to ensure proper tracking and attribution. For any further assistance, feel free to reach out to our support team.

Last updated on May 05, 2025

ADVERTISER LINKS, POSTBACKS, MACROS

UCLIQ Advertiser Links Ucliq advertiser offer link, transferring a visitor’s browser from a tracking link to an advertiser offer link has a following format: https://offers.advertiser.com/offer111/?click={click_id}&p1={publisher_id}&p2={publisher_me}&p3={source}&p4={subsource}&p5={country}&p6={time}&p7={city}&p8={language}&p11={sub1}&p12={sub2}&p13={sub3}&p14={sub4}&p15={sub5}&p16={sub6} Visitor is being redirected to this offer using the aforementioned link, using GET request with either Javascript or HTTP-based redirect requests. Macros, being passed by Ucliq: - {publisher_id} - Ucliq’s publisher id - {publisher_username} - Ucliq’s publisher username - {click_id} - Ucliq’s click id - {source} - a combination of Ucliq’s publisher id and subsource - {subsource} - subsource submitted in the tracking URL - {country} - country of the click origin, e.g. 'US' or 'CA' - {time} - date and time of the click - {city} - traffic’s city(determined from the IP) - {offer_name} - Ucliq’s offer display name - {language} - traffic’s language (determined from the user agent) - {sub1}-{sub6} - additional parameters, passed as a part of the tracking link by an affiliate MMP INTEGRATIONS For MMA platforms, publishers can set up their advertising platform to pass information about advertising settings, cost, region, campaign to the MMA/Advertiser using custom parameters such as subsource, track, sub1..sub6. MMP can return additional information to UCLIQ via postbacks using custom parameters ext1... ext6. POSTBACKS FROM ADVERTISER TO UCLIQ These are S2S postbacks sent by Advertisers, Integrators to Ucliq to register a conversion or an event. Postbacks are accepted in the form of a GET HTTP call. Link format: https://track.ucliq.com/pb/aaaabbbbccccddddeeeeffff?sum= <conversion amount> &click_id=<Ucliq ClickID> &tid= <transaction_id> &goal= <Goal Alias> &ext1 = <external data 1> & .. &ext6 =<external data 6> Where: - https://track.ucliq.com/pb/aaaabbbbccccddddeeeeffff - postback link, containing a postback URL specific to a customer of Ucliq, including a postback security token - Sum - amount of conversion, optional, decimal - Click_id - original Ucliq’s click id provided as a part of the offer link to an Advertiser, mandatory, alphanumeric - Tid - transaction id from an Advertiser, optional, alphanumeric - Goal - conversion goal/event alias, specified in Ucliq platform, optional, alphanumeric - ext1 - ext6 - additional data provided by an advertiser, available in Ucliq platform and can be passed to a publisher in publisher’s postbacks, optional, alphanumeric After a GET request has been sent, the server will respond with an OK message and 200 code, or with an error message, describing error and 4xx response code

Last updated on May 07, 2025