ClickBank Marketplace Scraper | Gravity, Sales, Refund Rate

For affiliate marketers, media buyers, and AI agents evaluating ClickBank offers at scale — without clicking through the marketplace UI one offer at a time.

No login required. No ClickBank account, no API key. Pay per result (Pay Per Event).

Scrape the ClickBank affiliate marketplace by keyword or category and get every offer's real marketplace stats — gravity, initial/average sale $, average rebill $, refund rate, EPC, conversion rate — in one structured dataset. Pay per result.

---

What data you get

One record per offer:

• offer_title, vendor, offer_url, offer_description, category, sub_category
• gravity, bi_gravity — ClickBank's affiliate-activity popularity scores
• is_recurring — whether the offer has a rebill/subscription component
• initial_sale_usd, avg_sale_usd — real $ earned per sale (average across affiliates)
• avg_rebill_usd — average $ per rebill (0.0 for non-recurring offers — a real value, not missing data)
• refund_rate — the marketplace's return/refund rate for the offer (return_rate_source tells you the measurement window, e.g. "90 Day Return Rate")
• initial_epc, average_epc, future_epc, net_epc, conversion_rate — affiliate performance stats
• seller_volume, rank, score, activate_date
• languages — which locales the offer is live in (en/de/es/fr/it/pt)
• has_upsell, has_dollar_trial, mobile_enabled, direct_tracking, cpa_visible
• affiliate_tools_url, affiliate_support_email, image_url
• hoplink — your personalized ClickBank tracking link, built automatically if you supply your own affiliate nickname (optional — see Input below)

Every record includes parse_confidence (0.0–1.0) and warnings.

---

Why this beats a metadata-only marketplace scrape

Most marketplace scrapers only surface what's trivially visible in the page's title/description text. This actor reads ClickBank's own marketplace stats endpoint directly, so it returns the numbers that actually decide whether an offer is worth promoting:

Stat	What it tells you
initial_sale_usd / avg_sale_usd	Real $ per sale — not a guess from price × commission %
avg_rebill_usd	Real recurring $ per rebill cycle
refund_rate	How often buyers refund — a high-gravity offer with a bad refund rate is a trap

These are genuine public marketplace stats (rendered on the ClickBank marketplace page for every logged-in and logged-out visitor) — not vendor-gated, not scraped from a paywalled page.

---

How to use

Search by keyword, ranked by gravity (default)

{
  "keyword": "weight loss",
  "maxResults": 50
}

Browse a whole category, ranked by average earnings per sale

{
  "category": "Health & Fitness",
  "sortBy": "averageEarningsPerSale",
  "maxResults": 100
}

Narrow to a sub-category

{
  "category": "Health & Fitness",
  "subCategory": "Dietary Supplements",
  "sortBy": "gravity",
  "maxResults": 50
}

Get your own personalized hoplinks

{
  "keyword": "keto diet",
  "affiliateNickname": "yourAffiliateNick",
  "maxResults": 20
}

---

Input parameters

Field	Type	Default	Description
keyword	string	""	Free-text search across offer titles/descriptions
category	string	""	Marketplace category filter, e.g. "Health & Fitness"
subCategory	string	""	Sub-category filter (used together with category)
sortBy	string	gravity	relevance, gravity, biGravity, averageEarningsPerSale, averageEPC, initialEarningsPerSale, futureEarnings, netEPC, conversionRate
sortDescending	boolean	true	Highest values first
maxResults	integer	50	Total offers to return
affiliateNickname	string	(none)	Optional — your ClickBank affiliate nickname, used only to build personalized hoplink values. The actor works fully without it.
proxyConfiguration	object	RESIDENTIAL	Apify proxy — always used, works out of the box

At least one of keyword or category should be set, otherwise the marketplace's default (unfiltered, relevance-ranked) result set is returned.

---

Output schema

See "What data you get" above for the full field list. Full field reference in .actor/dataset_schema.json.

---

Pricing example

Pay per result (PPE). Charged once per offer record pushed.

Fetch	Records
Keyword search, top 50 offers	50
Category browse, 100 offers	100
Deep research pull, 500 offers across a category	500

---

FAQ

Does it need a ClickBank account or login? No. The marketplace search this actor reads is publicly available — the same data any anonymous visitor to the ClickBank marketplace page sees.

What's a hoplink and why is it optional? A hoplink is ClickBank's affiliate tracking URL format (hop.clickbank.net/?affiliate=...&vendor=...). If you supply your own ClickBank affiliate nickname via the affiliateNickname input, every record's hoplink field is built as your personalized tracking link. If you don't, hoplink is simply null — everything else in the record is unaffected.

Why is avg_rebill_usd sometimes 0? 0.0 is the real, correct value for offers that don't have a recurring/rebill component (is_recurring: false). It's not missing data.

Can I sort by refund rate? Not directly (ClickBank's marketplace API doesn't expose refund rate as a sort field), but every record includes refund_rate so you can filter/sort the dataset yourself after the run.

Legal

Not affiliated with ClickBank or Keynetics Inc. This actor reads ClickBank's own public marketplace endpoint. Use responsibly.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.