Managing Multiple Kickstarter and Indiegogo Campaigns: An Agency Guide

Picture a small agency running multiple Kickstarter and Indiegogo campaigns at once, three clients deep. A hardware startup, a board game publisher, a clothing brand. Three unrelated businesses, three campaigns, three creator accounts.

And every one of those accounts is logged into from the same two office laptops, by the same four people, using passwords the clients emailed over.

From the agency's side that's just how the work gets done. From the platform's side it looks like one operator controlling several creator accounts, which is precisely the pattern its trust-and-safety team is paid to look at. If one of those campaigns gets reported, the others can get pulled into the review with it.

Most guides answer this by reaching for the browser: make the accounts look unrelated and hope nobody joins the dots. That's the wrong fix. Kickstarter's own rules list overlapping creator and backer accounts and inaccurate account information as grounds for suspension, and Indiegogo's terms cover the same ground — check its current wording. And it doesn't even touch the agency's actual problem. The real problem is that the agency is logging into accounts it shouldn't be logging into at all.

Which is a contract and onboarding problem. Not a browser one.

Below: who should own what, how the platforms expect agencies to get access, why they link accounts, what to do when something gets flagged, and where separate browser profiles genuinely earn their keep.

Who Should Own the Campaign Account

Start here, because almost every later problem traces back to it.

The creator account should belong to the client. The person or company whose project it is verifies their identity, connects their own bank details, receives the funds, and is responsible to backers. Kickstarter and Indiegogo both put that responsibility on the campaign owner, and the identity and payout checks are built around it.

Agencies sometimes set up the account in their own name "to save the client the hassle." Don't. You get a verification that doesn't match the business behind the project, a payout routed through someone who isn't the creator, and an ownership fight waiting to happen. Picture the engagement ending badly while your agency is still the legal face of someone else's project, still the name on the identity check, still the account the payout runs through. That is not a conversation you want to have with a lawyer listening in.

So the rule for an agency is simple: one creator account per client, owned by the client. Your agency has zero creator accounts of its own for client work.

How Agencies Get Access to Kickstarter and Indiegogo Campaigns

Both platforms have a built-in way to let other people work on a campaign without sharing the owner's login.

Kickstarter lets a creator add collaborators to a project. Each collaborator uses their own Kickstarter account and gets permissions set by the creator, covering things like editing the project, handling backer messages and comments, and managing fulfilment. Access can be withdrawn when the engagement ends; check Kickstarter's help centre for the current steps.

Indiegogo lets a project creator invite collaborators by email and give each one roles. A role can cover a single project or every project that creator runs, and the creator can edit or remove it at any time. Each collaborator uses their own account.

Permission options and their names change over time, so check each platform's help centre for the current list before you write your onboarding SOP. Read the source page, not someone's blog post about the source page.

The shape, though, is the same on both: the client invites your people, your people log in as themselves.

What this gets you:

Nobody holds the client's password, so nobody trips their login verification or locks them out.
Every change to the campaign is attributable to a named person.
When the engagement ends, the client removes your team and there's nothing to untangle.

And here's the bit that surprises people. An account manager who's a collaborator on six client projects isn't running six accounts. They're running one, with access granted by six owners. That's the legitimate version of "multiple crowdfunding accounts," and it needs no tricks at all.

Why Kickstarter and Indiegogo Link Accounts

It helps to understand what Kickstarter and Indiegogo are protecting against, because it explains why "make the accounts look unrelated" is a losing game, and on Kickstarter a rules violation, not a clever workaround.

Crowdfunding runs on social proof. A campaign that funds on day one gets featured, gets press, gets more backers. So there's an obvious temptation to fake it: back your own project from accounts you control, seed the comments with puppets, grab early-bird tiers through extra accounts. Real backers then decide based on numbers that aren't real.

There's also plain fraud: creators who were removed coming back under a new name, stolen cards used to pledge, rewards that were never going to ship. Regulators do pay attention here. In 2015 the US Federal Trade Commission brought its first crowdfunding case, against the creator of a Kickstarter board game project who took backers' money and didn't deliver. Misleading backers is a consumer-protection matter, not just a platform-rules one.

So platforms look for accounts that are controlled by the same person or group. The signals available to any website are broad: payment instruments, payout and bank details, identity verification, shipping addresses, contact details, IP addresses, device and browser characteristics (including things like TLS fingerprints such as JA4), and behaviour over time. Exactly which ones Kickstarter or Indiegogo weigh, and how, isn't public, and I'm not going to guess.

Here's the part that matters for an agency. A shared device by itself is a weak, explainable signal. An agency whose staff are named collaborators on client projects has a perfectly ordinary explanation for touching several campaigns. An agency that's logging into client creator accounts with shared passwords, or holding accounts in its own name, looks a lot more like the thing the platform is hunting for.

Scrubbing the connection doesn't make you legitimate. It makes you look like someone with something to hide, and platforms reserve the right to suspend the accounts involved. The honest setup is also the lowest-risk one, which is a rare and pleasant thing to be able to say about compliance work.

The Backer Side: One Account Is Enough

This topic often drifts into "professional backers" running several profiles, so let's be direct. One backer account can back as many projects as you want. Reviewers and collectors don't need a second one, and the usual reasons for wanting extra backer accounts are on the wrong side of the line:

Getting around per-backer limits on early-bird or limited tiers. Those limits exist so more people get the deal. Extra accounts take slots from real backers, and creators running a pledge manager can and do cancel duplicates.
Inflating a campaign's numbers with pledges or comments from accounts you control. That's manipulation, and it's the core thing the platforms prohibit.
Re-registering after your account was suspended. That's evading enforcement, and it typically turns a temporary problem into a permanent one.

If you review products and want to cover a campaign, contact the creator for a press kit or review unit. That's how the legitimate version works.

Where Separate Browser Profiles Actually Help

So if the platforms already give agencies collaborator access, what's an antidetect browser for in this workflow? Fair question. The answer is everything around the campaign page.

A campaign doesn't live only on Kickstarter. Each client also has a pre-launch landing page, an email platform, ad accounts, social pages, a pledge manager, maybe a store for late pledges. Your team touches all of it, for every client.

One named profile per client. In JustBrowser you'd create a profile called something like "Client – Board Game Co" and keep that client's tool logins, cookies and sessions inside it. Open the profile and you're in their world; close it and nothing leaks into the next client's. Each profile carries its own consistent browser identity across 40+ parameters, so a client's tools see the same stable browser every time rather than a parade of different devices.

Name them properly on day one. Names like "Client", "Client 2" and "Client 2 (new)" are exactly as useful as they sound at 7am on a launch day when someone asks which one has the ad account in it.

The practical wins are boring and real. Nobody schedules a launch-day email from the wrong client's account. One client's pixels and cookies don't get mixed into another's sessions, so attribution stays cleaner. And when a contractor leaves, you revoke their profile access instead of hunting for saved passwords on their laptop.

Where a tool has a real agency access model, use it first — swapping one out for a browser profile is inventing work for yourself. Meta's business tools let a client give your agency partner access to their ad account, and Google Ads manager accounts let you work across client accounts under your own login. The browser profile is for keeping your team's sessions organised, not for replacing the platforms' own permission systems. (For the setup basics, our profile best-practices checklist covers naming, storage and sharing habits.)

Team access without passwords. JustBrowser has role-based permissions (owner, admin, member, viewer), and direct shares can be view-only or launch. Team seats are free, and a seat can run the profiles shared with it but can't create its own, sync its own, or use the API. For an agency that's a sensible default: a junior account manager can launch the client profiles they're assigned to and nothing else.

Geo and device QA. If a client is targeting backers in the UK, Germany and Australia, you want to see what those people see: the landing page's currency and shipping copy, cookie banners, the ads that actually serve in each market. Give a QA profile a proxy in the country you're checking, with timezone and language to match. JustBrowser doesn't include proxies (it's bring-your-own), but each profile can route through its own HTTP, HTTPS or SOCKS5 proxy, and the proxy tester shows the exit IP, country, city and timezone so you know the check is genuine. The ad verification workflow goes deeper on this.

Light automation. The local REST API and CDP support let you drive profiles from Playwright, Puppeteer or Selenium. A reasonable use here is screenshotting your client's own landing pages across your QA profiles before launch. If you're scheduling that kind of job, running a browser pool from Airflow shows one way to structure it. If you're tempted to automate anything on the crowdfunding platforms themselves, read their terms on automated access first.

What JustBrowser is not for here: hiding the relationship between accounts from Kickstarter or Indiegogo. If that's the plan, no browser makes it legitimate, and payment, payout and identity checks sit outside the browser anyway.

When Something Goes Wrong

A client's account gets a verification request

Have the client complete it; the details have to match the owner. If your staff keep triggering these prompts, they're logging in as the client, and should move to collaborator access.

A campaign or account is suspended or flagged

Whichever it is, be specific. Say who runs the project, how the agency is involved, and attach what proves it: business registration, identity documents, your agency agreement if it helps. If your staff were collaborators, say so; it explains the shared activity.

Don't open a new account to relaunch the same project. Re-registering after enforcement is evasion, it breaks the platform's terms, and it usually ends in a permanent ban. If the appeal fails, the client's realistic options are to accept the decision or take legal advice if they believe the platform got it wrong.

A backer's card is declined

Point them to their bank and the platform's payment help pages. Repeated attempts with different cards on the same pledge look like card testing, so cycling cards is the single worst thing you can suggest. One card, one bank, one phone call.

Next Steps

Running multiple Kickstarter and Indiegogo campaigns comes down to ownership and access first: the client owns the account, your people are collaborators, nobody shares a password. Then organise the work around the campaign with one profile per client, launch-only shares for staff, and country-specific QA profiles.

If your agency is sending paid traffic to clients' pre-launch landing pages and the referral numbers look off, bot clicks are a separate problem from anything above; ClickzProtect is built for filtering that traffic. And for measuring those landing pages without third-party cookies, JustAnalytics is a privacy-first option.

None of this is glamorous. It's mostly onboarding paperwork and naming conventions, and chasing a client for their business registration certificate at 11pm the night before a launch is genuinely miserable work that nobody thanks you for.

Do it anyway. It's the version where a platform review ends with an explanation instead of a closed account.

Frequently Asked Questions

Can an agency run Kickstarter or Indiegogo campaigns for several clients?

Yes, and the clean way is for each client to own their own campaign account, verified in their own name or their company's, with the agency's staff invited in using the platform's own access features: collaborators on Kickstarter, collaborators on Indiegogo. Each staffer logs in with their own personal account. Nobody shares the client's password, and the agency never holds the creator account.

Is it OK to create extra accounts to back a campaign or claim more limited rewards?

No. Backing your own campaign from other accounts fakes momentum and misleads real backers, and using several accounts to grab more early-bird slots than a per-backer limit allows takes those slots from other people. Platforms treat both as manipulation, and creators can cancel duplicate pledges. One account can back as many projects as you like, so a genuine backer or reviewer never needs a second one.

What should I do if a client's campaign account is suspended?

If the platform's trust-and-safety team contacts the client about a campaign, have the client answer quickly and fully. On Kickstarter that contact comes before a suspension, and a project that has been suspended cannot be reinstated. If an account is restricted or a project is declined, use the platform's own appeal or support route from the affected account, led by the account owner (the client), and check its help centre for the current process. Explain who runs the campaign, how the agency is involved, and include documents that prove ownership, such as business registration and identity details. Don't open a new account to relaunch the same project. Platforms treat that as evading enforcement, and it usually turns a restriction you could have explained into a permanent one.

Where does an antidetect browser fit for a crowdfunding agency?

In keeping each client's tools apart for your own team: their ad accounts, email platform, pledge manager and landing-page logins live in one named profile per client, which you can share with staff at launch-only permission. It's also useful for checking how pages and ads render from the countries you're targeting. It is not a way to hide a link between accounts from Kickstarter or Indiegogo; that runs against Kickstarter's rules, so check Indiegogo's current terms too.

Does JustBrowser include proxies for geo testing?

No. JustBrowser is bring-your-own-proxy. Each profile can route through its own HTTP, HTTPS or SOCKS5 proxy, and the built-in proxy tester shows the exit IP, country, city and timezone so you can confirm a geo check is really coming from where you think it is.

Try JustBrowser

Antidetect browser on a custom Chromium engine with native C++ integration, not an extension, and patched on every upstream release. Real C++ engine patches at the canvas / WebGL / audio / font / screen layer, so 40+ identity parameters are consistent rather than faked. Local REST API + CDP for Playwright, Puppeteer and Selenium. Role-based team sharing with free seats. Windows x64 and macOS (Apple Silicon). $9.99/month or $99.99/year. 7-day free trial, card required — cancel any time in the seven days and you are not charged. Unlimited profiles, unlimited cloud sync, unlimited team seats.

Get started → · How it differs from Multilogin / GoLogin / AdsPower