Home Integrations

Integrations

Integrate UCLIQ with external tracking, analytics, and advertising platforms. Simplify workflow automation and improve campaign performance seamlessly.
By Azema
• 7 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

UCLIQ & Microsoft (Bing) Ads Technical Setup

This guide explains how to configure Ucliq tracking with Microsoft Ads using Parallel Tracking. Step 1. Configure the Offer in Ucliq 1. Create a new Offer in Ucliq 2. Set: - Redirect type: HTTP -No targeting rules, caps, or device restrictions 3. Configure at least one Goal 4. In the Advertiser Link: -use your landing page URL -pass Ucliq’s internal click_id Step 2. Configure Microsoft Ads Campaign 2.1 Final URL (Landing Page) Set the Final URL to your actual landing page: https://example.com Users will be sent directly to this page after clicking the ad. 2.2 Landing Page Parameters (Required) Pass the Microsoft click ID to your landing page: clickid={msclkid} Final landing page example: https://example.com?clickid=XXXXXXXX This value will later be used in the conversion postback. 2.3 Tracking Template (Required) In the Tracking Template field, paste your UCLIQ tracking link and pass msclkid as ext_click_id. Example: https://yourtracking.domain/c/CAMPAIGN_KEY?ext_click_id={msclkid}&sub1={AdGroupId}&sub2={CampaignId} Required: - {msclkid} must be passed - ext_click_id must contain {msclkid} Optional: - sub1 / sub2 / sub3 for additional reporting 2.4 Enable Tracking Permission Make sure tracking templates are allowed at the campaign or account level in Microsoft Ads. If tracking is disabled, msclkid will not be generated. Step 3. Parallel Tracking Compatibility Your landing page must handle two parallel requests: 1. User > landing page 2. Microsoft Ads > Ucliq (background request) The Ucliq request contains: - Microsoft click ID (msclkid) - Ucliq internal click_id Both values must be stored correctly. Step 4. Send Postback to Ucliq When a conversion happens, send a server-to-server postback to Ucliq. Example: https://ucliq.domain/pb/YOUR_KEY?click_id={clickid}&currency=USD&sum=10 Where: - {clickid} = msclkid stored on the landing page - sum = conversion amount (if applicable) - currency = conversion currency Pre-Launch Checklist - msclkid passed in Tracking Template - msclkid passed to landing page - Landing page stores clickid - Postback includes click_id - Offer redirect type is HTTP Common Issues Conversions not tracked - msclkid missing in Tracking Template - postback sent without click_id Clicks tracked, conversions missing - landing page does not store msclkid - parameter name mismatch (clickid vs click_id)

Last updated on Jan 10, 2026

Google Ads Integration Overview

This article provides a high-level overview of how Google Ads tracking works with UCLIQ, what requirements must be met, and why certified setup is mandatory. What is Google Ads tracking in Ucliq? Ucliqis a Google-certified third-party tracking provider, which means it is officially approved to track Google Ads traffic in compliance with Google’s technical and privacy requirements. This certification guarantees: - Correct click and conversion attribution - Compatibility with Google Ads infrastructure - Support for Parallel Tracking - High-speed tracking without user redirects Why Google certification matters Google Ads allows only certified tracking domains and partners. Using non-certified tracking may result in: - Broken attribution - Conversion mismatches - Campaign disapproval or limited delivery Ucliq certification ensures that: - Tracking requests are processed in parallel (no redirect delays) - Click IDs are captured securely - Data accuracy meets Google’s performance standards Parallel Tracking explained Google Ads uses Parallel Tracking by default. How it works: - The user is sent directly to the landing page - The tracking URL is triggered in the background - No visible redirects occur This improves: - Page load speed - User experience - Campaign quality score Ucliq is fully compatible with parallel tracking and captures all required parameters without interfering with the user journey. Required parameters for tracking To correctly match clicks and conversions, Google Ads uses the following click identifiers: - gclid - wbraid - gbraid These parameters must be passed to your landing page and stored consistently. Before you start (Requirements) Make sure the following conditions are met: - Google Ads functionality is enabled for your Ucliq account - A Google-certified tracking domain is assigned to you - You have access to your Google Ads account If any of these are missing, contact your account manager before proceeding. What’s next? Once all requirements are met, follow the step-by-step setup guide to configure your Google Ads offer and campaign. Continue to Google Ads Integration Technical Setup

Last updated on Jan 23, 2026

Google Ads Technical Setup

Step 1. Create a Google Ads offer in Ucliq 1. Go to Offers > New Offer 2. Fill in the offer name 3. Select your Advertiser account 4. Set Offer type to Google Ads 5. Choose: -Offer currency -Category 6. Select a Google-certified tracking domain 7. Click Next If no tracking domains are available, contact your account manager. Step 2. Configure the landing page URL In the Link step: 1. Set your Offer landing URL (final destination page) 2. Make sure the URL: -Uses HTTPS -Is the final URL (no redirects to other domains) Click ID configuration To support parallel tracking, Google click IDs must be passed to your landing page. Recommended template: cid={gclid}--{wbraid}--{gbraid} - cid is an example parameter name - You may replace it with your own click ID parameter - The same parameter must be used on your landing page and in postbacks Step 3. Configure goals and creatives - Set your default payout goal - Add creatives (optional) that may be used in Google Ads campaigns Click Next to finish offer creation. Step 4. Activate the offer 1. Open the created offer from the Offers list 2. Change the status to Active 3. Scroll down to Landing Configuration Here you can: - Adjust landing URL and parameters - Review tracking and postback templates - Ensure macros match your landing page setup Step 5. Launch a campaign in Ucliq 1. Inside the offer, click + Add 2. Select: -Offer -Publisher -Traffic type 3. Click Launch This step generates tracking links required for Google Ads. Step 6. Configure the campaign in Google Ads 1. Create a campaign in Google Ads 2. Set the Landing URL 3. Open Campaign Settings > Campaign URL options 4. Enter: Tracking Template - from Ucliq Final URL Suffix - from Ucliq 5. Save settings These values can be copied from the Links & Creatives section in Ucliq. Step 7. Test tracking 1. Click Test in Google Ads 2. Make sure: -Landing page is found -Tracking call is successful Important: - The landing page must not redirect to another domain - Only HTTPS URLs are allowed If any questions appear, please contact your manager

Last updated on Jan 23, 2026