> 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/measuring-and-optimizing.md).

# Measuring & Optimizing

A program you do not measure is a program you cannot improve. The short answer: read your analytics from outcomes back through the funnel to find the one weak step, change a single thing to fix it, and prove the change with an A/B test before you keep it. This article explains how to diagnose and optimize, then links the Bloop tools that do the work.

Optimization is a loop, not a launch task: measure, find the gap, change one lever, test, bank the winner, repeat. Done steadily, a program compounds; done by guesswork, it churns.

### Read the funnel backwards

Your [analytics dashboard](/referral-program/analytics/analytics.md) moves from outcomes (who joined, who converted, how much revenue followed) back through behaviour (who saw the offer, who shared, on which channels). Reading it in that order makes the gap announce itself.

| Symptom in the data                      | Likely cause                            | Lever to pull                                       |
| ---------------------------------------- | --------------------------------------- | --------------------------------------------------- |
| Many impressions, few shares             | The incentive feels too weak to mention | Reward type or value                                |
| Many shares, few successful referrals    | The referee offer or eligibility is off | Referee discount, minimums, or audience             |
| Strong first orders, thin repeat revenue | A retention problem, not acquisition    | Reward type (store credit), post-purchase follow-up |

Two ratios are worth watching above the rest: **successful referrals to shares** (do shares actually convert) and **subsequent referral revenue** (do referred customers stick). Revenue totals look good on a slide, but these ratios are what you can act on.

### Change one lever at a time

When the data points at a step, resist fixing everything at once. Change the single variable with the most money riding on it — usually the reward value or the referee discount, which move conversions more than wording or layout. Changing one thing keeps the cause of any improvement unambiguous.

### Prove it with an A/B test

Guesswork is the most expensive way to set a reward, because a too-small and a too-generous discount look identical from the outside. Bloop's [A/B testing](/referral-program/ab-testing.md) splits new participants between your current setup (control) and one edited copy, then declares a winner from real conversions and can promote the winning settings to your live campaign automatically.

* Test the highest-stakes change first — reward value, then referee discount, before anything smaller.
* Change one thing per test.
* Let it run until both groups have real volume.
* Bank each winner before starting the next test.

### Keep affiliate spend tied to real revenue

For affiliate programs, optimization is also about not paying for revenue that evaporates. Build a [sales review](/affiliate-program/sales.md) rhythm aligned with your refund window — approving weekly, after the typical return period — so you rarely pay commission on an order that later comes back. Skim for anything unusual, like a sudden spike from one affiliate, before bulk-approving the rest.

### Set it up in Bloop

* Diagnose with the [referral analytics dashboard](/referral-program/analytics/analytics.md).
* Validate changes with [A/B testing](/referral-program/ab-testing.md).
* Keep affiliate payouts honest in [Affiliate sales review](/affiliate-program/sales.md).
* For the wider playbook, see [referral program best practices](https://bloop.plus/blog/referral-program-best-practices/).

### Related

* [Best practices: launching your referral program](/quick-start/launch-checklist.md)
* [Best practices: choosing the right referral reward](/best-practices/choosing-rewards.md)
* [Referral program best practices](https://bloop.plus/blog/referral-program-best-practices/)


---

# 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/measuring-and-optimizing.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.