Skip to content

Media buyer tool 3 · Postback URL Tester for Everflow

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

Everflow calls the partner's server endpoint (the Partner Postback) when a conversion happens, replacing its curly-bracket macros with real values. Below: Everflow's postback format and macros as Everflow's own docs give them, the ways a Everflow postback usually breaks, and the tester, pre-filled with an example of the postback the platform fires to your tracker. Edit it to match yours and run the check.

Nothing you enter leaves your browser.

Everflow's postback format

Partner pastes their own server endpoint URL with parameters built from Everflow macros (docs give no full template: 'Paste your server endpoint URL with the appropriate parameters'). Macros are always in curly brackets.

Everflow's click-ID macro: {transaction_id}. Source: Managing Postbacks as a Partner, Your guide to parameters & macros (read on November 9, 2026). Networks rename macros and some show them only inside your account; if your dashboard differs, it wins.

Everflow macros

MacroMeaning
{transaction_id}Unique ID associated to the transaction which serves as the click ID, generated by Everflow
{sale_amount}Sale amount associated with the order (use this rather than {amount} in Partner Postbacks)
{payout_amount}Amount paid out to a Partner for a Conversion or Event, in offer currency
{offer_id}Offer ID
{event_id}Event ID
{conversion_id}Conversion ID
{sub1}Partner sub parameter 1 ({sub1} to {sub10})
{adv1}Advertiser parameter 1 ({adv1} to {adv10}), only if visibility settings allow
{order_id}Order ID
{source_id}Source ID

Parameter names on the receiving side

  • transaction_id: Everflow click/transaction ID returned so the partner's tracker can match the click
  • payout: Partner payout, filled from {payout_amount}
  • amount: Sale amount, filled from {sale_amount}
  • sub1: Partner sub value passed back

How a Everflow postback usually breaks

  1. Wrong bracket type

    Everflow macros must use curly brackets; square brackets and parentheses are not substituted, so the literal text reaches your tracker.

    Fix: Use {transaction_id} style braces exactly.

  2. {amount} used in a partner postback

    Use {sale_amount} rather than {amount} in Partner Postbacks ({amount} belongs to advertiser postbacks), so the sale value arrives empty or literal.

    Fix: Use {sale_amount} for sale value and {payout_amount} for payout.

  3. Visibility-gated macros arrive blank

    {adv1}-{adv10} and {sale_amount} are only available to partners when the network admin's visibility settings allow it.

    Fix: Ask the network to enable macro visibility or use macros that are visible.

  4. Click ID not the one you stored

    {transaction_id} is generated by Everflow and serves as the click ID; if your tracker expects its own click ID it will not match unless you passed it in a sub parameter and return {sub1}.

    Fix: Either store Everflow's transaction_id at click time or pass your click ID in sub1 on the tracking link and return {sub1}.

Test your Everflow postback

Pre-filled with an example: Everflow's macros in an example tracker postback (track.example.com stands for your tracker). Paste your own URL over it; the check runs in this page and fires nothing.

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.