Skip to content

Media buyer tool 3 · Postback URL Tester for TrafficJunky

Test your TrafficJunky postback URL before the next conversion goes missing.

The affiliate's tracker calls TrafficJunky's conversion URL when a conversion happens, returning the click ID that TrafficJunky passed as {ACLID}. Below: TrafficJunky's postback format and macros as published (TrafficJunky publishes no public postback docs; the format and tokens come from Voluum's TrafficJunky guide.), the ways a TrafficJunky postback usually breaks, and the tester, pre-filled with an example of the postback your tracker fires back to the traffic source. Edit it to match yours and run the check.

Nothing you enter leaves your browser.

TrafficJunky's postback format

https://ads.trafficjunky.net/ct?a=1000539512&member_id=1002392921&cb=[RANDOM_NUMBER]&cti=[TRANSACTION_UNIQ_ID]&ctv=1.00&ctd=[TRANSACTION_DESCRIPTION]&aclid=[ACLID]

Where this comes from: TrafficJunky publishes no public postback docs; the format and tokens come from Voluum's TrafficJunky guide.

TrafficJunky's click-ID macro: [ACLID]. Source: TrafficJunky as a traffic source (Voluum docs) (read on November 9, 2026). Networks rename macros and some show them only inside your account; if your dashboard differs, it wins.

TrafficJunky macros

MacroMeaning
[ACLID]Click-ID slot in TrafficJunky's postback; Voluum's guide replaces it with {externalid}
[RANDOM_NUMBER]Left in place by Voluum's guide; the guide doesn't say what fills it
[TRANSACTION_UNIQ_ID]Left in place by Voluum's guide; the guide doesn't say what fills it
[TRANSACTION_DESCRIPTION]Left in place by Voluum's guide; the guide doesn't say what fills it

Parameter names on the receiving side

  • a: account-specific value in the example URL
  • member_id: account-specific value in the example URL
  • cb: random number placeholder
  • cti: transaction unique ID
  • ctv: conversion value (1.00 in the example)
  • ctd: transaction description
  • aclid: the TrafficJunky click ID

How a TrafficJunky postback usually breaks

  1. [ACLID] left unreplaced

    Voluum's guide replaces [ACLID] with the tracker token ({externalid} in Voluum); a literal [ACLID] cannot be matched to a click.

    Fix: Replace [ACLID] with your tracker's stored-click-ID token.

  2. Placeholders left literal

    [RANDOM_NUMBER], [TRANSACTION_UNIQ_ID] and [TRANSACTION_DESCRIPTION] are placeholders in the example URL.

    Fix: Fill them with real values or tracker tokens.

  3. Account IDs copied from the example

    a and member_id in the example are account-specific.

    Fix: Use the postback URL from your own TrafficJunky account.

  4. Click ID never stored

    The tracker must receive TrafficJunky's {ACLID} on the click, otherwise {externalid} is empty at postback time.

    Fix: Include {ACLID} in the campaign URL parameter the tracker stores as external ID.

Test your TrafficJunky postback

Pre-filled with an example: The postback exactly as Voluum's TrafficJunky guide prints it, with Voluum's {externalid} in aclid. The guide leaves the other bracketed values unexplained; ask TrafficJunky before relying on them. Paste your own URL over it; the check runs in this page and fires nothing.

Not TrafficJunky's own macros: {externalid} (Voluum (tracker)).

Your network's click-ID macroThe macro the network fills with the click ID you sent it. It also tells the tester which syntax the network uses.

Want me to trace one real campaign?

This tool checks the postback URL and offer link you pasted from what you typed. It can't see your ad accounts, tracker, network or live traffic. If the result shows gaps, I'll look at one real campaign for free: I trace it from ad click to payout and back, and within 48 hours I send you a written report on where money or data leaks silently, the fix for each, and the tests that prove it's fixed.

In the review I fire a test conversion end to end on one real campaign and check it lands once, with the right payout, in your tracker and in your traffic source. You get the fix for every place it doesn't.

Request the free spend-path review (opens Cal.com in a new tab)

Shilpa Goel, [email protected]

This is an engineering checklist, not a security audit, legal, compliance or investment advice.

Not affiliated with or endorsed by Meta, Google, TikTok or any network or tracker named here.