> 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/best-practices/recruiting-affiliates.md). # Recruiting Affiliates Who you let into your program matters more than how many people apply. The short answer: recruit for **audience fit** rather than follower count, keep your registration form **short but filtering**, and treat the pending queue as a real gate. A focused roster of partners whose audience overlaps your customers will out-earn a crowd of casual sign-ups every time. This article covers how to attract and screen affiliates, then links the Bloop settings that run it. There are two ways affiliates join in Bloop: you add them manually, or they self-register through your form. Most programs use both — a handful of hand-picked partners to start, then an open form once the offer is proven. ### Recruit for fit, not volume A relevant partner with a small, engaged audience usually drives cleaner sales than a large but mismatched one. Before chasing reach, ask whether a candidate's audience plausibly buys what you sell. * Start with people who already love your products — past customers, creators who have mentioned you, niche publishers in your category. * Lead recruitment with the concrete benefit: your commission rate and what a partner can realistically earn. * Hold your richer rates for proven performers so there is a reason to keep promoting, rather than opening the top tier to everyone. ### Make the registration form sell, then filter The registration form is your first impression and your first screen. It has to convince good partners that joining is worth their time while collecting only what you will actually use to vet and pay them. * Keep it short. A long, demanding form scares off the creators and customers you most want. * Lead the copy with the benefit — surface your commission with a dynamic variable so applicants see the upside immediately. * If you must filter (a niche, an audience size, a portfolio link), collect it with a single-choice or file-upload field rather than free text, so applications are easy to compare at a glance. Build and style this in [the affiliate registration form](/affiliate-program/branding/registration.md). ### Use the pending queue as a gate Self-registered affiliates arrive as **pending** and cannot earn until you approve them (see [affiliate statuses](/affiliate-program/affiliates.md#affiliate-statuses)). That queue is your control point — review applicants for fit, not just to clear the backlog. You can approve or reject in bulk, and Bloop sends the matching status email automatically, so screening a batch of applications is quick. ### Onboard so partners actually start An approved affiliate who never promotes is no better than a rejected one. After approval, make sure they have what they need: their referral link, any discount coupon, and a clear sense of what to share. You can preview exactly what an affiliate sees with "login as" before launch, which is the easiest way to confirm their portal and links work. ### Set it up in Bloop * Add, approve, reject, and export affiliates in [Managing affiliates](/affiliate-program/affiliates.md). * Build the application form in [the affiliate registration form](/affiliate-program/branding/registration.md). * Hold top performers on a higher-rate campaign — see [Best practices: a commission structure that scales](/best-practices/commission-structure.md). ### Related * [Best practices: a commission structure that scales](/best-practices/commission-structure.md) * [Managing affiliates](/affiliate-program/affiliates.md) * [Referral program vs affiliate program](https://bloop.plus/blog/referral-program-vs-affiliate-program/) --- # 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/best-practices/recruiting-affiliates.md?ask=&goal= ``` `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.