Adtraxo Postback Setup — Every Network Parameter Mapped

A postback is the only thing standing between you and knowing which traffic actually converts. If your Adtraxo postback setup is wrong, you're optimizing blind — the tracker shows clicks, the affiliate network shows conversions, and nobody agrees on the numbers. This guide maps every parameter for each major traffic source so you can copy the exact string, paste it into the network, and get server-to-server conversion data flowing in under ten minutes. We'll cover PropellerAds, EvaDav, RichAds, Taboola, MGID, and solo ads, plus the sub-ID structure that ties it all together.

One thing up front: postback conversion tracking and sub-ID passing are Pro features in Adtraxo. The Free plan tracks clicks and gives you per-campaign analytics, but the server-to-server loop that makes postbacks work requires Pro at $27/mo. Everything below assumes you're on Pro.

What is a postback and why does Adtraxo postback setup matter?

A postback is a server-to-server ping. When a conversion fires on the affiliate network's side, their server calls a URL on your Adtraxo tracking domain. That URL carries a click ID so Adtraxo can match the conversion back to the exact click, campaign, sub-ID, geo, and device that produced it. No cookies, no pixel loss, no attribution gaps from browser privacy settings.

Without postback setup, Adtraxo sees clicks but not conversions. You get CTR and spend, but not ROI, not EPC, not conversion rate by placement. The AI Campaign Optimizer has nothing to optimize against. Postback is the feedback loop; everything else is guesswork.

The mechanism is simple: Adtraxo generates a unique click ID for every visitor (stored in the {click_id} macro), you pass that ID to the affiliate network via a sub-ID parameter, the network stores it against the conversion, and on conversion the network fires your Adtraxo postback URL with that same click ID appended. Adtraxo matches, records, and reports.

The universal Adtraxo postback URL structure

Every Adtraxo postback URL follows the same skeleton regardless of traffic source:

https://yourdomain.com/postback?clickid={click_id}&payout={payout}&status={status}

Break it down:

• yourdomain.com — your custom tracking domain. Using a custom domain instead of the default Adtraxo subdomain keeps your links clean and avoids any domain-level blocking on picky traffic sources.
• clickid — the Adtraxo click ID, passed back from the network. This is the join key. If this is wrong, nothing matches.
• payout — the conversion value. Some networks pass a fixed value, some pass dynamic revenue. Optional but strongly recommended for ROI reporting.
• status — approved, pending, or rejected. Lets you filter out reversals so your reported ROI isn't inflated by conversions that later get clawed back.

The variable that changes per network is which macro the network uses for the click ID, and which sub-ID slot you use to carry it. That's the mapping exercise. Get the sub-ID slot right on the outbound side and the click ID macro right on the inbound side, and the loop closes.

How do you set up the outbound sub-ID in Adtraxo?

Before any network can fire a postback, it needs to receive your click ID. That happens on the outbound offer URL — the link you send traffic to. In Adtraxo, you build that link with sub-ID parameters:

https://offer.com/?sub1={click_id}&sub2={campaign_id}&sub3={source}

Adtraxo supports sub1 through sub5. A practical allocation that scales across networks:

1. sub1 — Adtraxo click ID (mandatory; this is what the postback returns)
2. sub2 — campaign ID or name (lets you audit which campaign a conversion belongs to even outside Adtraxo)
3. sub3 — traffic source or zone/placement ID
4. sub4 — creative or landing page variant
5. sub5 — geo or device tag

Not every network passes all five sub-IDs back in the postback. Some return only sub1. Check each network's postback macro list before you commit to a structure. If a network only returns one sub-ID, put the click ID there — everything else you can reconstruct inside Adtraxo from the click record.

Adtraxo postback setup by network — parameter map

Here's the mapping table. The pattern is identical across networks; only the macro names differ.

PropellerAds

PropellerAds uses {click_id} on the outbound side and returns it in the postback as {click_id}. Standard setup:

https://yourdomain.com/postback?clickid={click_id}&payout={payout}

Pass your Adtraxo click ID into PropellerAds' sub1 (or the equivalent tracking token in the campaign's postback settings). PropellerAds also supports zone and creative macros that you can fold into sub3 and sub4 for granular reporting inside Adtraxo.

EvaDav

EvaDav exposes {click_id} as the primary token and supports multiple sub-parameters. Outbound:

https://offer.com/?sub1={click_id}&sub2={campaign_id}

Postback:

https://yourdomain.com/postback?clickid={click_id}&payout={payout}

EvaDav's postback field accepts the full URL. Paste it once at the account or campaign level and confirm the test conversion lands in Adtraxo before you scale spend.

RichAds

RichAds uses {click_id} and passes it back identically. The outbound link carries your Adtraxo click ID in the first available sub-slot; the postback returns it in the clickid parameter:

https://yourdomain.com/postback?clickid={click_id}&payout={payout}&status={status}

RichAds supports status callbacks for approved and rejected conversions — use them. Filtering rejected conversions out of your Adtraxo reports is the difference between a 40% ROI and a real 22% one.

Taboola

Taboola's click ID macro is {click_id} and it's passed through the tracking URL. Because Taboola campaigns run at higher CPCs, accurate postback attribution matters more here — a single misattributed conversion skews a whole campaign's EPC. Outbound:

https://offer.com/?sub1={click_id}

Postback:

https://yourdomain.com/postback?clickid={click_id}&payout={payout}

Taboola also passes site and campaign IDs you can map to sub3 and sub4 for publisher-level reporting inside Adtraxo.

MGID

MGID uses {click_id} as well. Same structure, same postback template:

https://yourdomain.com/postback?clickid={click_id}&payout={payout}

MGID's campaign-level postback setting accepts one URL per campaign, so if you're running multiple Adtraxo campaigns against MGID, build a separate MGID campaign for each or use sub2 to disambiguate.

Solo ads

Solo ad vendors vary wildly. Some pass a click ID, most don't. If your vendor supports a tracking token, use it in sub1 and fire the standard postback. If they don't, you can't do server-to-server attribution — fall back to Adtraxo's click-level analytics and a unique tracking link per solo buy, then reconcile conversions manually against the vendor's report. It's not elegant, but it's honest. Don't fake a postback with a static click ID; you'll corrupt your conversion data.

How do you test that your Adtraxo postback setup is working?

Never launch a campaign on an untested postback. The test takes two minutes:

1. Create a test campaign in Adtraxo and copy its tracking link.
2. Open the link in a browser. Adtraxo records a click and generates a click ID.
3. Copy that click ID from the click log.
4. Manually fire the postback URL in a browser, substituting the real click ID for {click_id} and a test value for payout.
5. Refresh the Adtraxo campaign report. A conversion should appear within seconds, attributed to that click.

If no conversion appears, the problem is almost always one of three things: the click ID parameter name doesn't match what Adtraxo expects (clickid), the click ID value is empty because the network macro didn't populate, or the postback is hitting the wrong domain (http vs https, or a typo in your custom tracking domain). Check the raw request in your server logs if you have access — the query string tells you exactly what arrived.

Common Adtraxo postback setup mistakes

After you've debugged a few dozen of these, the failure modes cluster:

• Wrong click ID macro. You pasted {clickid} when the network uses {click_id}. The postback fires with a literal string and matches nothing.
• Sub-ID slot mismatch. You passed the Adtraxo click ID in sub2 but the network only returns sub1 in its postback. The click ID never comes back.
• Missing payout. Postback fires without a value, so Adtraxo logs the conversion but can't compute revenue or ROI. Always include payout.
• No status filter. Rejected conversions inflate your numbers. Include status and filter to approved.
• Testing with a static ID. Firing the postback with a hardcoded click ID "works" in testing but tells you nothing about whether the live macro populates.
• Fraud-blind scaling. A working postback on a bot-heavy source will happily report conversions from datacenter IPs and duplicate click IDs. Turn on Adtraxo's fraud detection (IP velocity, datacenter IP, bot UA, uniqueness conflict, invalid referer) before you scale, or you'll optimize toward garbage.

What to do once conversions are flowing

With postbacks live, Adtraxo's per-campaign analytics give you conversion rate, EPC, and ROI broken down by geo, device, and sub-ID. That's where the actual optimization happens — kill the placements with clicks and no conversions, scale the ones with positive ROI, and let the AI Campaign Optimizer surface patterns you'd miss manually. But none of it works if the postback loop is broken. The mapping above is the foundation; everything downstream is arithmetic.

If you're running more than two networks, standardize your sub-ID structure now. sub1 for click ID, sub2 for campaign, sub3 for source, sub4 for creative, sub5 for geo. Every network's postback template then becomes a find-and-replace of the click ID macro. One structure, six networks, zero confusion.

Frequently asked questions

Ready to close the loop? Set up your postback in Adtraxo and start attributing every conversion to the click that earned it.