Skip to content

Media buyer tool 3 · Postback URL Tester for Revcontent

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

The advertiser's server or tracker calls Revcontent's conversion endpoint (GET or POST), returning the rc_uuid that Revcontent appended to the click URL. Below: Revcontent's postback format and macros as Revcontent's own docs give them, the ways a Revcontent 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.

Revcontent's postback format

https://trends.revcontent.com/api/v1/conversion.php?api_key={your_api_key}&rc_uuid={rc_uuid_value}&amount={conversion_value}

Revcontent has no click-ID macro of its own: it appends rc_uuid to your landing URL. Store that value and return it in rc_uuid=. Source: Server to Server (S2S) Conversion Tracking (read on November 9, 2026). Networks rename macros and some show them only inside your account; if your dashboard differs, it wins.

Revcontent macros

MacroMeaning
{your_api_key}Placeholder for API access key from Account Settings
{rc_uuid_value}Placeholder for the rc_uuid captured from the click
{conversion_value}Placeholder for the dollar value of the conversion
{conversion_uuid}Macro the page says can assign the rc_uuid value to an internal variable of your choosing

Parameter names on the receiving side

  • api_key: Required; API access key
  • rc_uuid: Required; unique ID of the user who clicked
  • amount: Required; dollar value of each unique conversion, non-zero integer
  • user_ip: Optional; IP of the clicking user
  • user_agent: Optional; user agent of the clicking user

How a Revcontent postback usually breaks

  1. Missing or zero amount

    amount is required and must be a non-zero integer, so payout 0 or decimals-only values risk a rejected conversion.

    Fix: Send a non-zero integer dollar amount.

  2. Pixel and S2S together

    Revcontent warns using both reports duplicate conversions.

    Fix: Use only one of pixel or S2S.

  3. rc_uuid lost on the landing page

    Revcontent appends rc_uuid to the destination URL; if redirects or the tracker drop it, the postback has no ID to return.

    Fix: Capture rc_uuid at landing and store it with the click.

  4. Missing api_key

    api_key is a required parameter found in Account Settings.

    Fix: Add the key from Account Settings.

Test your Revcontent postback

Pre-filled with an example: Revcontent's documented postback with example tracker tokens. The API key is left out here; add your own in your tracker, never on a web page. Paste your own URL over it; the check runs in this page and fires nothing.

Not Revcontent's own macros: {clickid} (your tracker (example token)); {payout} (your tracker (example token)).

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.