Routy

Tracking Setup Guide

This guide covers everything you need to configure tracking in Routy — from basic click tracking to advanced server-to-server postbacks.

Understanding the Tracking Flow

Routy's tracking works in three stages:

  1. Click — User clicks your affiliate link
  2. Redirect — Routy logs the click and redirects to the merchant
  3. Conversion — Merchant fires a postback when the user converts

Important: All tracking requires a properly configured tracking profile. Without one, clicks will redirect but won't be logged.

Tracking Profiles

Creating a Profile

Navigate to Tracking → Tracking Profiles and click Add Profile.

Required fields:

Field Description Example
Name Descriptive name "Main Tracker"
Domain Your tracking domain track.example.com
Redirect Type How users are redirected 302 (recommended)
Click Expiry Days until click expires 30 days

Redirect Types Explained

301 — Permanent Redirect

  • Best for SEO-focused campaigns
  • Browsers cache the redirect
  • Not recommended for A/B testing

302 — Temporary Redirect (Recommended)

  • Most common for affiliate tracking
  • No browser caching
  • Works with all traffic sources

JavaScript Redirect

  • Client-side redirect via window.location
  • Allows firing pixels before redirect
  • May not work with all ad platforms

Advanced: Server-to-Server Postbacks

Setting Up S2S Tracking

Server-to-server (S2S) postbacks are the most reliable conversion tracking method.

POST https://api.routy.app/v1/postback
Content-Type: application/json

{
  "click_id": "abc123",
  "event": "conversion",
  "payout": 25.00,
  "currency": "USD",
  "order_id": "ORD-789",
  "status": "approved"
}

Response Codes

Code Meaning Action
200 Success Conversion recorded
400 Bad request Check required fields
404 Click not found Verify click_id is valid
409 Duplicate Conversion already exists
429 Rate limited Reduce request frequency

Conversion Events

Routy supports multiple conversion event types:

  • Registration — User signs up
  • FTD — First-time deposit
  • Deposit — Subsequent deposits
  • Qualified — User meets qualification criteria
  • Revenue Share — Ongoing revenue events

Event Configuration

Each event type can have different:

  • Commission rates (CPA, RevShare, Hybrid)
  • Approval workflows (auto-approve, manual review)
  • Payout schedules

Debugging

Common Issues

Clicks not tracking:

  • Verify your tracking domain DNS is configured
  • Check that the tracking profile is active
  • Test with curl -v https://track.yourdomain.com/click?test=1

Postbacks failing:

  • Check the Events page for error details
  • Verify the postback URL is accessible from Routy's servers
  • Ensure click_id matches an existing click

Pro tip: Use the Event Log to trace a click through the entire conversion funnel.