Check these common causes:

• NID is placeholder: Make sure &nid= contains your actual Network ID number, not "XXX" or other placeholder text
• Transaction ID expired: Click data is purged after 90 days. If no conversion occurred within 90 days of the click, the TID is invalid
• Verification token missing: If the Advertiser enforces a verification token, include &verification_token=YOUR_TOKEN
• Offer status inactive: Postbacks fail if the Offer Status is not "Active" at the time of conversion
• Whitelist blocking: If "Enforce Advertiser Whitelist" is ON, conversions from non-approved IPs/domains are rejected

Diagnose with Investigator: Use the Investigator Tool with the Transaction ID to trace why the conversion was rejected.

For Revenue Per Sale (RPS) or Cost Per Sale (CPS) offers, Everflow needs the sale amount to calculate dynamic revenue and payout.

• Missing amount parameter: Add &amount=99.99 to your postback URL
• Currency mismatch: If the amount is in a different currency than the Offer default, add ¤cy=EUR (or appropriate code)
• Amount = 0 passed: Check that the Advertiser's system is actually passing the sale value, not a literal zero

Pro tip: Set Revenue to 100% in Offer settings to capture the full sale amount, then configure Payout as a separate percentage or flat fee.

Duplicates occur when the same conversion signal fires multiple times (e.g., user refreshing a thank-you page).

• Disable duplicate conversions: In Offer settings, turn OFF "Allow Duplicate Conversions"
• Implement deduplication: Ask the Advertiser to implement server-side deduplication to prevent multiple postback fires
• Use order_id: Pass a unique &order_id= value — Everflow can use this for deduplication logic

Important: Everflow fires Partner postbacks once — at the moment the conversion is initially received.

• "One-shot" behavior: If an Advertiser updates the payable amount hours or days later, the system does NOT automatically re-fire a postback to the Partner
• Check Partner postback URL: Verify the Partner has correctly configured their postback endpoint in their system
• Test first: Use the postback testing workflow before going live

For late updates: If you need to notify Partners of amount changes, you'll need to manually trigger notifications or use the API.

Everflow only captures metadata passed through recognized parameters.

• Custom parameter names ignored: Parameters like &product_category=shirts or &lead_score=high are NOT captured
• Use ADV fields: Map your custom data to &adv1= through &adv5= — these ARE captured and appear in reports
• Example: Instead of &product_type=premium, use &adv1=premium

Reporting: ADV1-5 values appear in the Flex Report and can be used for filtering and segmentation.

If you're tracking milestone events but everything shows as "Base Conversion," you're missing event parameters.

• Event ID omitted: Without &event_id= or &adv_event_id=, ALL conversions default to Base (ID = 0)
• The postback won't fail: It successfully records — just to the wrong event! This causes misreported data and incorrect payouts
• Use the right parameter: adv_event_id for global Advertiser-Level Events across multiple Offers, or event_id for Offer-specific milestone events

Find Event IDs: Offers → [Offer] → Events tab, or Advertisers → [Advertiser] → Events tab

This error means Everflow couldn't match the Transaction ID to a valid click.

• TID parameter mismatch: The parameter name in your Default Landing Page (e.g., ?s1=) doesn't match what the Advertiser's system expects — they never captured/stored the TID
• TID not returned: Advertiser's postback is passing an empty or placeholder value instead of the actual Transaction ID
• 90-day expiration: The click occurred more than 90 days ago with no prior conversion, so the TID was purged
• Wrong bracket format: Everflow requires curly brackets {transaction_id} — square brackets [transaction_id] or parentheses won't work

Prevention: Always coordinate with the Advertiser on the exact parameter name before going live.

The Advertiser has enabled token-based authentication, and the postback is missing or has an incorrect token.

• Where to find the token: Advertisers → [Advertiser] → Edit → Advanced Options → Additional Information card
• Add to postback: Append &verification_token=YOUR_TOKEN_HERE to the URL
• Max 50 characters: The token can be up to 50 characters long
• Case sensitive: The token must match exactly — including capitalization

Note: Once enabled on an Advertiser, the token is required for ALL postbacks to that Advertiser's Offers.