Skip to content

Media buyer tool 3 · Postback URL Tester for Zeropark

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

The affiliate's tracker calls the Zeropark-generated postback URL, passing back the click ID that Zeropark sent via the {cid} token. Below: Zeropark's postback format and macros as published (Zeropark's own docs give the {cid} token; the literal postback URL and the {external} and {payout} tokens come from FunnelFlux's Zeropark guide.), the ways a Zeropark 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.

Zeropark's postback format

https://zp-postback.com/zppostback/ff776d65-577b-4240-af21-e11574822cca?cid={external}&payout={payout}

Where this comes from: Zeropark's own docs give the {cid} token; the literal postback URL and the {external} and {payout} tokens come from FunnelFlux's Zeropark guide.

Zeropark's click-ID macro: {cid}. Source: Tracking Conversions (Zeropark docs), Tracking Tokens (Zeropark docs), Tracking setup with Zeropark (FunnelFlux, shows literal postback) (read on November 9, 2026). Networks rename macros and some show them only inside your account; if your dashboard differs, it wins.

Zeropark macros

MacroMeaning
{cid}Zeropark token that sends the click ID; mandatory in the destination URL
{visit_cost}Cost of the visit
{campaign_id}Numeric campaign ID
{source}Source ID
{target}Target ID, sub-placement within a source

Parameter names on the receiving side

  • cid: The click ID returned to Zeropark
  • payout: Conversion payout; not obligatory if manual conversion payout is selected

How a Zeropark postback usually breaks

  1. {cid} missing from destination URL

    Zeropark calls {cid} mandatory to keep track of visits; without it no click ID is sent and the postback has nothing to match.

    Fix: Add the {cid} token to the destination URL after a parameter name your tracker reads.

  2. Missing '?' before first parameter

    The '?' sign must precede the first parameter when appending tokens.

    Fix: Check the URL starts its query string with ?.

  3. Parameter name mismatch

    Zeropark says the cid parameter must be paired with a parameter name your tracking platform recognizes.

    Fix: Use the tracker's own click ID parameter name in the postback.

  4. Manual payout vs payout parameter

    Payout parameter is only optional if manual conversion payout is selected in Zeropark.

    Fix: Either send payout or set manual payout in Zeropark.

Test your Zeropark postback

Pre-filled with an example: The postback from FunnelFlux's Zeropark guide (its sample ID) with FunnelFlux's tokens. Copy your own from Zeropark. Paste your own URL over it; the check runs in this page and fires nothing.

Not Zeropark's own macros: {external} (FunnelFlux (tracker)); {payout} (FunnelFlux (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.

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.