Home All about tracking

All about tracking

Master tracking in UCLIQ with postbacks, tracking links, and key parameters. Ensure data accuracy for optimized advertiser and publisher interactions.
By Azema
• 5 articles

Basic Tracking Concepts

Tracking is at the core of UCLIQ, allowing you to monitor traffic, attribute conversions, and analyze performance. Tracking links record user actions, such as clicks and conversions, by passing data between publishers, UCLIQ, and advertisers. The data collected ensures accurate attribution and performance analysis. Key Components of Tracking Tracking Links A tracking link is a unique URL generated for publishers to send traffic to offers. It contains parameters that capture data like the click ID, source, and user details. Example tracking link: https://yourtrackingdomain.com/c/offer_id?click_id=12345&subsource=affiliate Click ID A unique identifier assigned to every click. It links clicks to subsequent conversions. Postbacks Postbacks are URLs used to send conversion data back to UCLIQ from the advertiser. They ensure accurate attribution. Example postback URL: https://track.ucliq.com/pb/securekey?click_id={click_id}&sum={sum} How Tracking Works 1. Publisher Sends Traffic A user clicks on a tracking link and is redirected to the advertiser's landing page. 2. Data Captured The link records parameters like click ID, traffic source, and geography and this information appears in UCLIQ. 3. Conversion Reported User is now on the advertiser’s page and makes an action. The advertiser sends a postback to UCLIQ, including the click ID and other details of this action = conversion. 4. Attribution UCLIQ matches the conversion to the original click and attributes it to the correct publisher. Parameters in Tracking Links Tracking links often include the following: - click_id: Unique identifier for the click (mandatory for tracking conversions). - subsource: Affiliate or sub-publisher ID. - country: Geo-location of the traffic. - device: Type of device used (e.g., mobile, desktop). Testing Tracking 1. Generate a tracking link in the Publisher Portal. 2. Open the link in a browser and confirm redirection to the advertiser’s page. 3. Simulate a conversion and ensure it appears in the UCLIQ dashboard. Tips - Always include click_id in tracking links for accurate conversion attribution. - Use clear parameters to segment traffic effectively. - Test tracking links regularly to ensure they work as expected.

Last updated on May 11, 2025

Server Postback S2S Integration with Advertisers

S2S (Server-to-Server) integration for advertisers is a powerful solution for tracking conversions and ensuring accurate attribution without relying on browser cookies. This method involves direct communication between servers, providing a more reliable and precise way to report conversions back to UCLIQ, especially in environments where cookies or ad blockers might interfere with traditional tracking methods. What is Advertiser S2S Integration? Advertiser S2S integration involves two key components: 1. Tracking Links: These are the URLs used by publishers to generate traffic. The tracking link contains a click_id, a unique identifier that allows UCLIQ to track the click through the entire conversion process. 2. Postbacks: Once a conversion occurs (e.g., a sale, lead, or sign-up), the advertiser sends a postback to UCLIQ. This postback includes the click_id and conversion details, allowing UCLIQ to match the conversion with the corresponding click and attribute it to the right publisher. By using server-to-server communication, the system eliminates the risk of data loss caused by ad blockers or cookie restrictions, ensuring that the conversion tracking remains accurate and consistent. How Advertiser S2S Integration Works 1. Tracking Link is Generated The publisher generates a tracking link that includes a unique click_id. This link is shared with users, and when they click it, the click_id is passed along to the advertiser’s website. 2. User Clicks the Link The user clicks on the ad or tracking link and is redirected to the advertiser’s offer page. The click_id that was included in the tracking link is passed to the advertiser’s website, ensuring that the click is recorded. 3. User Converts on the Advertiser’s Website The user completes the desired action (purchase, sign-up, etc.) on the advertiser's website. At this point, a conversion is registered. 4. Advertiser Sends Postback to UCLIQ After the conversion, the advertiser sends a postback to UCLIQ with the click_id and additional conversion details (e.g., the value of the conversion or the type of conversion). The postback URL is set up by the advertiser and contains the necessary parameters to transmit this data. 5. UCLIQ Matches the Conversion UCLIQ receives the postback and matches the click_id with the original click. This allows UCLIQ to attribute the conversion to the correct publisher, ensuring accurate reporting and commission tracking. 6. Conversion is Recorded in UCLIQ Once the conversion is attributed to the correct publisher, the data is recorded in UCLIQ’s system, and the publisher is credited for the conversion. This information is visible in the Manager Portal and reports. Why Use Advertiser S2S Integration? - Reliable Conversion Tracking: S2S integration ensures that conversions are tracked directly between servers, eliminating issues caused by ad blockers, browser cookies, or cross-domain tracking problems. - Accurate Attribution: By passing the click_id through the entire process, advertisers can ensure that each conversion is correctly attributed to the publisher who generated the click, preventing fraud and ensuring fair payout distribution. - Improved Performance Marketing: For advertisers in affiliate networks, S2S is an essential tool for reliable conversion tracking, providing full transparency and better control over reporting and campaign performance. - Better Reporting and Optimization: Advertisers benefit from precise, real-time conversion tracking, which enables them to optimize campaigns more effectively based on accurate data. By implementing Advertiser S2S integration, advertisers can ensure reliable and accurate tracking of conversions, improving their performance marketing efforts and strengthening their partnerships with publishers.

Last updated on May 11, 2025

Server Postback S2S Integration with Publishers

S2S (Server-to-Server) integration for publishers is a robust and efficient way to track conversions and attribute them to the correct source without relying on browser cookies. By directly transmitting conversion data between servers, this method ensures accurate tracking, even in environments with ad blockers or cookie restrictions. What is Publisher S2S Integration? Publisher S2S integration involves two primary components: 1. Tracking Links: These are the unique URLs that publishers use to track clicks. The tracking link includes a click_id—a unique identifier that connects the user’s click with their eventual conversion. The click_id is passed to the advertiser’s system to link the traffic to the conversion. 2. Postbacks: These are the URLs that the advertiser sends back to UCLIQ to report conversions. The postback URL includes conversion details, including the click_id, and this allows UCLIQ to attribute the conversion to the publisher who drove the initial click. By using this server-to-server communication, the system bypasses common issues that arise from browser-based tracking, like ad blockers or cookie restrictions, making it an essential tool for performance marketers who need reliable tracking. How Publisher S2S Integration Works 1. Publisher Generates a Tracking Link The publisher generates a unique tracking link that contains a click_id. This click_id is used to identify the click in the system. When the user clicks on the ad, UCLIQ generates and stores this unique identifier. 2. Tracking Link is Clicked The user clicks the tracking link, which redirects them to the advertiser’s landing page or offer. The click_id travels along with the user to the advertiser's website, ensuring the click is recorded. 3. Conversion on Advertiser’s Website The user completes the desired action on the advertiser’s website—whether that’s a purchase, sign-up, or another predefined conversion event. 4. Advertiser Sends Postback to UCLIQ After the conversion happens, the advertiser sends a postback to UCLIQ. This postback contains the click_id that was passed from the publisher’s tracking link, along with conversion details (e.g., the amount or type of conversion). 5. UCLIQ Matches the Conversion UCLIQ receives the postback from the advertiser, matches the click_id in the postback to the original click, and attributes the conversion to the publisher who drove the initial click. 6. Publisher Sees the Conversion Once the conversion is matched and attributed, the publisher is credited for the conversion and can see the result in their performance metrics on the Publisher Portal. Why Use Publisher S2S Integration? - Accurate Attribution: S2S eliminates the risk of data loss due to issues like cookie blocking or cross-domain tracking problems. It ensures that every conversion is accurately attributed to the publisher who generated the click. - Reliability: Unlike traditional browser-based tracking methods, which can be disrupted by browser settings, S2S provides a more reliable and consistent way to track and attribute conversions. - Performance Marketing: For publishers in affiliate or performance marketing networks, S2S integration is critical. It helps track the exact source of conversions and provides transparency and control over reporting. By setting up S2S integration, publishers ensure they are working with a robust and effective system that accurately tracks their performance and optimizes the conversion process, making it a key part of their success in digital marketing.

Last updated on May 11, 2025

Set up S2S Integration with Advertisers

Step 1: Configuring the tracking link Go to the Offers > Specific offer > Links and add the advertiser tracking link. It will contain parameters to which you need to add matching macros (e.g., {click_id}, {source}). Example:https://advertiser.com/?click_id={click_id}&affiliate={publisher_id} Step 2: Setting up the advertiser postback Go to the Offers > Specific offers > find Postback URL Template in the general widget: Copy the unique postback URL for the offer: Example: https://track.ucliq.com/pb/securekey?click_id={click_id}&sum={sum}&goal={goal} Provide this URL to the advertiser and let them know they should add their own macros to our parameters in the link like  click_id The postback link can include optional parameters like sum (conversion value) and goal (conversion type) if needed. The advertiser must add the macros to these parameters too. Step 3: Testing the setup 1. Generate a Test Click Use the tracking link mentioned in Step 1. Paste the link in your browser’s address bar and you will see the click ID 2. Test the Postback Use the postback URL from Step 2 and test the data transmission by adding a test value for the sum and click_id parameters. Copy the modified postback URL and paste it into your browser’s address bar. The server should respond with "OK" (this means the postback was received and processed). If the response is not "OK," check the URL and parameters for errors. 3. Check the Conversion After testing the link, the conversion should appear in the Conversions section of the Admin Panel. This confirms that the postback is working correctly. Common parameters used in postbacks include: click_id: Unique identifier for the click (mandatory). sum: Conversion value (optional). goal: Conversion type or goal alias (optional). tid: Transaction ID for deduplication (optional). Tips - Ensure macros consistency and double-check that click_id and other macros are supported by the advertiser’s system. - Use secure postbacks and avoid sharing postback URLs publicly to prevent misuse. - Conduct periodic tests to ensure the integration remains functional. - Use UCLIQ’s analytics tools to verify conversions and performance.

Last updated on May 11, 2025

Set up S2S Integration with Publishers

Step 1: set up tracking link for publisher After launching the offer, the publisher can find it in the Publisher Panel > Offers. They need to launch the offer in order to get the tracking link for further usage. It has to include unique identifiers like ext_click_id to track conversions. Common parameters to use include: subsource: Identifies the affiliate ID or the traffic source. track: Typically used for internal tracking (e.g., UTM tags). ext_click_id: Publisher's unique click ID, which is essential for postback attribution. Step 2: configure publisher postback URL The postback URL is the endpoint where conversion data will be sent from UCLIQ to the publisher’s system. In this step, configure the correct postback link that transmits conversion information when the publisher makes a payment. For S2S postback integration, make sure the following parameters are included in the postback URL: Click_id: A unique identifier for the click. Goal: Alias of the specific goal set for the offer (only for goals). Sum: The amount of the conversion, based on the payment method used (e.g., CPS, CPL). It can be set up in the Publisher Panel > Offers > Live >Postbacks: Or in the Admin Panel > Publishers > Postbacks > Manage > Edit specific Publisher: Replace placeholders like {sum} and {click_id} with the appropriate dynamic variables used by the advertiser. These parameters must be passed correctly to ensure accurate data tracking. Step 3: Test Publisher Postback Before going live, it’s crucial to test the postback configuration. 1. Generate a Test Click Use the tracking link mentioned in Step 1. Click the link and ensure the click ID is passed through. 2. Test the Postback Use the postback URL from Step 2 and test the data transmission by adding a test value for the sum and click_id parameters. Copy the modified postback URL and paste it into your browser’s address bar. Hit Enter to execute the request. 3. Check the Conversion After testing the link, the conversion should appear in the Conversions section of the Admin Panel. This confirms that the postback is working correctly.

Last updated on May 11, 2025