Postbacks

A postback is the message that closes the loop. When someone you referred converts on Secrets AI, Everflow can fire a server-to-server (S2S) request back to your tracker so it knows exactly which click turned into revenue. Without it you can see clicks going out, but not which ones paid off.

What a postback does

When a referred user subscribes, Everflow logs the conversion against your account. If a postback is configured, Everflow then sends a request to a URL you control, almost always your tracker, carrying the Click ID you passed in sub1 and the payout amount. It can also return any sub2 to sub5 values you set on the link. Your tracker matches the Click ID to its click record and credits the campaign, creative or placement that drove it.

For paid traffic this is not optional. Ad platforms optimize off the conversion signals they receive: no signal, no smart bidding. For organic and SEO traffic it is lower urgency, but still worth having for your own cohort and creative-level reporting.

The loop, step by step

1. A visitor clicks your link. Your tracker (RedTrack, Voluum, Binom, BeMob, Keitaro, FunnelFlux or similar) generates a unique Click ID.
2. That Click ID rides along as sub1 on your Secrets tracking link.
3. The user subscribes. Everflow logs the conversion with sub1 intact.
4. Everflow fires your postback URL, swapping real values in for the macros you included.
5. Your tracker matches the Click ID and credits the right source. From there it can forward the conversion to Google, Meta, TikTok or Reddit through their Conversions APIs.

Set it up in Everflow

Once you have a destination URL, this takes about two minutes.

1. Open Postbacks from the menu. The first time, the list is empty.
2. Click + Postback to open the form.
3. Pick the tracking type. Conversion is for subscriptions, which covers the large majority of payouts across the PPS and Revshare offers. Event is a signup; you can add a postback for that too.
4. Choose the scope. Global fires on every Secrets conversion, which is right if you run one tracker for everything. Specific ties the postback to a single offer, useful when, for example, your Meta traffic needs its own endpoint.
5. Pick Postback (server-to-server) as the delivery method over HTML Pixel. Pixels depend on the visitor's browser loading them, and ad blockers eat a meaningful share. S2S has no such dependency.
6. Paste your postback URL with the macro placeholders intact. Do not URL-encode the curly braces; Everflow handles that when it fires.
7. Save, then test. An organic click that converts, or a test conversion fired by your affiliate manager, both work. Check Reporting → Postback to confirm it fired and got a 2xx response. The View Debug Info action on any row shows the exact request and response.

Before you set it live

Everflow auto-deactivates a postback after 10 consecutive failures within 72 hours. This applies to postback delivery only, not pixels. A failure is no response or an error code; anything in the 2xx range, including 204 No Content, counts as a pass. The most common cause of an unexpected deactivation is a Global postback expecting a parameter only one traffic source sends, such as a field that is empty on everything except Meta traffic. If that is the pattern, switch it from Global to Specific.

The generic S2S template

The simplest setup is a GET request to an endpoint you control: your own server, a database, or any tracker that accepts GET requests.

https://your-tracker.example.com/conversion?click_id={sub1}&payout={payout}&offer_id={offer_id}&tx_id={transaction_id}

Macro	What it returns
{sub1}	The Click ID you captured at click time
{payout_amount}	Your payout on this conversion, in USD
{transaction_id}	Everflow's internal ID for the conversion record
{offer_id}	Which Secrets offer the conversion belongs to (PPS T1, PPS WW, Revshare)
{sub2} to {sub5}	Your other sub-parameters, exactly as set on the link

Macro names are case-sensitive and must match Everflow's reference exactly. Check the postback documentation in your dashboard before saving if you are unsure of a spelling.

Running direct on one platform, no tracker

These platforms do not accept a plain GET postback. Each needs authenticated POST requests through its own Conversions API.

• Google Ads: capture gclid into sub1. Conversions go back through an Offline Conversions action, via your tracker's integration (RedTrack, Voluum and AnyTrack handle this) or a manual CSV upload in Google Ads.
• Meta (Facebook and Instagram): capture fbclid into sub1. Post-iOS 14, Conversions API (CAPI) is the only option worth setting up, through your tracker or Business Manager → Events Manager.
• TikTok Ads: capture ttclid into sub1. Report through TikTok's Events API, via your tracker or TikTok Ads Manager → Assets → Events. Needs an access token.
• Reddit Ads: capture rdt_cid into sub1. Same pattern: POST with an access token, through your tracker or Reddit Ads Manager → Conversions.

The honest recommendation is to put a tracker in the middle. RedTrack, Voluum, Binom, BeMob and AnyTrack handle the Conversions API plumbing, and you maintain one generic S2S postback instead of four integrations.

When it is not firing: five usual suspects

1. The macro comes through empty. The Click ID was never captured. If sub1 is blank on the click in Everflow, fix the link, not the postback.
2. The macro name is wrong. {Sub1}, {sub_1} and {sub-1} will not substitute; your destination gets the literal placeholder.
3. The destination rejects the request. A 400 usually means a missing parameter, a mangled URL, a destination that wants POST, or an expired auth token.
4. It was auto-deactivated. Fix the cause, confirm the destination returns 200 OK, then re-enable it.
5. Protocol mismatch. An HTTPS-only destination given an HTTP URL. Default to HTTPS.

Avoid the mistakes that eat the most support time: setting up postbacks before the link itself is verified, trying to GET-postback straight into Meta, Google or TikTok, and running more than one postback on the same conversion event. One destination per event is enough.

Stuck? Send your affiliate manager the postback URL, the destination platform and the response code Everflow logs in the Postback report.

Next steps

• Plan your launch in Your first week, the next step.
• Testing detail: How do I test a postback?.
• Troubleshooting: Why is my postback not firing?.
• Not approved yet? Apply to the Secrets AI affiliate program.