Kickstarter Campaign Tracker - Backers, Pledged & Days Left

Backers, amount pledged, goal, percent funded, days left and state (live, successful, failed, canceled) for any Kickstarter project, one row per project. Amounts come with a USD conversion, so campaigns in GBP, EUR or JPY can sit in one table.

With monitoring on, a campaign is returned only when its backers, pledged amount or state have changed. The row carries the difference since the last check and the pace per day. The first check of a campaign is free.

Paste project links as they appear in the browser (https://www.kickstarter.com/projects/<creator>/<project>), one per line.

Input

Field	What it does
projectUrls	Kickstarter project links, one per line (?ref=... and /description at the end are fine)
maxProjects	Stop after this many projects (default 100)
monitoringMode	Return only campaigns that changed since the previous run
monitorMode	What counts as a change: funding-change (backers, pledged, state), any-change (also comments) or milestones (goal reached or state changed)
resetMonitoringState	Forget the remembered figures and start over with a free first check
useProxy	Move to fresh Apify datacenter proxy addresses if Kickstarter refuses requests (default on)

What you get

One row per project:

Column	Meaning
projectName	The project title
state	live, successful, failed, canceled, suspended or submitted, as Kickstarter reports it
backers	Number of backers
pledged	Amount pledged, in the project's currency
currency, goal	The project's currency and funding goal
percentFunded	Pledged as a percentage of the goal, rounded down to one decimal (99.96% shows as 99.9, never 100)
isGoalReached	true when the pledged amount has reached the goal
pledgedUsd, goalUsd	Pledged and goal converted to US dollars at Kickstarter's own rate for the project
averagePledge	Pledged divided by backers
daysLeft, hoursLeft	Time until the deadline, rounded down; 0 once the deadline has passed
deadline, launchedAt	Deadline and launch time (ISO 8601, UTC)
pledgedPerDay, backersPerDay	Average per day since launch (up to the deadline for ended campaigns)
commentsCount, updatesCount	Comments and creator updates
rewardsCount, lowestRewardAmount	Number of reward tiers and the cheapest one
staffPick, isInLatePledges	Kickstarter's "Project We Love" flag, and whether the project accepts late pledges after the campaign
blurb, creatorName, category, parentCategory, location, country, imageUrl	Description and context
projectId, projectUrl	Kickstarter's numeric project ID and the project link
detailsStatus, detailsReadAt	Whether the name, goal and deadline were read in this run or remembered from an earlier one (see below)
input, scrapedAt, status	What you typed, when it was read, ok for a project row

Monitoring columns (filled in monitoring mode): change, isFirstCheck, changedFields (for example ["backers","pledged"] or ["state"]), backersChange, pledgedChange, pledgedChangeUsd, previousBackers, previousPledged, previousState, previousCheckedAt, goalReachedSinceLastCheck, backersPerDaySinceLastCheck, pledgedPerDaySinceLastCheck.

Read on 2026-10-23:

Project	state	backers	pledged	goal	percentFunded	pledgedUsd
An Infamous Traffic: Second Edition	live	6436	601727 USD	50000	1203.4	601727
Nap Comix: First Steps	live	192	4973 GBP	8000	62.1	6628.02
Good Kitties + Super Chonk: The Purr-fect Pair of Cat Games	live	367	36758 USD	9600	382.8	36758
GENKI: Covert Dock 3 and ShadowCast 3	successful	12237	1437389 USD	16800	8555.8	1437389
Lil - The Book Series	failed	49	2455 USD	6000	40.9	2455

Monitoring mode

Turn on Monitoring mode and run the same list on a schedule (for example every hour or every day):

1. First run of a project: its backers, pledged amount, state and comment count are remembered as the starting point. You get a first-check row without figures, and nothing is charged.
2. Later runs: each project is read and compared with what was remembered.
   • Something changed: you get the project row with backersChange, pledgedChange, changedFields and the pace since the last check, charged as one project row.
   • Nothing changed (or, in milestones, nothing that counts as a milestone): no project row; the project is charged as one check. When no project in the run is returned, you get one no-change row so an empty result is never ambiguous.

What counts as a change:

• funding-change (default): backers, pledged amount or state. A new comment alone is not reported.
• any-change: the same, plus the comment count.
• milestones: only when the project reaches its goal for the first time (goalReachedSinceLastCheck: true) or its state changes, for example live to successful. Smaller moves are charged as a check and remembered without being returned, so the next difference is measured from the latest check. While the goal is unknown (the project's details could not be read), the moves are not remembered, so passing the goal is still caught once the goal is read.

backersPerDaySinceLastCheck and pledgedPerDaySinceLastCheck are filled when at least one hour has passed since the previous check, so a few minutes between runs never turn into an inflated daily pace.

Figures are remembered per project ID, so adding a project to your list does not reset the others, and the same project given with two different links is one project. Forget the remembered figures and start over clears them, and the next run is a free first check again. A change that could not be delivered because the run's maximum total charge was reached is not remembered, so the next run returns it.

What is charged

• campaign-returned: one per project row with status: ok.
• campaign-checked: monitoring mode only. One per project that was compared and not returned: it had not changed, or in milestones mode it moved without reaching its goal or changing state. A project that is returned is charged as a row only, not as a check.
• Not charged: first-check, no-such-project, invalid-input, duplicate-input, unreadable, blocked, no-change, not-read and budget-reached rows. There is no monthly fee.

If you set a maximum total charge, the run stops before it, lists the lines it did not read in a not-read row, and charges nothing for them. In monitoring mode the run stops as soon as the limit cannot cover one more check, before reading the next project, even if that project would have been a free first check.

Rows that explain instead of failing

status	When
first-check	Monitoring: the first time a project is seen, its starting point was remembered
no-such-project	Kickstarter has no project at the link: it was deleted, or the creator or project part of the link is wrong
invalid-input	The line is not a Kickstarter project link, for example a kck.st short link or a Discover page - or no project was given
duplicate-input	The same project appeared earlier in the list (also when it was given with a different link)
unreadable	The figures came back in a form that could not be read. No figure is guessed
blocked	Kickstarter kept refusing the request (HTTP 403/429)
not-read	Lines that were not requested: after a blocked row or three unreadable projects in a row, or when maxProjects or the charge limit was reached
no-change	Monitoring: every project was compared and none had changed
budget-reached	A changed project was ready but did not fit inside the run's maximum total charge

Questions people ask

How do I track a Kickstarter campaign's backers and pledges over time? Put the project link in projectUrls, turn on monitoring mode and schedule the Actor. Each run returns only the campaigns that moved, with the change in backers and pledged amount since the previous run.

How do I get the pledged amount and days left for many Kickstarter projects at once? Paste up to 1,000 project links in one run. Each row has pledged, goal, percentFunded, daysLeft and hoursLeft, plus pledgedUsd for comparing campaigns in different currencies.

Can I get an alert when a Kickstarter campaign reaches its goal? Use monitoring mode with monitorMode: milestones. The project is returned once, with goalReachedSinceLastCheck: true, in the run after it passes its goal, and again when its state changes to successful or failed.

Does it work for campaigns that have already ended? Yes. Successful, failed and canceled projects return their final backers and pledged amount, with daysLeft: 0.

Good to know

• Figures are fresh on every run: backers, pledged amount, state and comments are read each time. The name, goal, deadline, rewards and the other details are read at most once a day per project and reused from memory in between (detailsStatus: remembered); they are read again as soon as the project's state changes. If the details cannot be read for a project, its row still has the figures, the detail columns are null, and detailsStatus says why.
• One schedule per list: do not let two monitoring runs of the same projects overlap. Both compare with the same remembered figures, so the same change can be returned and charged by each. A change that was returned is remembered at once, so a run that is aborted does not return it again.
• Search is not included: this Actor follows the projects you give it. Use the link from the project page.
• Short kck.st links are not followed: open one once in a browser and paste the full link.
• Currency: pledged and goal are in the project's currency. pledgedUsd and goalUsd use the exchange rate Kickstarter shows for the project, which can differ slightly from today's market rate.
• Requests go to Kickstarter's public project pages with a pause between them and a User-Agent that identifies this Actor. No login, no Kickstarter account and no residential proxy are used. If Kickstarter refuses requests from one address, the run moves to fresh Apify datacenter proxy addresses (you can turn this off).
• This Actor is not affiliated with, endorsed by or sponsored by Kickstarter. Kickstarter's terms restrict automated collection; decide for yourself whether your use is permitted before you run it.

Thanks for using this Actor

We build these tools for people who run them every day, and we improve them from what users tell us.

• Missing a field, or need another filter? Tell us in the Issues tab. If the data is there, we add it.
• Found a bug or a wrong value? Post the run ID in the Issues tab. Wrong data is the thing we fix first.

If this Actor saved you time, a short review helps other people find it.