Your Join Page Is a Landing Page: Designing an Affiliate Application That Converts

You have spent months on your product pages. Headlines tested, photography reshot, reviews surfaced, the buy button moved four times. Then a creator with fifty thousand engaged followers clicks "join our affiliate program" and lands on a form with your logo, three fields and no reason to fill them in.

The join page is a landing page. Its visitor is deciding whether to give you their time and their audience, which is a bigger ask than a $40 purchase, and it gets a fraction of the attention. This post treats it the way you would treat any other conversion page: what goes above the fold, how to present the offer, which proof matters to creators specifically, what the form should ask, and how to build a fully custom version in Reveshare when the default layout is not enough.

1. Who is on this page and what they are asking

Three kinds of people land on a join page, and they are asking different questions.

The customer who just bought. They arrived from the thank-you page or an email. Their question is "is this easy and is it worth it?" They will not read past the first screen.

The creator evaluating you. They found you on the marketplace, in a search, or through outreach. Their questions are "what is the rate, does this brand convert, and will I be embarrassed to promote it?" They will scroll, and they will look for reasons to leave.

The professional partner. A publisher or agency. Their questions are "what are the terms, what is the attribution, and who do I talk to?" They will read everything and then email you anyway.

A join page that serves all three puts the customer's answer at the top, the creator's answers in the middle, and the partner's answers at the bottom with a contact line.

2. Above the fold

The first screen has to do three jobs in the time it takes to decide whether to scroll.

3. Presenting the offer without scaring anyone

The offer block is where most join pages either overwhelm or underwhelm. The structure that works is one big number, then the supporting terms in a short list.

15%

This is the pattern: the headline rate as the biggest thing on the block, and the supporting facts as one calm sentence. The reader gets the number in under a second and the terms in under five.

Under the big number, list only what a creator needs to decide:

• The customer discount. "Your audience gets 10% off with your code." This is what converts, and creators know it.
• The ladder, if you have one. "Rates rise to 18% and 22% as your sales grow." Two numbers, no thresholds. The thresholds are for the dashboard.
• How attribution works. "You get credit for 30 days after someone clicks your link, even if they forget your code." This single sentence is the most reassuring thing on the page.
• How and when you pay. "Paid monthly via PayPal or bank transfer." Name the methods.
• Who it is for. One line that filters: "For creators with an active audience in fitness" or "Open to every customer."

Leave out anything that is only relevant after approval: the exact tier thresholds, the full terms, the disclosure rules. Link to them, do not print them.

4. Proof that works on creators

Product-page proof is reviews and star ratings. Join-page proof is different, because the visitor is not asking "is this product good" but "will this program work for me". Three kinds land.

Other creators. A row of a few partner avatars or handles, with permission, says "people like you are already here". It is the single most effective element on a join page and most brands do not have it.

A payout or earnings figure. "Our partners earned over $X last quarter" or "Top partners earn $Y a month". Real numbers, rounded down. If you are too new to have them, skip it rather than inventing one.

Conversion evidence. Creators care whether your store converts, because their commission depends on it. A line like "4.8 stars from 2,000 reviews" or "one in five people who click a partner link buy" tells them their effort will not be wasted.

What you do not need: press logos, founder bios, a mission statement. Those persuade customers. Creators want to know that the deal is real and the store converts.

5. The form

The application form should be short enough that a customer finishes it and specific enough that a creator's answers tell you something.

Payment details and tax information belong after approval, at the first payout. Asking for them on the application is the most common reason a join form is abandoned by someone who would have been a good partner.

6. Building a custom join page in Reveshare

The default join page in Reveshare takes your brand colours, logo, showcase products and program copy and produces a clean page without any design work. For most brands that is enough. When you want a page that looks like part of your site rather than a form, the custom join page editor lets you build one from your own HTML and CSS.

1. Ask for the editor to be switched on

   Custom join pages are enabled per brand by the Reveshare team. Once enabled, a Join Page tab appears under Customizations with an HTML pane, a CSS pane and a live preview.

2. Write the page with tokens for the live values

   Instead of hard-coding your brand name, logo, banner or products, use tokens that are filled in per program when someone visits. The brand name, logo, banner and hero image, your website and social links, and your showcase products are all available, so one page can serve every program and stays correct when you change a product.

3. Watch the linter

   The page is checked as you type. Anything outside the join page spec is removed and listed: scripts, unsupported tags, links to hosts other than your website, your socials and Reveshare, images from anywhere except your brand storage and the Shopify CDN, fonts from anywhere except Google Fonts. What you see in the preview is exactly what will ship.

4. Publish, and keep the history

   Publishing creates a numbered version. Every publish is kept, so you can roll back to a previous version if a redesign underperforms. The published page is served inside a sandboxed frame, so nothing in it can touch the rest of the portal.

5. Put the application above the fold anyway

   The custom page wraps the application, it does not replace it. Design the page so the offer and the apply action are visible on the first screen, and the story, proof and details follow. A beautiful page with the form three screens down converts worse than the default.

7. Testing it

Treat the join page like any landing page: pick one metric, change one thing, wait for enough traffic.

The metric is applications per visitor. Not follower quality, not approval rate, just whether people who land on the page apply. Quality is a separate question answered by the form fields and your approval setting.

Changes worth testing, roughly in order of impact:

1. The headline. Audience plus benefit, versus program name.
2. Showing the rate above the fold versus below it. Show it. But test it if you doubt it.
3. Adding creator proof. A row of partner handles usually moves the number more than any copy change.
4. Form length. Removing one field at a time.
5. Button label. "Get your code" versus "Apply".

If you have a post-checkout invite, watch that traffic separately. Customers arriving from the thank-you page behave differently from creators arriving from the marketplace, and a change that helps one can hurt the other.

Conclusion

The join page is where someone decides whether to lend you their audience, and it deserves the same care as the page where someone decides whether to buy. Put the audience and the benefit in the headline, show the rate as one big number with the terms beneath it, prove that other creators are already here and that the store converts, and ask for as little as you can on the form. When the default layout is not enough, build a custom page with tokens for the live values, keep the apply action on the first screen, and test one thing at a time.

---

Frequently Asked Questions