Setting Up Server-to-Server Tracking

Why Use Server-to-Server Tracking?

Server-to-Server tracking allows you to send conversion data directly back to your tracking platforms or ad platforms for better campaign optimization. This automated data flow helps you scale successful campaigns, identify profitable traffic sources, and make data-driven decisions to improve your ROI — all without manual reporting or guesswork.

Introduction

Server-to-Server tracking is a postback system that automatically sends conversion data (like click IDs, commission amounts, and conversion status) from the affiliate network to your external tracking platform. This is essential for affiliates running traffic campaigns who need accurate conversion tracking.

Setting Up Server-to-Server Tracking

Step 1: Access Account Settings

1. Log in to your account
2. Navigate to My Account → Account Details
3. Go to Affiliate Settings
4. Click Manage next to “Server to Server Postback”

Step 2: Configure Your Postback URL Create your postback URL using these essential parameters:

Required Parameters:

• Click ID: clickid=TID (26 character limit)
• Commission Amount: sub=affiliate_amount
• Status (optional): status=status (useful for RevShare campaigns)

Example Postback URL:
https://your-tracker.com/postback?clickid=TID&sub=affiliate_amount&status=status

Step 3: Update Your Affiliate Links Add the click ID parameter to your affiliate links:

https://offer-link.com/?affiliate_id=A1&TID=[CLICK_ID]

Important Notes:

• This is account-wide — set it once and it works for all campaigns
• For Click IDs longer than 26 characters, use Sub IDs (512 character limit)
• CPA campaigns don’t fire refund postbacks
• RevShare campaigns can track refunds and status changes

Common Tracking Platforms:

• RedTrack
• Voluum
• ClickFlare
• BeMob
• Any platform supporting postback URLs

Need Help?

• Check the support documentation for detailed setup guides
• Use live chat for technical assistance (usually resolved in 2 minutes)
• Contact the Support team who can help with platform-specific configurations