Conversions Error Code Reference Guide

Conversion errors prevent your conversions from being properly recorded or attributed. Each error code indicates a specific problem - from missing transaction IDs to security blocks to configuration issues.

This guide provides three interactive tools to help you diagnose and fix conversion errors faster:

Error Code Lookup: Search any error code to see causes and step-by-step fixes
Troubleshooting Flowchart: Answer a few questions to find your exact solution
Diagnostic Generator: Create formatted support tickets with all required details

Most Common Mistake Users often say "my conversions aren't tracking" without checking if there's an error code explaining why. Always check the Conversion Report → Error Code column first. Error codes tell you exactly what's wrong and how to fix it.

Interactive Error Lookup

Search by error code number or message to instantly see causes and fixes. Click any card to flip and see detailed troubleshooting steps.

🔍 Error Code Lookup

Search by error code number (e.g., "13") or message (e.g., "invalid click") to find causes and fixes

🔍

No errors found

Try a different search term or category

Troubleshooting Flowchart

Not sure which error code you have? Follow the interactive decision tree to find your exact problem and solution path.

🗺️ Troubleshooting Flowchart

Answer a few questions to find the exact fix for your conversion error

Where did you first notice the conversion error?

📊

Conversion Report

Error appears in the main Conversion Report

🔍

Debug Info / Logs

Found error in Advertiser Postback Report or Debug Info

❌

No Conversion at All

Conversion never appeared in system

What error code range are you seeing?

🚫

Error 1-5

Throttle, Whitelist, Caps, Lookback

🔗

Error 6-11

Protocol, Domain, Network issues

🎯

Error 12-14

Transaction ID, Click, Offer mismatch

⚙️

Error 15-20

Offer setup, status, expiration

🔐

Error 21-24

Security tokens, fraud, device matching

🎛️

Error 25-27

Event mismatch, Postback Controls, Pass Through

What HTTP response code are you seeing?

📭

204 No Content

Postback accepted but no conversion appears

⚠️

400 Bad Request

Malformed URL or wrong parameters

🔒

403 Forbidden / 401 Unauthorized

Access denied or authentication failure

💥

500 Server Error

Partner's server issue

What tracking method are you using?

📝

JavaScript SDK

Using ClickScript on landing page

🔄

Server-to-Server (S2S)

Advertiser fires postback from their server

📧

Email Attribution

Clickless / Coupon code tracking

✓ Fix: Caps, Whitelist & Lookback Issues

Error 1 (Throttled): Check Offers → Postback Controls → Throttle must be 0-100%
Error 2/3 (Whitelist): Advertisers → Settings → Whitelist → Add advertiser's domain/IP (check Advertiser Postback Report for actual source)
Error 4 (Over Caps): Offers → General Tab → Caps → Increase limits OR approve pending conversions manually
Error 5/20 (Lookback): Offers → Attribution Tab → Adjust Click-to-Conversion time window (default: 30 days)

✓ Fix: Protocol, Domain & Network Configuration

Error 6 (Non-HTTPS): Update advertiser postback URL to https:// OR disable 'Require HTTPS' in Offers → General Tab
Error 7 (Invalid Protocol): Ensure postback URL starts with http:// or https:// (not // or missing protocol)
Error 8 (Duplicate): For subscriptions: Enable 'Allow Duplicate Conversions' in Offers → Revenue & Payout Tab
Error 10 (Domains Not Matching): Verify click domain = conversion domain → Update Offers → General Tab → Tracking Domain
Error 11 (Invalid Network): Verify NID in postback matches Account Settings → Network ID

✓ Fix: Transaction ID & Click Attribution

Error 12 (Invalid Transaction ID): Check landing page → DevTools → Application → Cookies → Look for _ef_transaction_id. If missing, ClickScript didn't fire.
For S2S: Verify advertiser pulled ?transaction_id= from landing page URL and passed it back in postback
Error 13 (Invalid Click): Run Click Report filtered by Transaction ID → If no click found, check: (1) Click >90 days old? (2) Cookie blocked? (3) Click was Invalid due to targeting?
Error 14 (Offer Mismatch): Click on Offer A, conversion on Offer B → Verify advertiser's postback URL uses correct offer_id OR passes TID properly

✓ Fix: Offer Setup & Configuration

Error 15 (Invalid Offer): Verify offer exists in Offers → Manage. If deleted, recreate OR update advertiser postback URL
Error 16/17 (Invalid Domain): Check Network Settings → Tracking Domains / Conversion Domains → Add missing domain → Configure DNS (A record or CNAME)
Error 18 (Inactive Offer): Offers → General Tab → Set Status to 'Active'. If Private, approve partners in Visibility Tab
Error 19 (Expired Offer): Offers → General Tab → Extend 'End Date' OR remove end date for evergreen offers

✓ Fix: Security, Fraud & Device Matching

Error 21 (Invalid Token): Find token in Advertisers → Settings → Verification Token → Add to postback: &security_token=YOUR_TOKEN
Error 22 (Fraud): Check Conversion Report → 'Fraud Flag' column. If AppsFlyer, review their fraud logs. If false positive, manually approve
Error 23/24 (Device Mismatch): For IDFA/GAID errors, verify device ID captured on click matches conversion. Check Click Report → 'IDFA'/'Google AID' columns
For MMP integrations: Ensure proper SDK implementation and signature verification to prevent spoofing

✓ Fix: Events, Postback Controls & Redirects

Error 25 (Event Mismatch): Check Offers → Revenue & Payout Tab → Events. Verify advertiser's event_id parameter matches a valid event OR remove event_id to use base conversion
Error 26 (Postback Control): Navigate to Offers → Postback Controls → Review active rules. Temporarily disable to identify blocking rule, then adjust criteria
Error 27 (Pass Through): Check Offers → Forwarding Rules. If intentional redirect to fail traffic, this is working correctly. If not, check SmartSwitch settings or targeting rules

✓ Fix: 204 Response (Postback Accepted, No Conversion)

Root Cause: Everflow received postback but couldn't match to a click. This is usually Error #13 (Invalid Click) in disguise
Fix 1: Add 1-second delay between click/TID generation and postback firing to ensure record is indexed
Fix 2: Verify Transaction ID in postback matches _ef_transaction_id cookie → Use DevTools → Application → Cookies
Fix 3: Check if click is >90 days old (raw data purged after 3 months)
Fix 4: Run Click Report filtered by TID → If no click found, see Error #13 solutions above

✓ Fix: 400 Bad Request (Malformed URL)

Missing brackets: Check macro format → Everflow uses {transaction_id} not [transaction_id]
Missing required parameters: At minimum, postback must include nid= and transaction_id=
Special characters: URL-encode special characters in parameters (spaces, &, %, etc.)
Protocol mismatch: Ensure http:// or https:// matches server configuration
Test URL: Use Postback Testing Tool (Partners → Postbacks → Test button) to validate syntax

✓ Fix: 403 Forbidden / 401 Unauthorized

IP Whitelist: Add your server IP to Advertisers → Settings → Whitelist (this is Error #3)
Verification Token: Add &security_token=TOKEN to postback URL (find in Advertiser Settings)
API Key: For API integrations, include X-Eflow-API-Key header with valid API key
Check permissions: Ensure API key has appropriate scopes for the endpoint you're calling

✓ Fix: 500 Internal Server Error

Partner's server issue: This is usually on the receiving end (partner/advertiser server crashed or overloaded)
Check status: Contact partner to verify their server status and postback endpoint availability
Retry mechanism: Everflow will automatically retry failed postbacks up to 25 times. After 25 failures, postback auto-disables
DNS issues: Verify partner's domain resolves correctly → Run: nslookup partnerdomain.com
Temporary workaround: If persistent, ask partner for backup postback endpoint

✓ Fix: JavaScript SDK Not Tracking

Check ClickScript: View page source → Search for "EF.click" or "_ef_" → If missing, ClickScript not installed
Check Cookie: DevTools → Application → Cookies → Look for _ef_transaction_id. If missing, script didn't execute
Test in Incognito: AdBlockers and browser extensions can block JavaScript → Test in clean Incognito window
Sticky parameters: URL parameters made "sticky" cause script to fire on every page load → Remove sticky logic
Script placement: ClickScript must load BEFORE conversion script. Check or top of

✓ Fix: S2S Postback Not Firing

Check Advertiser Postback Report: Run report to see if postback was received. Look at 'Response Code' and 'Error' columns
Verify TID captured: Ensure advertiser's system pulled ?transaction_id= from landing page URL and stored it
Test postback manually: Use Postback Testing Tool (Partners → Postbacks → Test) with known TID
Check whitelist: If using IP/domain whitelist, verify advertiser's server IP is whitelisted (Errors #2/#3)
Verify postback URL: Must include: https://domain.com/?nid=XXX&transaction_id=TID at minimum

✓ Fix: Email Attribution / Clickless Tracking

Lead-first requirement: For Email Attribution, the lead event (with email) must fire BEFORE the conversion
Check email captured: Run Conversion Report → Add 'Email' column → Verify email was stored during initial event
For coupon codes: Ensure coupon_code parameter passed in postback: ?coupon_code=SUMMER2024
For clickless S2S: Must include oid= (Offer ID) and affid= (Affiliate ID) in addition to email or coupon
Test attribution: Fire conversion postback with known email → Check if it matches to correct partner

Diagnostic Info Generator

Opening a support ticket? Use this tool to generate formatted diagnostic information with all the details support needs to help you faster.

📋 Diagnostic Info Generator

Create a formatted support ticket with all the details support needs

Error Code Number (if known)

Find in Conversion Report → Error Code column

Error Message (optional)

Find in Conversion Report → Error Message column

Transaction ID

The unique ID for this conversion attempt

Offer ID (optional)

Partner ID (optional)

💡 Auto-detected: Timestamp, browser, and URL will be included automatically

✓ Diagnostic Info Ready - Paste Into Support Ticket

✅ Pre-Support Checklist

Try these quick fixes before opening a support ticket:

Run Click Report filtered by Transaction ID to verify click exists and isn't "Invalid"

Check Advertiser Postback Report to see what URL was actually received and response code

Verify offer is Active (Offers → Manage → Status column) and not expired or over cap

Test in Incognito mode to rule out browser extensions, AdBlockers, or cached cookies

Check IP/Domain Whitelist if using (Advertisers → Settings → Whitelist)

Review the Error Lookup above for your specific error code's common causes and fixes

Complete Error Code Reference Table

For quick reference, here's the complete list of all 27 conversion error codes

Code

Error Message

Quick Definition

Throttled Conversion

Throttle rate is invalid (must be 0-100%)

Advertiser Whitelist Domain

Domain not in advertiser whitelist - More Details

Advertiser Whitelist IP

IP not in advertiser whitelist - More Details

Over Caps

Daily/weekly/monthly conversion or payout caps exceeded

Above Lookback Window

Conversion outside attribution window - More Details

Non-HTTPS Traffic

Incoming pixel using HTTP but offer requires HTTPS

Invalid Protocol

Cannot detect whether pixel using HTTP or HTTPS

Duplicate Conversion

Conversion already recorded for this transaction

Manually Rejected

Network admin manually rejected this conversion

Domains Not Matching

Click domain ≠ conversion domain

Invalid Network

Network ID (NID) is invalid or missing

Invalid Transaction ID

Transaction ID missing, empty, or malformed

Invalid Click

Associated click not found (most common error)

Click and Conversion Offer Not Matching

Click on Offer A, conversion fired to Offer B

Invalid Offer

Offer ID does not exist

Invalid Tracking Domain

Tracking domain not configured or DNS issue

Invalid Conversion Domain

Conversion domain not configured or DNS issue

Inactive Offer

Offer status set to Inactive or Private

Expired Offer

Offer's end date has passed

Below Lookback Window

Conversion occurred too quickly (possible bot)

Invalid Verification Token

Security token missing or incorrect

Fraudulous Conversion

Advertiser flagged as fraudulent (e.g., AppsFlyer fraud_flag)

Invalid IDFA Match

iOS device ID on click ≠ conversion

Invalid Google ADID Match

Android device ID on click ≠ conversion

Unmatching Offer Event ID

Event ID does not belong to this offer

Postback Control

Blocked by Postback Control rule

Pass Through

Pass Through / Fail Traffic redirect active

Hidden Causes & "Gotchas"

Some errors have causes that aren't obvious from the error message alone. Here are the most important hidden causes to know:<

🕒 The 90-Day Data Purge

Hidden Cause: Error #13 (Invalid Click) can mean the click is >90 days old. While analytics are kept forever, raw click data is purged after 3 months to manage database size.

What This Means: If an advertiser fires a postback for a click older than 90 days, Everflow no longer has the raw record to match it against.

Fix: This is expected behavior, not a bug. Conversions must fire within 90 days of click for attribution.

🔒 Silent Advertiser Whitelist

Hidden Cause: If "Enforce Advertiser Whitelist" is enabled, any conversion from an unlisted IP/domain is blocked silently without notifying the advertiser.

What This Means: The advertiser thinks they fired the postback successfully (they see 200 OK response), but Everflow rejected it before it reached the system.

Fix: Check Advertisers → Settings → Whitelist. Add advertiser's server IP or domain. Check Advertiser Postback Report to see actual source IP.

📧 Email Attribution Duplicate Logic

Hidden Cause: Error #8 (Duplicate Conversion) can mean "same email used twice" if Email Attribution is enabled.

What This Means: The system is configured to only allow one "Approved" conversion per email address for a specific event.

Fix: If legitimate (e.g., same customer making multiple purchases), enable "Allow Duplicate Conversions" in Offers → Revenue & Payout Tab.

🔄 The 25-Failure Auto-Disable

Hidden Cause: After 25 consecutive postback failures, Everflow automatically disables the postback entirely.

What This Means: If your partner postback URL is misconfigured or their server is down, after 25 failed attempts, Everflow stops trying completely.

Fix: Fix the underlying issue (wrong URL, partner's server down, etc.), then manually re-enable the postback in Partners → Postbacks.

🍪 Direct Linking "Invisible" Transaction ID

Hidden Cause: In direct linking (Meta, Google Ads), users expect to SEE the Transaction ID in the URL. When it's not there, they think tracking is broken.

What This Means: With direct linking, the TID is generated by ClickScript and stored in a first-party cookie (_ef_transaction_id), NOT passed as a URL parameter.

Fix: Check DevTools → Application → Cookies → Look for _ef_transaction_id. If present, tracking IS working (you just can't see it in the URL).

Where to Find Error Codes

Error codes appear in multiple locations depending on how you're tracking conversions:

Conversion Report (Most Common)

Navigate to Reporting → Conversion

Add columns: Error, Error Code, and Error Message

Rejected conversions show a red X in the Error column with the specific code and message.

Advertiser Postback Report (For S2S Debugging)

Navigate to Reporting → Advertiser Postback

Shows:
• Raw postback URL received
• HTTP response codes (200, 204, 400, 403, 500)
• Error details if postback was rejected

This is essential for diagnosing "postback fired but no conversion appeared" scenarios.

Conversion Import Errors (For CSV Uploads)

Navigate to Reporting → Conversion Imports

Click the Conversion Errors column to see which rows failed and why.

Common CSV import errors include "Reached Cap" (conversion in Pending status, not rejected) and formatting errors.