> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Conversion Tracking Methods Explained

> Understand the different ways to track conversions in ClickFlare and choose the right method for your setup

## Overview

ClickFlare supports multiple ways to register conversions. While they all achieve the same goal—recording a conversion and attributing it to the correct campaign—they differ in **reliability**, **requirements**, and **best-fit use cases**.

This article helps you answer a common question:

> **Which conversion tracking method should I use for my campaign?**

It compares each method at a high level and explains when to use one over another.

***

## The Five Conversion Tracking Methods in ClickFlare

ClickFlare can register conversions through the following methods:

1. **S2S Postback (Server-to-Server)**
2. **Conversion Tracking Pixel (Image Pixel)**
3. **Conversion Tracking Script (Thank-You Page Script)**
4. **API-Based Pull (Integration)**
5. **Manual Conversion Upload**

All methods rely on the same principle:
👉 **the conversion must be matched to a valid ClickFlare Click ID**.

***

## 1) S2S Postback (Recommended)

**Best for:** Most affiliate networks and paid traffic setups

### How it works (high level)

* ClickFlare passes a Click ID to the affiliate network
* When a conversion happens, the network sends that Click ID back to ClickFlare via a server-to-server request

### Why this is the preferred method

* Does not rely on the user’s browser
* Not affected by cookies, ad blockers, or page load issues
* Most accurate and reliable option

### Use S2S postback if:

* Your affiliate network supports postback URLs
* You want maximum tracking reliability
* You are running performance-driven campaigns

> [!NOTE]
>
> **Recommendation:**
> If S2S postback is available, always use it.

***

## 2) Conversion Tracking Pixel (Image Pixel)

**Best for:** Simple funnels where S2S postback is not available

### How it works

* ClickFlare stores the Click ID in the browser
* A hidden image pixel fires on the thank-you page
* The pixel sends a conversion request to ClickFlare

### Limitations

* Relies on browser cookies
* Can fail if cookies are blocked or cleared
* Less reliable than S2S postback

### Use a pixel if:

* You do not have access to postback tracking
* You control the thank-you page
* Occasional tracking loss is acceptable

***

## 3) Conversion Tracking Script (Thank-You Page Script)

**Best for:** Browser-based tracking with improved reliability

### How it works

* Similar to the image pixel
* Uses JavaScript instead of a static image
* Can read/set first-party cookies on the page domain

### Why it’s better than a pixel

* More resilient in some cross-domain scenarios
* Better cookie handling in modern browsers

### Use the script if:

* You control the thank-you page code
* You want a browser-based fallback that’s more reliable than an image pixel

📌 Still less reliable than S2S postback.

> [!NOTE]
>
> **Note**: Pixel- and script-based tracking fires on page load. If a user refreshes or revisits the thank-you page, the conversion request may fire again. While ClickFlare typically deduplicates conversions using the Click ID, setups that use dynamic transaction IDs (txid) can unintentionally overreport conversions.
>
> For this reason, pixel- and script-based tracking should be treated as a fallback method and used carefully. Whenever available, server-to-server (S2S) postback tracking is strongly recommended, as it fires conversions once, server-side, and is not affected by page reloads or browser behavior.

***

## 4) API-Based Pull (Integration)

**Best for:** Platforms where ClickFlare pulls conversions and revenue directly

### How it works

* ClickFlare connects to a supported platform via API
* Conversions and revenue are pulled automatically
* No postback or pixel is required

### Important clarification

This method works **only when a supported integration exists in ClickFlare**.

It is commonly used for:

* Certain affiliate networks
* Search monetization feeds
* Revenue streams with delayed reporting

### Use API-based pull if:

* A native ClickFlare integration exists
* The platform provides conversion data via API
* Revenue is delayed or finalized later

> [!WARNING]
>
> **Do not confuse this with Conversion API integrations**, which are used to send conversions *from* ClickFlare *to* traffic sources.

***

## 5) Manual Conversion Upload

**Best for:** Edge cases and recovery scenarios

### How it works

* You manually upload conversions via the ClickFlare UI
* Each conversion must include a valid Click ID
* Optional payout, transaction ID, type, and timestamp can be included

### Typical use cases

* Offline conversions
* Missed postbacks
* Delayed reconciliation
* One-time corrections

📌 Manual upload is not intended for real-time tracking.

***

## Comparison Overview

| Method | Reliability | Browser-Dependent | Recommended |
| - | - | - | - |
| S2S Postback | ⭐⭐⭐⭐⭐ | ❌ No | ✅ Yes |
| Tracking Script | ⭐⭐⭐ | ✅ Yes | ⚠️ Fallback |
| Image Pixel | ⭐⭐ | ✅ Yes | ⚠️ Fallback |
| API Pull | ⭐⭐⭐⭐ | ❌ No | ✅ When available |
| Manual Upload | ⭐ | ❌ No | ❌ Exception only |

***

## Can You Use Multiple Methods at Once?

Technically yes, but **not recommended**.

Using more than one method for the same conversion can result in:

* Duplicate conversions
* Inflated revenue
* Reporting inconsistencies

📌 **Best practice:**
Use **one conversion tracking method per conversion event**.

***

## Common Mistakes When Choosing a Method

* Using pixel tracking when S2S postback is available
* Assuming Conversion API integrations report conversions *into* ClickFlare
* Mixing multiple methods for the same event
* Forgetting to pass the Click ID to the affiliate network

***

## How to Choose (Quick Decision Guide)

* **Affiliate network supports postback?** → Use **S2S postback**
* **No postback, but you control the thank-you page?** → Use **script**
* **No script access?** → Use **image pixel**
* **Using a supported revenue/feed integration?** → Use **API pull**
* **Need to recover missed conversions?** → Use **manual upload**

***

**FREQUENTLY ASKED QUESTIONS**

Got questions? Find the answers below:

> **Q1:** Which method should I start with?

**A1**: S2S postback, whenever possible.

> **Q2:** Is browser-based tracking still supported?

**A2**: Yes, but it should be treated as a fallback, not a primary method.

> **Q3:** Can I change the method later?

**A3**: Yes. Conversion tracking methods affect future conversions only.

> **Q4:** Do all methods support payout tracking?

**A4**: Yes, but payout handling depends on the method and configuration.

## Related Resources

* How Conversion Tracking Works
* Tracking Conversions Using S2S Postback
* Conversion Tracking Pixel Setup
* Conversion Upload
* Event Filter (Advanced)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.