# Frenzy documentation

Source: https://frenzy.zone/docs/

Frenzy helps a campaign owner record who joined through a referral, which action qualifies, and how a reward was reviewed. Participants get a campaign link and a private view of their referrals. The local beta has real campaign and reward records; account providers, AI assessments, subscriptions, and payouts depend on configuration.

<a id="choose-your-guide"></a>

## Choose your guide

- [Marketer guide](https://frenzy.zone/docs/marketers/): create an offer, record qualifying actions, review rewards, and understand your budget.
- [Participant guide](https://frenzy.zone/docs/participants/): join, share, follow captures, choose consent, and appeal a hold.
- [Self-hosting guide](https://frenzy.zone/docs/operators/): run the installation, manage credentials and data, and distinguish local testing from live services.

<a id="how-frenzy-works"></a>

## How the referral loop works

1. The owner creates a campaign with an offer, a qualifying action, a direct referral reward, and caps.
2. A signed-in participant joins and receives a unique public referral link and code.
3. Another signed-in participant joins using that code. Frenzy retains that first attribution.
4. The owner records a real qualifying action with a unique event reference.
5. The direct referrer's reward enters review. The owner approves, holds, or rejects it with a reason.
6. A payment remains separate: a reviewed record does not transfer money.

These records persist on the installation. The landing-page receipt, rank badges, forecasts, and animated graph use illustrative data.

<a id="what-is-available"></a>

## What is available

Local beta capability boundaries

| Area | Available behavior | Boundary |
| --- | --- | --- |
| Campaigns and referrals | Create an offer, pause or end it, join, share a link, retain attribution, opt in to a leaderboard. | Accounts require configured sign-in or explicit local test access. |
| Qualification and review | Record unique actions, inspect direct rewards, approve, hold, reject, and record appeals. | The owner must verify that the action actually happened. Approval is not a payout. |
| Profile evidence | Consent to public Bluesky profile collection and optional audience review; remove saved evidence. | Submitted handles do not verify ownership. Other networks need approved connections. |
| AI and forecasts | Audience assessment can use consented evidence and explicit audience, offer, and review policy. | AI needs a configured service. Campaign forecasting is unavailable without supported service and enough outcomes. |
| Billing and payouts | Configured checkout, subscription evidence, invoices, and cancellation use the payment service. | No fake paid subscription, bank balance, or payment confirmation. Destination setup and provider proof remain required. |
| Beta and quotes | Requests are saved for review. | No email is automatically sent and no payment is taken. |

Start in the [campaign workspace](https://frenzy.zone/app) or open a campaign owner's `/c/:campaign` link. Check the workspace's integration status before relying on a provider feature.

<a id="read-scores-correctly"></a>

## Read scores and forecasts correctly

An **influence score** is an assessment index out of 100. An **expected capture count** estimates how many people a recruit may bring in over a stated window. A score of 80 is not 80 expected signups.

Facts describe observations. Judgements assess evidence. Forecasts estimate future outcomes. None establishes a causal effect, and missing evidence stays missing. The local referral reward uses the campaign's fixed direct reward; the sample audience-weighted formula is not silently applied to a real ledger.

<a id="find-an-answer"></a>

## Find an answer

Search all guides with the field at the top or use the topic list. Common questions include [reward states](https://frenzy.zone/docs/participants/#reward-statuses), [starting a campaign](https://frenzy.zone/docs/marketers/#campaign-quickstart), and [profile consent](https://frenzy.zone/docs/participants/#social-data-and-consent).

Each topic has a shareable address. The guides and campaign pages remain readable without JavaScript. Copy and device sharing are optional browser enhancements. Use your browser's print command to save a guide as a PDF.