Everflow macros & parameters

Here's what I'd do

Useful when you're tracking multiple conversion events (installs, purchases, registrations) and your partner needs to know which type fired. If you only have one conversion event, you don't need this.

Here's what I'd do

This is the non-negotiable one. Every postback you configure in Everflow must include {transaction_id} — without it, Everflow can't match the conversion back to the original click. If a publisher's URL uses a different name like {clickid} or {tid}, that's fine — you replace their name in your Everflow postback setup with {transaction_id}.

Here's what I'd do

This one only works when an advertiser is firing a postback TO Everflow — not when Everflow is firing out to a partner. If you're setting up a Partner Postback, use {sale_amount} or {payout_amount} instead. Using {amount} in a Partner Postback is one of the most common mistakes I see — it'll return blank.

Here's what I'd do

Use this to pass the currency code to your partner alongside the payout amount. If you're sending {sale_amount}, it's good practice to send {offer_currency} too so the partner knows what currency they're receiving.

Here's what I'd do

This passes what Everflow actually paid out to the partner, in the offer's currency. Use this if your partner wants to see their commission amount rather than the sale total. If you're not sure which to use, {sale_amount} is usually what publishers ask for.

Here's what I'd do

Use this when you want to pass the sale value back to your publisher in a Partner Postback. The easy mistake — and a very common one — is using {amount} here instead. That only works on the advertiser side and will come back blank in a Partner Postback. You'll also need to flip a switch in Global Settings first (see the note below).

Here's what I'd do

When a partner sends traffic through their tracking link, they typically pass their own click ID in sub1 so they can match conversions on their side. If they need it back in the postback, include {sub1} in your Partner Postback URL. Your partner will tell you what parameter name to use in their system — for example in Voluum they'd want it as cid={sub1}.

Here's what I'd do

Works the same way as sub1 — a passthrough slot for whatever value the partner passed in their tracking link. Partners sometimes use sub2 for campaign ID, creative ID, or other values they want to see at conversion time.

Here's what I'd do

A passthrough slot for custom data from the advertiser. If you're collecting something from the advertiser's postback — like their internal order reference — you can pass it back to partners here. Requires a global setting to be visible in Partner Postbacks (see note below).

Here's what I'd do

Two-letter country code (GB, US, DE etc). Useful if your partner pays different rates by geography or needs to know where conversions are coming from.

Here's what I'd do

The user's IP address at click time. Some partners use this for fraud detection or geographic validation. Only include it if your partner specifically asks for it.

Here's what I'd do

The date and time the event happened, formatted as YYYY-MM-DD HH:MM:SS in UTC. Useful for reconciliation — lets both sides match up conversion records by time if needed.