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

# Supported Use Cases

> How ClickFlare can be used across different traffic and business models

## TL;DR

> ClickFlare is a flexible tracking and attribution platform that supports multiple performance-marketing use cases. While setups may differ, the underlying tracking logic remains the same.

If you run paid traffic and need to understand **where results come from**, ClickFlare can be adapted to your workflow.

***

## Why Use Cases Matter

Different users come to ClickFlare with different goals:

* Some want to track affiliate offers
* Others run e-commerce or lead generation
* Some focus on search arbitrage or call tracking

This article helps you quickly identify **where you fit** and which parts of ClickFlare are most relevant to you.

📌 This is not a setup guide — each use case links to dedicated documentation later.

***

## Affiliate Marketing

ClickFlare is commonly used to track traffic sent to **affiliate offers**.

Typical setup:

* Traffic source → ClickFlare → landing page (optional) → affiliate offer
* Conversions are tracked via postback, script, or API

What you can analyze:

* Performance by campaign, ad, or keyword
* Landing page → offer click-through rates
* Conversion volume and revenue attribution

ClickFlare helps affiliate marketers understand **which traffic actually converts**, not just which traffic gets clicks.

***

## Search Arbitrage & RSOC

ClickFlare is widely used for **search arbitrage** and **RSOC (Related Search / AdSense-based) setups**, and is specifically designed to handle the challenges of search traffic.

One of the main challenges in search arbitrage is **delayed revenue reporting**. Search feeds often report revenue hours or days after the click, making optimization difficult if data is not refreshed continuously.

ClickFlare solves this through **direct API integrations with more than a dozen major AFD and RSOC feeds**, ensuring that revenue data in ClickFlare is **continuously updated and kept in sync** as feeds report new earnings.

Typical setup:

* Traffic source → ClickFlare → content or RSOC page
* Revenue is pulled automatically via API or tracked via script

What you can analyze and optimize:

* **Keyword-level performance**
* **Feed-level performance**
* **Revenue and profit attribution**
* Core metrics such as **EPC** and **EPM**

ClickFlare also allows you to:

* Rotate or split-test multiple RSOC or AFD feeds **within the same link**
* Split-test keywords and keyword sets
* Compare performance across feeds, keywords, and traffic sources

For search-focused workflows, ClickFlare includes a **built-in keyword builder**, making it easy to create, rotate, and manage large keyword sets efficiently.

This makes ClickFlare especially well suited for search arbitrage setups where **accurate, up-to-date revenue data** and **granular keyword analysis** are critical.

***

## E-commerce

ClickFlare can be used to track **full e-commerce user journeys**, including **cross-domain tracking** setups where users move between different domains before completing a purchase.

This is common in scenarios where traffic flows through:

* Advertorial or pre-sell pages
* One or more product or checkout domains
* Multiple stores or brand domains

With ClickFlare, you can:

* Rotate or split-test **advertorials**
* Route traffic to **different stores or product pages**
* Track the entire user journey **across domains**, from the first click to the final outcome

Typical setup:

* Traffic source → ClickFlare → advertorial (optional) → store / product page (same or different domain)

ClickFlare supports tracking of **both primary and secondary e-commerce events**, such as:

* Purchase (sale)
* Upsell or downsell
* Refund
* Add to cart
* Initiate checkout
* Custom funnel events

This allows you to:

* Build funnel-level metrics
* Identify drop-off points across the journey
* Analyze performance beyond just the final sale

ClickFlare can also report on **product-level performance**, making it possible to understand:

* Which products convert best
* Which traffic sources perform best per product
* How advertorials, pages, or stores impact results

ClickFlare is traffic-source agnostic and supports **all major traffic types**, including:

* Native
* Social
* Search
* Push
* Pop
* Display

This makes it well suited for e-commerce advertisers running **multi-step, cross-domain funnels** across multiple platforms.

***

## Lead Generation (Forms & Events)

ClickFlare is well suited for **lead generation campaigns**, especially setups where users go through **multi-step funnels** to pre-qualify before submitting a lead.

Typical setup:

* Traffic source → ClickFlare → landing page or funnel → form or event
* Conversions are tracked via script, postback, or API

ClickFlare’s **built-in Tag Manager** allows you to track **in-page events**, such as:

* Form submissions
* Quiz or funnel step progression
* Button clicks
* Drop-offs at specific steps

This is especially useful for lead generation funnels where understanding **user behavior before the final lead** is critical.

Through the Tag Manager, ClickFlare can also capture **first-party user data** (such as name, email, phone, or custom inputs) and store it alongside the conversion for analysis and enrichment.

ClickFlare also includes an **Event Filter**, which allows you to control **which conversions are sent back to the traffic source**.

For example, you can:

* Send back only **high-quality leads** (based on payout or conditions)
* Fire conversions only when specific criteria are met (such as location or lead type)

This is particularly valuable when building:

* High-quality audiences
* Lookalike audiences
* Conditional conversion signals for ad platforms

In addition, ClickFlare supports **custom webhooks**, making it possible to send lead data directly to:

* Your CRM
* Internal systems
* External automation tools

This makes ClickFlare a flexible layer between traffic sources, lead funnels, and downstream systems.

***

## Call Tracking & Offline Conversions

ClickFlare supports **call-based campaigns** and offline conversions, which often involve **pre-qualification funnels** before a call is initiated.

In many call-tracking setups, users go through:

* A quiz or questionnaire
* One or more qualification steps
* A call action (click-to-call or phone number reveal)

Similar to lead generation, ClickFlare’s **built-in Tag Manager** allows you to track:

* User progression through quizzes or funnels
* Drop-offs at specific questions or steps
* Clicks on call buttons or phone numbers

These insights help you understand **where users disengage** and which steps drive qualified calls.

For call tracking specifically, ClickFlare also helps prevent **number saturation**.
Using the Tag Manager, you can inject the **number pool script only after a user is qualified** (for example, after answering certain questions). This reduces unnecessary number allocation and helps avoid running out of available phone numbers.

All tracked events — such as quiz completion, call button clicks, or qualified calls — can be:

* Recorded as conversions in ClickFlare
* Sent back to the traffic source for optimization and audience building

ClickFlare is compatible with **any call-tracking platform** that supports conversion tracking and integrates natively with widely used platforms such as **Ringba**, **Retreaver**, and **MarketCall**.

This makes ClickFlare a strong fit for call-based campaigns where **qualification, cost control, and optimization** are critical.

***

## Paid Media Optimization & Conversion APIs

ClickFlare can act as a **central attribution layer** for paid media platforms.

Typical setup:

* Traffic source → ClickFlare → destination
* Conversions are sent back to the traffic source via Conversion APIs

What you can achieve:

* More accurate conversion attribution
* Improved platform optimization and bidding
* Reduced data loss from browser and privacy restrictions

This use case is common with Google Ads, Meta Ads, Pinterest, and similar platforms.

***

## One Platform, Multiple Use Cases

Although these use cases differ in execution:

* The **core tracking logic remains the same**
* Visits, Clicks, and Conversions behave consistently
* Reporting and attribution follow the same principles

The difference lies in:

* How traffic is sent
* How conversions are triggered
* Which integrations are used

## Related Resources

* How ClickFlare Works (High-Level Overview)
* Key Concepts & Terminology
* First-Time Setup Checklist
* Create Your First Redirect Campaign