Adding your campaign team
Own logins instead of a shared password — invitations, seats by plan, roles, and what a downgrade does to your team.
Plain-English guides to the things campaigns actually get stuck on — connecting your donation processor, moving your domain and email, forms and texting consent, and getting found in search. Still deciding whether Electbase fits your race? That's the FAQ. Can't find an answer? Contact us.
Own logins instead of a shared password — invitations, seats by plan, roles, and what a downgrade does to your team.
A brand guide that can't go stale, a voice guide that shapes your copy, and palette and logo concepts — including what the logo review does and doesn't cover.
Editing is private, publishing is the commitment — the pages each plan produces and the checks that run before anything goes live.
How to pick a donation processor for your campaign — ActBlue, Anedot, Donorbox, Raise the Money, and Numero compared by fees, embeds, and who they serve.
Why publishing is gated, the two ways to confirm your committee, and what Electbase does and doesn't check about your disclaimer.
Who can embed ActBlue forms, where your hosted form link lives, and how to sync donation data back to your supporter list automatically.
Embed codes, hosted pages, webhooks, and the honest trade-offs between Anedot and Donorbox.
Connect a custom domain, keep your email working, and set up SPF, DKIM, and DMARC before your first blast — all in plain English.
Four question types, up to 12 per form, supporter filtering, and how answers reach your CSV export.
Events on your site, RSVPs with guest counts, an email on every signup, and the CSV you take to the check-in table.
Electbase pings Bing and Yandex automatically on every publish. Google takes one manual, five-minute step in Search Console.
The GTM container and its Google terms are yours — the PII and consent obligations your campaign must meet.
Free until you publish, plan changes, and the post-election option most campaigns miss — hibernate keeps the site up while the tools go quiet.
Who gets the email, what's in it, and where every submission lives once it arrives.
Why the texting-consent checkbox is unchecked and optional, what the disclosure text means, and what 10DLC registration asks for.
Expenses, receipts and hand-entered contributions — a visibility tool with a CSV exit ramp, not books of record.
Every publish kept permanently, autosaves for a while — and restoring is itself undoable and never publishes on its own.
More guides on the way