> 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.md).

# Branding

The six places a customer meets your referral programme, and which one to set up first.

Your referral programme has no single home. It appears in several places on your storefront and in your customers' inboxes, and each surface catches a different person at a different moment. A theme sets the look across all of them; the individual surfaces decide where the programme shows up at all.

### The surfaces

| Surface                                                                         | Who it reaches             | When to reach for it                                                       |
| ------------------------------------------------------------------------------- | -------------------------- | -------------------------------------------------------------------------- |
| [Branding themes](/referral-program/branding/themes.md)                         | Everyone                   | First. A theme is the complete look applied across every surface below     |
| [Widget panel, launcher and referee popup](/referral-program/branding/popup.md) | Any visitor                | Your always-on placement, and the one most customers actually meet         |
| [Referral page](/referral-program/branding/page.md)                             | Anyone you send a link to  | When you need a permanent URL for a newsletter, menu item or social bio    |
| [Post-purchase widget](/referral-program/branding/post-purchase.md)             | A customer who just bought | The highest-intent moment you get — enthusiasm peaks on the thank-you page |
| [Customer account extension](/referral-program/branding/account-extension.md)   | Logged-in repeat buyers    | Steady, long-tail referrals from the people most likely to refer           |
| [Sharing channels](/referral-program/branding/social-sharing.md)                | Referrers about to share   | Once a referrer is ready to share, this decides where the referral travels |

### Where to start

Set the [theme](/referral-program/branding/themes.md) first — everything else inherits it. Then turn on the [widget](/referral-program/branding/popup.md) and the [post-purchase widget](/referral-program/branding/post-purchase.md): together they cover the always-on case and the peak-intent case, which is most of the value. Add the rest when you have a specific reason.

Relying on one placement is the most common reason a programme underperforms — see [making your referral program visible](/best-practices/program-visibility.md).

### Related

* [How to create and configure a referral campaign](/referral-program/campaign.md) — the campaign each theme belongs to.
* [How to control how a reward reads to customers](/referral-program/reward-display.md) — the words the reward renders as on every surface.


---

# 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.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.