> For the complete documentation index, see [llms.txt](https://docs.bloop.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloop.plus/affiliate-program/branding/registration.md).

# Registration Form

The registration form is the first impression your program makes on a potential affiliate. It has to convince good partners that joining is worth their time and collect the information you need to vet and pay them. Get the balance wrong and you feel it: a long, demanding form scares off the creators you most want, while a bare email-only form lets in low-quality applicants you'll spend hours screening.

Bloop gives you a drag-and-drop builder to decide which fields to collect, how they're labelled, which are required, and how the page looks. You'll find it under the affiliate **Branding** tab. Every store starts with a working default form, so you can launch right away and refine once applications start arriving.

> **Best practice:** Keep the form short and let the copy do the recruiting. Lead with the benefit — your commission rate and what affiliates can earn — using a dynamic variable like `{{campaign_amount}}`, then ask only for fields you'll use to approve and contact partners. If you need to filter (a niche, an audience size, a portfolio link), use a single-choice or file-upload field rather than free text so applications are easy to compare. See [Managing affiliates](/affiliate-program/affiliates.md) for how submissions flow into review, and [recruiting affiliates](/best-practices/recruiting-affiliates.md) for how the form fits your wider recruiting funnel.

### What makes a registration form convert

Every field you add is a small tax on the applicant — another thing to read, decide, and type before they can join. Some of that tax is worth paying because it earns information you'll genuinely use. **Every field has to justify its place by answering "what decision does this help me make?"**

Two failure modes to avoid:

* **Too long.** Asking for a phone number, mailing address, tax ID, and open-ended essays up front is almost all premature. You don't need a payout address before you've approved anyone, and free-text answers are slow to read and easy to fake. Long forms have lower completion rates, and the people who abandon are disproportionately the busy creators you most want.
* **Too thin.** An email-only form admits everyone — including bots and people with no relevant audience. You pay for that convenience later in screening time.

The form that works asks for the **few facts that change an approve-or-decline decision**, and nothing else. For most stores that's a name, an email, one screening question, and a terms agreement. Collect payout details *after* approval on the affiliate's profile — see [Affiliate settings](/affiliate-program/settings.md) for where those payment fields live.

### Default fields

A new form ships with three required fields:

| Field      | Type         | Required |
| ---------- | ------------ | -------- |
| First name | `first_name` | Yes      |
| Last name  | `last_name`  | Yes      |
| Email      | `email`      | Yes      |

These are the program's core identity fields. You can rename their label or change placeholder text, but you can't make them optional or delete them. Everything else is yours to add, reorder, or remove. For many programs these three fields plus a terms checkbox are the whole form.

### Adding and editing fields

Open the field editor to add a new field or change an existing one. Each field has a **field type**, a **label**, and a **required** toggle. The available field types are:

| Field type      | Internal value      | What it collects                                     |
| --------------- | ------------------- | ---------------------------------------------------- |
| Text            | `text`              | A single line of free text                           |
| Multiple choice | `multiple_checkbox` | A set of checkboxes the applicant can multi-select   |
| Single choice   | `radio`             | A set of radio options where the applicant picks one |
| File upload     | `file`              | A file the applicant attaches                        |
| Terms checkbox  | `checkbox`          | A single agreement checkbox linked to your terms     |

A few rules the builder enforces:

* **Labels must be unique.** Two fields can't share the same label (case-insensitive).
* **Required fields can't be left blank.** Labels and option values are validated before a field is saved.
* **Only one terms checkbox.** Once you add a terms checkbox, the option is disabled for additional fields.
* **Multiple-choice fields are always optional.** The required toggle is disabled for `multiple_checkbox`.

#### Choosing the right field type

The field type decides how comparable your applications are. Free text is flexible but slow to scan; closed answers (radio, checkbox) turn a judgment call into something you can sort in seconds.

| You want to...                                                                             | Use this type                         | Why                                                                             |
| ------------------------------------------------------------------------------------------ | ------------------------------------- | ------------------------------------------------------------------------------- |
| Capture a name, social handle, or website URL                                              | Text                                  | One open line is fine when the answer is short and you'll read every one anyway |
| Ask which single category an applicant fits (niche, platform, audience-size band)          | Single choice (`radio`)               | One answer, easy to compare and filter across applicants                        |
| Let an applicant pick several that apply (channels they post on, product lines they cover) | Multiple choice (`multiple_checkbox`) | Multi-select, always optional — good for "nice to know" without adding friction |
| Collect a media kit, portfolio, or proof of audience                                       | File upload (`file`)                  | One attachment beats a wall of pasted links and is quick to open during review  |
| Get explicit agreement to your program terms                                               | Terms checkbox (`checkbox`)           | A single, link-backed agreement you can point to later; only one per form       |

The pattern that scales: turn any screening question you'd otherwise ask in free text into a **single-choice** field. "What's your audience size?" as an open box gives you "a lot" and "10k ish"; the same question as radio bands (`Under 1k / 1k–10k / 10k–50k / 50k+`) gives you something you can actually sort on.

#### Field-specific settings

Different field types expose different settings:

* **Text fields** add a **placeholder** to hint at what to type.
* **Multiple choice** and **single choice** fields let you add, edit, and remove individual **options**.
* **File upload** fields take a placeholder such as "Choose a file".
* **Terms checkbox** fields take a **term name** and a **term link**, so the checkbox reads like "I agree to the Terms" with a clickable link to your policy.

### Reordering fields

Grab any field and drop it into a new position to set the order applicants see on the page. Lead with easy, low-commitment fields (name, email) and put screening questions after — once someone has typed their name, they're far more likely to finish.

### A worked example: a lean screening form

Say you run a skincare store and want creators with a real audience. You need three sortable facts, not essays. Here's a form that recruits and screens at the same time:

1. **First name** *(default, required)*
2. **Last name** *(default, required)*
3. **Email** *(default, required)*
4. **"Where do you post?"** — **multiple choice**, options `Instagram / TikTok / YouTube / Blog / Other`. Optional — tells you the channel mix without blocking signup.
5. **"Audience size"** — **single choice**, required, bands `Under 1k / 1k–10k / 10k–50k / 50k+`. One tap, fully comparable across every applicant.
6. **"Link to your media kit or profile"** — **file upload**, optional. Lets serious creators prove themselves without forcing casual joiners.
7. **Terms checkbox** — required, term name "Affiliate Program Terms" with a link to your policy page.

Seven fields, only four required, and every one earns its place. See [Managing affiliates](/affiliate-program/affiliates.md) for how these show up in review.

### Page content

Beyond the fields, you control the wording around the form:

* **Header** — a title and sub-title that introduce the program.
* **Form labels** — the submit button text, the "Already have an account?" line, and the sign-in link.
* **Benefits** and **How it works** — bulleted lists that sell the program to prospective affiliates.
* **Thank-you page** — the title, body, and button shown after a successful submission.

Drop dynamic variables into your copy so the page reflects each program's real numbers. Supported variables include `{{store_name}}`, `{{email}}`, `{{cookies}}`, and `{{campaign_amount}}` — for example, "Earn a {{campaign\_amount}} commission on every sale."

You can also toggle the **information section** (the benefits/how-it-works panel) on or off for a leaner page. Lead the header with the commission, use the benefits list to answer "what's in it for me?", and let `{{campaign_amount}}` quote the real number so the offer feels concrete.

### Styling the form

The form's appearance is controlled by four collapsible style groups:

* **General** — button color, font family, heading and content font sizes, which sections to display, and square or rounded borders.
* **Header style** — title and sub-title colors and font sizes.
* **Information style** — background and text colors for the benefits panel (shown only when the information section is on).
* **Form style** — background, text, and submit-button colors for the form itself.

Match these to your store theme so the application page feels like part of your brand. For the affiliate-facing portal that comes after signup, see [Portal style](/affiliate-program/branding/portal-style.md).

### Common mistakes to avoid

* **Making the form a job application.** Phone number, full address, tax details, and long-answer questions up front — none of it changes whether you approve someone. Collect payout details after approval, not on the public form.
* **Screening with free text.** Asking "tell us about your audience" in a text box gives you answers you can't compare or filter. Use a single-choice field with bands so you can sort applicants in seconds.
* **Selling nothing.** A bare form with no benefits copy and no commission number gives a prospect no reason to join. Lead with the offer — use `{{campaign_amount}}` to quote the real rate.

### When and why to revisit your form

* **Approval rate is very high and quality is mixed** → your screen is too loose. Tighten a single-choice screening question so weaker applicants self-identify.
* **Applications are trickling in** → the form may be too long or the benefits copy too thin. Cut a field or two and make the commission number prominent with `{{campaign_amount}}`.
* **You keep emailing applicants for the same missing detail** → that detail belongs on the form. Add it as the simplest field type that captures it.
* **You're scaling from a handful of partners to many** → free-text fields that were fine to read by hand now bottleneck review. Convert them to single- or multiple-choice so applications stay sortable at volume.

The goal: collect exactly the facts that drive an approve-or-decline call, sell the opportunity clearly, and keep everything else off the page. A short, sharp form recruits more good partners *and* makes them easier to vet — see [recruiting affiliates](/best-practices/recruiting-affiliates.md) for how to drive the right people to it.

### Related

* [Getting started with affiliates](/quick-start/getting-started-1.md) — overview and onboarding.
* [Managing affiliates](/affiliate-program/affiliates.md) — review and approve applications that come through this form.
* [Portal style](/affiliate-program/branding/portal-style.md) — brand the dashboard affiliates see after they join.
* [Affiliate settings](/affiliate-program/settings.md) — where post-approval payout details are collected.
* [Recruiting affiliates](/best-practices/recruiting-affiliates.md) — the playbook for driving the right partners to this form.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bloop.plus/affiliate-program/branding/registration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.