> 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/referral-program/branding/page.md).

# Referral Page

Give your programme a permanent URL you can link from anywhere.

A referral page gives your programme a permanent URL you can put anywhere — a menu item, a newsletter, an order email, a social bio. Unlike the on-site widget it's always there, and Bloop builds it as a real Shopify page on your own domain, so it inherits your theme and you style it in the theme editor like any other section.

Open **Branding**, pick your [theme](/referral-program/branding/themes.md), choose **Customize**, and open the **Referral page** card. It's marked **Recommended** for a reason: alongside the post-purchase widget, it carries most of a mature programme's traffic.

> **Best practice:** Keep the default `referral-program` handle and add the page to your main menu or footer before launch. A page nobody links to gets no traffic, however good it looks.

### When you need one

Reach for the page whenever the share has to start somewhere other than your storefront: a link from a newsletter, a "Refer a friend" menu item, a social bio, search traffic, or a programme with rules worth reading properly. If you only need to catch existing customers while they browse, the [widget](/referral-program/branding/popup.md) alone is enough.

### Create the page

The **Setup** tab walks three steps:

1. **Create your page.** Give it a page title and a URL handle — Bloop creates the page in your Shopify store at `/pages/<handle>`. Handles must be unique; if one is taken, Bloop asks for another. Copy the finished URL straight from the field.
2. **Customize design.** **Edit in theme editor** opens the page in Shopify's theme editor, where the Bloop app block does the styling (below).
3. **Set up your page.** Add it to your **main menu** or **footer**, or embed the block into any existing page from **Edit theme**, then start sharing the link.

Use **Update page** to change the title or handle later, and **View page** to see it live.

> Avoid renaming the handle after launch. A changed handle breaks every link you've already shared — in newsletters, emails and bios you can't edit.

### Design it in the theme editor

The referral page is built from three sections — **Main** (the join-and-share block), **Guide** (how it works) and **Reward** (what each side gets). The app block's settings control all three:

| Setting                            | What it does                                                                                    |
| ---------------------------------- | ----------------------------------------------------------------------------------------------- |
| Section visibility                 | Hide the main, guide or reward section independently                                            |
| Section order                      | Four arrangements, so you can lead with the guide instead of the form                           |
| Heading size                       | Small, medium or large, per section                                                             |
| Text / primary / background colour | Per section, so the guide can sit on a tinted band between two white ones                       |
| Padding top and bottom             | 0–100 px per section                                                                            |
| Image (main section)               | Turn it on, pick the image, put it **left** or **right**, and set its width between 30% and 70% |
| Border radius                      | 0–10 px on the main block                                                                       |
| Custom CSS                         | For the last detail the fields don't cover                                                      |

Two of these do most of the work. **Section order** decides what a cold visitor reads first — lead with the guide when your programme needs explaining, lead with the main block when the reward speaks for itself. And the **main section image** is the difference between a form and a page: a product shot at 40–50% beside the signup block gives the page something to look at while it explains itself.

### Write the content

The **Content** tab holds the page's wording, split into **Main**, **Guide** and **Reward**, and saved per language. Switch languages with the selector, or leave automatic translation on for the campaign and write only your default language — see [campaign language settings](/referral-program/campaign.md#name-language-and-translation).

What converts:

* **A headline that names the reward.** "Give a friend 15% off, get $10 when they buy" beats "Join our referral program".
* **One obvious action.** A single button; competing calls to action lower the share rate.
* **A three-step guide.** At most. Anything longer reads as terms and conditions.
* **Both rewards stated plainly**, in money or percentage terms, in the Reward section.

### Common mistakes to avoid

* **Building the page and never linking to it.** Menu, footer, newsletter, order emails — give it entry points on day one.
* **A vague headline.** Name the reward for both sides in the first line.
* **Renaming the handle after sharing it.** Choose it once and leave it.
* **Hiding sections you should reorder instead.** If the guide is getting in the way, move it below the main block rather than turning it off.

### Next steps

* Style the on-site widget in [Widget panel, launcher and referee popup](/referral-program/branding/popup.md).
* Add more entry points with the [post-purchase widget](/referral-program/branding/post-purchase.md) and the [customer account extension](/referral-program/branding/account-extension.md).
* Make the programme easy to find — see [making your referral program visible](/best-practices/program-visibility.md).


---

# 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/referral-program/branding/page.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.