> 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/help/test-referral.md).

# Testing Referrals

A referral program is a chain of moving parts that only your customers normally see all at once — the sharing widget, the discount, the reward review period, and a sequence of emails. If any link is misconfigured, the cost lands at the worst moment: a referrer is paid the wrong amount, a friend hits a broken discount, or a customer receives an email with a blank coupon. Testing before launch is how you find those gaps while the only person affected is you.

The idea is simple: run one real referral against yourself, end to end, and watch each stage behave the way a customer would experience it. Place a small test order through your own referral link or code, follow it through the **Referral orders** view, confirm the referrer reward is issued correctly, and preview every referral email. This page walks through that dry run step by step.

> **Best practice — test the full chain before you go live.** A quick pre-launch checklist that catches most problems:
>
> 1. App embed on, with the [campaign](/referral-program/getting-started.md) live and at least one sharing method enabled.
> 2. One real test order placed and correctly attributed in [referral orders](/referral-program/management/orders.md).
> 3. The referrer [reward](/referral-program/rewards.md) issued at the right type and value, with any minimum requirement behaving as configured.
> 4. Every [referral email](/referral-program/emails.md) previewed, with template variables filling in.
> 5. Test data cleaned up and the review period restored before launch.

### Before you start

Make sure these are in place, or the test will not produce a result:

1. **App embed is on.** Bloop widgets only appear on your storefront when the app embed block is enabled in your theme. If it is off, your test referee will not see the popup, landing page, or sharing widgets. See [the FAQs](/help/faqs.md) for how to enable it.
2. **A campaign is live** with at least one sharing method on. Confirm your [referral methods](/referral-program/referral-methods.md) (link, code, or both) and your [referrer and referee rewards](/referral-program/rewards.md) are configured.
3. **The review period is known.** A referrer reward only issues after the **reward review period** set on the campaign. For a fast test, set it to `0` (instant) so you do not wait, then change it back before launch. See [referral orders](/referral-program/management/orders.md) for how the hold works.
4. **A test email inbox** you control, ideally one different from your store login, so you can play the part of a referred friend.

### 1. Become a referrer and get a sharing link or code

First you need a referrer with a link or code to share:

1. Join your own program the way a real customer would — through the on-site widget, the customer account extension, or the referral landing page.
2. Bloop assigns you a unique referral link and referral code. Note both.
3. If you enabled only one method, you will only see that one. To test both, turn both on in [referral methods](/referral-program/referral-methods.md) first.

> Tip: use a different name and email here than the one you will use as the referred friend, so Bloop treats them as two separate people and does not flag a self-referral.

### 2. Place a test order as the referred friend

Now act as the friend who was referred:

1. Open the referral link in a fresh browser (or use the referral code at checkout).
2. If you shared a **link**, enter the friend's email to receive the discount code, then apply it at checkout. If you shared a **code**, enter the code directly in the discount field.
3. Add the cheapest product you have and complete a real order through Shopify checkout.

Keep the test order small. To avoid spending real money you can create a draft order in Shopify and mark it paid, use a 100%-off internal discount, or use Shopify's test payment gateway (Bogus Gateway) in test mode. The order still needs to *complete* for the referral to register.

### 3. Confirm the order appears in Referral orders

Open the **Referral orders** view in Bloop and find your test order. Check:

* The order is linked to the right **referrer** (your step-1 identity).
* The status is correct. With a review period of `0` it should approve and issue the reward; with a delay it sits in **Pending** until the period passes. See [referral orders](/referral-program/management/orders.md) for the full status workflow.
* The order value and customer match what you entered.

If the order is missing, the most common causes are: the app embed is off, the order did not complete, or the referee used the same identity as the referrer (which Bloop blocks as a self-referral).

### 4. Test without a storefront purchase (optional)

If you cannot place a storefront order, you can still test the reward side by adding a referral order by hand:

1. In **Referral orders**, choose to add an order.
2. Enter a Shopify order number, amount, and the customer email.
3. Choose the referrer to credit, and optionally issue the reward immediately on save.

A manually added order is recorded as **Approved** and credits the referrer, so this is a quick way to verify reward issuance and the success emails without a real checkout. The full rules are in [referral orders](/referral-program/management/orders.md).

### 5. Verify the referrer reward was issued

Once the order is approved, confirm the reward actually reached the referrer:

* **Discount coupon** — a new Shopify discount code is created and emailed to the referrer.
* **Store credit** — the credit is applied to the referrer's Shopify customer account.
* **Cash** — the reward is tracked in Bloop for you to pay out manually (cash requires a payment method on your account).

Check the reward type, value, and any minimum requirement behaved as configured in [referrer and referee rewards](/referral-program/rewards.md). If you set a minimum-referees threshold, remember the reward only issues on the cycle (for example referee #5), not on the first order.

### 6. Preview the referral emails

You do not need to trigger every event to check your emails. Each referral email supports a test send:

1. Open the email under **Branding → Emails** (see [referral email notifications](/referral-program/emails.md)).
2. Send yourself a test.

The test uses sample values — a placeholder coupon like `BLOOP123example` and an example link — so you can preview the subject, body, button, and layout exactly as a customer would see them, without affecting a real referral. Walk through the invite, sharing, successful-referral, and reminder emails this way, and check your template variables (such as `{{ReferrerReward}}` and `{{ReferralLink}}`) fill in correctly.

### 7. Reset before you go live

After the dry run, undo your test data and settings:

* Reject or delete the test referral order so it does not skew your [referral analytics](/referral-program/analytics/analytics.md).
* If you set the review period to `0` for speed, set it back to the value you want for launch.
* Confirm the app embed stays **on** for real customers.

Once your test referral has flowed cleanly from share to order to reward to email, your program is ready to launch.

### Related

* [Getting started with referrals](/referral-program/getting-started.md) — the full setup flow this test validates.
* [Review and manage referral orders](/referral-program/management/orders.md) — statuses, holds, and manual orders.
* [Referrer and referee rewards](/referral-program/rewards.md) — what should be issued in step 5.
* [Referral email notifications](/referral-program/emails.md) — the emails you preview in step 6.


---

# 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/help/test-referral.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.