Indiegogo is the crowdfunding platform that doesn't end. Where Kickstarter shuts the door when the funding bar closes, Indiegogo flips you over to InDemand and the campaign keeps selling for months — sometimes years. Snapmaker raised more on InDemand than during their initial campaign. Great for revenue. Brutal for the comment wall, which keeps growing while your attention has long since moved on. Indiegogo doesn't ship a built-in export, so triaging that thread by hand stops working past a few hundred rows. This guide walks through pulling every comment off any public Indiegogo campaign into Excel, CSV or JSON — backer flag, owner-reply flag, team-member flag, threaded replies and timestamps included.

Why export Indiegogo comments

Indiegogo comments are the canary for fulfilment risk and the fuel tank for InDemand growth. Pull them into a spreadsheet and the workflows the campaign UI was never designed for finally become possible:

  • Backer-only triage — filter is_backer = Y so paying contributors get answered first. Public chatter waits its turn.
  • InDemand transition window analysis — your funding-window backers and your InDemand backers behave differently. The InDemand cohort asks more shipping questions and refunds at a higher rate. Pull comments before vs. after the cutover and you can see it in the data.
  • Owner-reply rate — calculate (owner replies ÷ top-level comments) and watch what happens to it when fulfilment slips. Every project we've seen that ended in a refund storm had a falling reply rate two weeks before the storm hit.
  • Refund-risk early warning — sentiment-tag the comment_text column on a 7-day rolling window. A sustained spike in "refund", "scam" or "where is my" is the earliest sign of a chargeback wave forming.
  • Cross-campaign superfan map — the profile_url column de-duplicates backers across every Indiegogo (and Kickstarter) campaign you've run. Three-time backers are your free pre-launch list.
  • Team-member audit — the is_team_member flag separates official team replies from the founder's voice. Useful for the post-mortem on the week everything went sideways.

How to export — step by step

Step 1 — Copy the campaign URL

Open the Indiegogo project page (e.g. https://www.indiegogo.com/projects/<project>) and copy the URL. The main page works, the #/comments tab works — the exporter normalises both. Campaign has to be publicly viewable; private drafts can't be scraped.

Step 2 — Paste it into the Indiegogo Comments Exporter

Go to exportcomments.com/download-indiegogo-comments and drop the URL in. No browser extension. No Indiegogo login on your side. No OAuth dance. The scrape runs server-side.

Step 3 — Pick an output format

Excel (.xlsx), CSV or JSON. Excel is the default for community managers and customer-success folks. JSON is what you want when the data has to land in a CRM, a BigQuery warehouse, or a Looker dashboard. Same columns either way.

Step 4 — Run the export

Click Export. The job runs in the background — close the tab if you want, the file lands in your account history and you'll get an email when it's ready. Long-running InDemand campaigns with tens of thousands of comments take a few minutes. Smaller ones return in seconds.

Step 5 — Bulk-export multiple campaigns

Auditing your own portfolio, or scouting Indiegogo competitors? Paste a list of URLs into the bulk input, one per line. You get back one file per URL, bundled in a single ZIP — not a merged spreadsheet. Each campaign stays in its own file, which matters when you want to diff them side-by-side without comment IDs colliding.

Step 6 — Open in Excel and start pivoting

Drop the file in, turn row one into a filter, and you can finally answer the questions you couldn't last week — what's our reply latency, what % of comments came from confirmed backers, did sentiment shift the day we announced the shipping delay. The data was always there. Now you can see it.

Inside the export — what fields you get

One row per Indiegogo comment (top-level or reply). The columns:

  • comment_id — Indiegogo's stable comment identifier.
  • parent_id — populated for replies, empty for top-level comments. Join comment_id ↔ parent_id to rebuild the thread tree.
  • backer_name — display name as shown on the campaign page.
  • profile_url — link to the commenter's Indiegogo profile, the cross-campaign join key for superfan analysis.
  • is_backer — Y/N flag for whether the commenter contributed to this campaign.
  • is_owner — Y/N flag for replies posted by the campaign owner.
  • is_team_member — Y/N flag for replies from official team members or collaborators.
  • comment_text — the full comment body, line breaks preserved.
  • created_at — UTC timestamp of when the comment was posted.

Common workflows for crowdfunding creators

Once the comments live in a spreadsheet, the workflows write themselves. The patterns we see Indiegogo creators run on repeat:

  • Backer-only inbox. Filter is_backer = Y, sort by created_at descending. That's your queue. Public visitors can wait.
  • InDemand transition window analysis. Indiegogo's killer feature is post-funding sales, but the late cohort behaves differently from the early one — more shipping questions, higher refund risk. Slice by created_at at the InDemand cutover date and compare the two cohorts. Snapmaker, Anker's PowerCore launches, and dozens of others all show the same pattern: late InDemand backers expect a finished product and they expect it now.
  • Owner-reply rate. Pivot on is_owner, divide by top-level comment count. One number, tracked weekly. A falling reply rate during fulfilment is the moment refund tickets start landing.
  • Refund-risk early warning. Run a keyword count over comment_text for "refund", "scam", "where is", "chargeback", "cancel" on a 7-day rolling window. A sustained spike — especially paired with a falling owner-reply rate — is the earliest signal of a fulfilment crisis. Don't wait for it to hit your support inbox.
  • Cross-campaign superfan map. Export comments from every Indiegogo and Kickstarter you've run, union the profile_url columns, deduplicate. Profiles appearing on three-plus campaigns are your free pre-launch ambassadors.
  • Team-member audit. Use is_team_member vs. is_owner to see which replies came from the founder vs. the team. Useful for retros — and for spotting the weeks you, the founder, vanished from the wall.

Plan limits & API access

Free accounts cap at 100 comments per job — enough to evaluate a campaign or sanity-check the schema. Paid plans raise the cap: Personal hits 5,000 per job, Premium 50,000, Business 250,000, which covers even the longest-running InDemand campaigns in one pass. Full breakdown at exportcomments.com/pricing.

If you want a recurring refresh — say, nightly during InDemand — or the data piped straight into your own systems, the REST API returns the same schema as JSON and fires a webhook the second an export finishes.

FAQ

  • Do I need to log into Indiegogo to export comments?
    No. The exporter works on any public Indiegogo campaign without you signing in to Indiegogo. You only need an exportcomments.com account.
  • Does this work for InDemand campaigns that are still selling post-funding?
    Yes. As long as the campaign page is publicly viewable, the exporter pulls every comment posted before, during and after the funding window — including the InDemand period.
  • Are threaded replies included?
    Yes. Every reply is its own row with parent_id linking back to the comment it replied to, so you can rebuild the full thread in Excel or in your own database.
  • How do I tell which comments are from backers vs. random visitors?
    The is_backer column is a Y/N flag taken from the contributor badge Indiegogo shows next to the commenter's name.
  • Can I export multiple Indiegogo campaigns at once?
    Yes — paste a list of URLs in the bulk input, one per line. You get back one file per URL bundled in a single ZIP, not a merged sheet, so each campaign's data stays clean.
  • Is there a row limit per export?
    Yes, it depends on your plan: Free 100, Personal 5,000, Premium 50,000, Business 250,000. The exporter shows the cap before the job runs.