> 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/program-visibility.md).

# Program Visibility

The most common reason a referral program underperforms is not a weak reward — it is that customers never see it. The short answer: do not rely on a single placement. Combine an always-on **widget**, a **post-purchase prompt** at the moment of highest goodwill, a dedicated **landing page** you can link anywhere, and **email** so the program reaches customers who have left your store. This article explains how those surfaces work together, then links the Bloop branding settings for each.

Think of visibility as a system, not one button. Each surface catches customers in a different state of mind, and a referral that one surface misses, another can catch.

### The four surfaces and what each is for

| Surface                   | When it reaches the customer   | Its job                                                            |
| ------------------------- | ------------------------------ | ------------------------------------------------------------------ |
| Widget (launcher + panel) | While browsing your store      | An always-on invitation to share, recognised as part of your brand |
| Post-purchase popup       | The instant an order completes | Captures the buyer at peak goodwill, before they leave             |
| Referral landing page     | Anywhere you link to it        | A permanent home for the program, off-site and on                  |
| Email                     | After the customer has left    | Brings inactive customers back into the program                    |

Each surface lives under the **Branding** tab of your referral campaign, except email, which has its own module.

### Lead with the post-purchase moment

The single highest-converting moment is right after checkout, when the customer is happiest with you. Frame the prompt around the friend's reward — "Give friends a discount, and earn one yourself" — so sharing reads as doing a favour, not as you asking for one. Keep it to a sentence. Set this up in the [post-purchase popup](/referral-program/branding/post-purchase.md).

### Keep the widget quietly present

The on-site widget catches customers mid-browse. Treat the launcher as advertising and the panel as the product: keep the launcher visible on high-intent pages without nagging, and make the panel polished enough that sharing feels worthwhile. Brand it before you promote anything, because every on-site share begins here. Style it in the [referral widget and popup branding](/referral-program/branding/popup.md).

### Give the program a permanent home

A landing page is the one link you can drop into a menu, newsletter, order email, or social bio and trust to explain the program. Give it a clean handle and add it to your main menu or footer before launch — a page nobody can find converts nobody. Create it in the [referral page branding](/referral-program/branding/page.md).

### Use email to reach customers who have left

The widget and post-purchase prompt only work while a customer is on your store. Email closes that gap, pulling lapsed customers back into the program and reminding referrers about rewards before they expire. Configure the program emails in [referral emails](/referral-program/emails.md).

### Sequence it for launch

1. Brand the widget so it matches your store.
2. Turn on the post-purchase prompt — your highest-converting surface.
3. Publish the landing page and add it to navigation.
4. Switch on the referral emails.
5. Then start actively promoting, knowing every surface is ready.

### Set it up in Bloop

* [Referral widget and popup branding](/referral-program/branding/popup.md)
* [Post-purchase popup](/referral-program/branding/post-purchase.md)
* [Referral landing page](/referral-program/branding/page.md)
* [Referral emails](/referral-program/emails.md)
* For off-site promotion ideas, see [how to promote your referral program](https://bloop.plus/blog/how-to-promote-referral-programs/) and [the best referral widgets for Shopify](https://bloop.plus/blog/referral-widgets/).

### Related

* [Best practices: designing your referral offer](/best-practices/designing-your-offer.md)
* [Best practices: launching your program](/quick-start/launch-checklist.md)
* [How to promote your referral program](https://bloop.plus/blog/how-to-promote-referral-programs/)


---

# 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/program-visibility.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.