FRENFrenzy 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.
Choose your guide
- Marketer guide: create an offer, record qualifying actions, review rewards, and understand your budget.
- Participant guide: join, share, follow captures, choose consent, and appeal a hold.
- Self-hosting guide: run the installation, manage credentials and data, and distinguish local testing from live services.
How the referral loop works
- The owner creates a campaign with an offer, a qualifying action, a direct referral reward, and caps.
- A signed-in participant joins and receives a unique public referral link and code.
- Another signed-in participant joins using that code. Frenzy retains that first attribution.
- The owner records a real qualifying action with a unique event reference.
- The direct referrer's reward enters review. The owner approves, holds, or rejects it with a reason.
- 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.
What is available
| 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 or open a campaign
owner's /c/:campaign link. Check the workspace's integration
status before relying on a provider feature.
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.
Find an answer
Search all guides with the field at the top or use the topic list. Common questions include reward states, starting a campaign, and profile 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.