Skip to main content

Click Logs & Data Verification

What are Click Logs?​

Click Logs show a detailed record of every visitor who clicked your tracking link. Each entry contains:

  • Timestamp — when the click happened
  • Click ID — unique identifier for this visit
  • IP address — visitor's IP
  • Geography — country, city, region (auto-detected)
  • Device & Browser — OS, browser type, device model, language
  • Network parameters — zone ID, source, creative, campaign
  • Custom tokens — token_1 through token_30
  • Bot flag — whether this appears to be a bot
  • Selected offer — which offer this click was routed to
  • Status — has this click converted yet?

Why Verify Click Logs?​

Before scaling a campaign, verify that:

  1. All parameters are being passed — zone ID, publisher ID, custom tokens
  2. Geography is correct — IP geolocation is working
  3. Bot detection is working — bots are being flagged
  4. Offer routing is correct — clicks go to the right offer
  5. Click IDs are unique — each click gets a different ID

How to Access Click Logs​

  1. Open your Campaign
  2. Go to the Click Log tab
  3. You'll see a table of all clicks for that campaign
  4. Click any row to see full details

Understanding Click Log Columns​

Time​

When the click arrived at Rinku.

What to check:

  • Timestamps should be in real time (no delays unless your network has lag)
  • Timestamps should be in UTC or your configured timezone

Click ID​

Unique identifier for this visit. This is critical — it's used to link conversions back to clicks.

What to check:

  • Should be different for every click
  • Should be random/unpredictable (not sequential like 1,2,3)
  • Format depends on your Rinku setup (UUID, hash, etc.)

Why it matters: Without a unique click ID, the affiliate can't send a postback that links the conversion back to the original click.

IP Address​

Visitor's IP address.

What to check:

  • Should vary for different clicks (not all the same)
  • Should be a valid IPv4/IPv6 format
  • Can be used to detect VPN or proxy users

Country / City / Region​

Auto-detected geographic location based on IP.

What to check:

  • Does it match where your traffic is coming from?
  • If you target US traffic, most should show US
  • Some IPs can't be geolocated (VPNs, proxies) — these show as "Unknown"

Device Type​

Auto-detected device category: mobile, desktop, or tablet.

What to check:

  • If buying mobile traffic, most should be "mobile"
  • If desktop, most should be "desktop"
  • Large discrepancies suggest network mislabeling

OS (Operating System)​

Detected OS: Windows, macOS, iOS, Android, Linux, etc.

What to check:

  • Mobile traffic should mostly show iOS or Android
  • Desktop should show Windows or macOS
  • If device type and OS don't match, something is wrong

Browser​

Detected browser: Chrome, Safari, Firefox, Edge, etc.

What to check:

  • Should be diverse (not 100% Chrome)
  • Mobile safari should correlate with iOS device type
  • Unusual browsers might indicate bots

Network Parameters​

Values your traffic source passes: net_pid, net_source, net_creative, net_campaign.

What to check:

  • These should match what your network promised to send
  • Should vary if you have multiple zones/creatives
  • Should match the format your network uses

Example:

  • If you set up Publisher ID as net_pid, you should see values like 123456 or zone_abc
  • If Source is net_source, you should see values like network_name or source_code

Tokens (token_1 to token_30)​

Custom parameters you configured for your traffic source.

What to check:

  • Should only have values if your network actually passes them
  • Should be consistent (e.g., if token_1 is "zone_id", all rows should have values)
  • Should vary if you have multiple token values

Example:

You configured:
  token_1 = Publisher's zone_id → should see values like "zone_100", "zone_200"
  token_2 = Publisher's sub_campaign → should see values like "summer_promo", "black_friday"

is_crawler / Bot Detection​

Boolean flag: Yes if this looks like a bot, No if it's a real user.

How it's detected:

  • User-Agent inspection (known bot signatures)
  • Behavior patterns (multiple clicks from same IP in seconds)
  • Missing JavaScript execution capability

What to check:

  • If you have high bot traffic (>10%), investigate your network source
  • If is_crawler = Yes but you expect human traffic, network filtering might be poor
  • You can filter bots out in Analytics

Selected Offer​

Which offer this click was routed to based on your rotation rules.

What to check:

  • Should match your configured routing (if no rules, should be your default offer)
  • If you have weighted distribution, offers should appear in proportion to their weights
  • If you have conditional rules, offers should match the rule conditions

Conversion Status​

Has this click converted yet?

Possible values:

  • Pending — no conversion received yet
  • Converted — postback received with valid click_id
  • Multiple Conversions — this click converted more than once

What to check:

  • After 24-48 hours, most clicks should show "Converted" or "Pending"
  • If 90% are "Pending" after days, postbacks aren't working
  • "Multiple Conversions" is normal if the offer uses multiple events (e.g. registration and deposit). If it isn't, your affiliate may be sending duplicate postbacks. Rinku does not deduplicate them

Verification Checklist​

When launching a new campaign, check:

✓ Parameter Flow​

  • Zone ID appears in net_pid column
  • Source appears in net_source column
  • Creative appears in net_creative column
  • Custom tokens have correct values
  • Click IDs are unique

✓ Geography & Device​

  • Countries match your targeting
  • Device types match what you're buying
  • Browsers look realistic (not all Chrome)
  • OS matches device type (iOS on mobile, Windows on desktop)

✓ Bot Traffic​

  • is_crawler flags aren't too high (>10% is suspicious)
  • If high bot traffic, contact your network provider

✓ Offer Routing​

  • Selected Offer matches your campaign setup
  • If you have multiple offers, they appear correctly
  • If you have routing rules, they're being applied

✓ Conversion Status​

  • After 24 hours, check if conversions are being tracked
  • If still all "Pending", postback URL may be wrong
  • Check that click_id is being passed to the affiliate

Common Issues & Solutions​

❌ No data showing up​

Causes:

  • Tracking link not being used by the network
  • Network hasn't started sending traffic yet
  • Firewall/proxy blocking clicks

Solution:

  • Verify the campaign URL is correctly placed in your network account
  • Wait 5-10 minutes for first clicks to arrive
  • Test the link manually in a browser

❌ All clicks showing same IP​

Causes:

  • Network is proxying all traffic through one server
  • Network has tracking issues

Solution:

  • Contact your network provider
  • Might indicate low-quality traffic

❌ Parameters missing (token_1, net_source, etc.)​

Causes:

  • Traffic source not configured with those parameters
  • Network not passing those values
  • Placeholder names don't match network's parameter names

Solution:

  • Go to Sources → edit your source
  • Add the missing parameters with correct names
  • Verify network documentation for parameter names

❌ All clicks going to wrong offer​

Causes:

  • Routing rules not configured correctly
  • Rule conditions not matching
  • Offer weight set to 0

Solution:

  • Review your routing rules (Campaign → Rotation)
  • Check that rule conditions match real data (e.g., if rule says "Country = US", verify US traffic exists)
  • Verify offer weights are > 0

❌ No conversions after 24+ hours​

Causes:

  • Postback URL not configured on affiliate network
  • Affiliate postback not passing click_id
  • click_id value doesn't match what Rinku expects
  • Offer's postback URL is malformed

Solution:

  • Go to Offers → select offer → copy the Postback URL
  • Verify this URL is configured in your affiliate network settings
  • Ask affiliate to send test postback
  • Check that {click_id} placeholder is in the postback URL
  • Monitor for a few more hours (some networks have delays)

Next Steps​