Asking your own questions on your forms

Where to find it

1. Open your campaign dashboard.
2. In the quick links row, choose Form questions — or go straight to /forms/your-site.

Each of your submission forms — contact, volunteer, events — gets its own list of extra questions there.

Which plans: Grassroots and up. If you're on Kickoff you can still see any questions and answers you already have — the plan only limits adding and editing new ones.

The four forms you can add questions to

Form	Where it appears
Sign-up form	Your Signup block and its /join page
Contact form	Your Contact block
Precinct recruitment	Your Precinct block
Yard sign requests	Your Sign Request block

If your site doesn't use one of those blocks, questions you add to it simply won't appear anywhere until you add the block.

The short sign-up form in your hero banner stays as it is — three quick rows, by design. It's the thing people fill in before they've decided to read the rest of the page, and every extra question there costs you sign-ups. Your custom questions go on the full sign-up form the hero's button scrolls down to.

The four question types

• Text — a single line. Good for open-ended answers.
• Multiple choice — a dropdown. You supply the options, one per line.
• Checkbox — a yes/no box.
• Date — a date picker.

You can mark any question required. That adds the browser's own "please fill this in" prompt.

Up to 12 questions per form

That's a deliberate ceiling, not a technical one. Response rates fall off sharply as forms get longer, and a 12-question sign-up form is already long.

Two things that surprise people

Changing a question later

Once you save a question, you can rewrite the question text freely. "Top issue" can become "What matters most to you this year?" any time — the answers you've already collected stay attached.

What you can't change is the column name shown underneath it. That's the heading the answers export under, and it's stamped onto every answer already stored. If we let you rename it, your existing answers would be orphaned from the question they answered. So it's set when you create the question and fixed after that.

Removing a question

Removing a question stops it being asked. It does not delete the answers.

Everyone who already answered keeps their answer, and it keeps appearing in your CSV export under the same column heading as before. That's on purpose: tidying up a form you've outgrown should never quietly destroy months of supporter data.

Finding people by their answers

On the Supporters page you can filter by any custom question — pick the question, type what the answer should contain, and the list narrows.

Two details worth knowing:

• The match is a contains match and ignores capitals, so "roads" finds "Roads and bridges".
• It searches everything a person has ever told you, not just their most recent submission. Somebody who said "roads" in March and "schools" in June shows up in both searches. That's usually what you want when you're building a list.

Leave the value box empty to find everyone who answered the question at all.

In your CSV export

Every custom question becomes its own column, after the standard ones. Where a supporter has answered the same question more than once, you get their most recent real answer — a later blank submission won't wipe out something they told you earlier.

Checkbox answers export as true / false, matching how the texting-consent column already works.

Changes go live when you publish

Adding or removing a question changes your site the next time you hit Publish, like any other edit. Until then your live forms keep asking exactly what they asked before.

A note on question names

A few column names are reserved — the standard fields (email, phone, first_name and so on), and anything that looks like it came from a connected Google account or a login token. If you pick one of those, you'll be asked for a different name while it's still free to change.