ClipAffiliates Clipping Campaigns Scraper avatar

ClipAffiliates Clipping Campaigns Scraper

Pricing

from $0.96 / 1,000 campaign results

Go to Apify Store
ClipAffiliates Clipping Campaigns Scraper

ClipAffiliates Clipping Campaigns Scraper

Scrape ClipAffiliates' public campaign board: CPM per 1,000 views, budget spent vs remaining, paid views left, active affiliate competition count and a 0-100 opportunity score. HTTP-only, no login, no key. Built for clippers, UGC creators and agencies hunting fresh, low-competition campaigns.

Pricing

from $0.96 / 1,000 campaign results

Rating

0.0

(0)

Developer

Mr Zack

Mr Zack

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Pulls the public campaign board of ClipAffiliates — the clipping & UGC marketplace where creators pay clippers per 1,000 views — and turns it into clean, money-first rows: CPM, budget remaining, paid views left, how many clippers are already competing, and a 0-100 opportunity score.

No login. No API key. No proxies. HTTP-only, so runs finish in seconds and cost almost nothing.

Who this is for

  • Clippers & UGC creators deciding which campaign to jump on today — before the budget runs out.
  • Clipping agencies monitoring every board (Whop, Vyro, ClipAffiliates) from one dashboard.
  • Analysts & builders tracking the creator-economy clipping market.

The board moves fast: budgets deplete in days and new drops appear without notice. The clippers who catch a fresh campaign with low competition earn the most per clip. This actor exists so you never refresh the board manually again.

What makes this board special: competition data

ClipAffiliates publicly exposes active_affiliates_count — how many clippers already joined each campaign. This actor turns that into:

  • remainingUsdPerAffiliate — remaining budget ÷ active affiliates: the competition-adjusted money on the table.
  • lowCompetition sort + maxActiveAffiliates filter — surface quiet campaigns before the crowd arrives.

No other clipping-board dataset gives you this.

Output fields

FieldMeaning
name, creatorName, typeCampaign, who runs it, clipping or ugc
statusactive / ended (derived from end date + budget)
cpmUsdUSD per 1,000 views (normalized from pay rate)
budgetUsd / budgetSpentUsd / budgetRemainingUsd / budgetSpentPctThe money pool
remainingViewsHow many views can still get paid at this CPM
activeAffiliatesCountClippers already in — your competition
remainingUsdPerAffiliateRemaining budget split across the competition
maxPostsPerAffiliate, maxAffiliates, accessTypeParticipation rules
platforms, countries, hashtagWhere and how to post
createdAt, ageHours, isFreshWithin24h/72hCatch new drops early
endDate, endsInDays, closingWithin48hDeadline math
opportunityScore0-100: CPM (30) + budget headroom (30) + low competition (15) + freshness (15) + time left (10)

This data is worth the most when it's fresh. Set it and forget it:

  1. Open the actor → Schedules → create a schedule (e.g. every 30 minutes or hourly).
  2. For a cheap "new drop alert", set input freshWithinHours: 1 with a 1-hour schedule — most runs push 0 rows (you pay only the $0.01 start fee), and the moment a new campaign lands you get exactly the new rows.
  3. Add an integration (Slack / email / webhook) on "run succeeded with items" to get pinged only when something new appears.
  4. Pair with sortBy: "lowCompetition" or maxActiveAffiliates: 10 to be first into quiet campaigns.

Example input

{
"activeOnly": true,
"minCpmUsd": 1,
"maxActiveAffiliates": 40,
"sortBy": "opportunity"
}

Pricing

Pay-per-event: $0.01 per run + $0.96 per 1,000 campaign rows. A typical run on today's board costs about a cent.

The full clipping-economy data stack

Track every major clipping board with one scheduler:

Notes & fair use

  • Reads only the public discover board over its official public JSON endpoint — no login, no bypass, gentle request rate (a single GET per run).
  • Not affiliated with ClipAffiliates.
  • Data accuracy depends on what the board publishes; estimated_spend is the platform's own estimate.