# Share and earn

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

Join a campaign you understand, share it with people who will benefit, and follow each reward through review. Frenzy Field works in a browser. The local beta records joins, referral links, qualifying actions, and reviewed rewards; a payment still needs an actual supported provider.

<a id="before-you-join"></a>

## Check the campaign before you join

A campaign belongs to the business running its offer. Read the public page at `/c/:campaign`. Its rules should identify the owner, a contact route, who may join, what action qualifies, the direct reward, the cap, and review conditions.

- **Eligibility:** check location, age, customer status, and other rules in the offer.
- **Qualification:** a click and a qualifying signup or purchase are different things.
- **Rewards:** a stated amount still needs a real qualifying action and owner review.
- **Payment:** check the payout method, timing, requirements, and any fees before treating a reward as cash.

An illustration, a badge, or an owner subscription plan is not your campaign agreement. If the offer has no owner contact or clear payment rules, ask before sharing.

<a id="joining-and-your-link"></a>

## Join and get your link

1. Open the campaign page and read the offer.
2. Sign in using the configured account service. Social profile assessment is a separate choice.
3. Enter your campaign display name and the referral code, if someone referred you.
4. Choose whether your display name may appear on the leaderboard. The default is private.
5. Join, then open [Your links](https://frenzy.zone/me) for your public link and referral code.
6. Check that the link opens the correct offer before posting it.

Your public referral link cannot sign someone into your account. Keep private account access and local test invitations separate from the public link. The local beta does not send sign-in emails; local invitations are explicit one-use testing links.

Joining again does not replace your first recorded attribution. A paused or ended campaign blocks new joins.

<a id="sharing-responsibly"></a>

## Share with people who will benefit

Copy the full link from Your links, or use device sharing when your browser supports it. The referral code also appears there. QR-code generation is not available in this beta.

Explain why the product fits the person. Disclose that you may receive a reward, describe the offer accurately, and follow the community's promotional rules. Ask before sending repeated messages.

- Do not create fake accounts, use bots, manufacture qualifying activity, or disguise a self-referral.
- Do not promise a bonus, discount, or payout that the owner has not published.
- Do not share private sign-in invitations or account credentials publicly.
- Do not edit or remove the referral code from a shared URL.

Sharing creates an opportunity for a qualifying referral. It does not by itself establish eligibility for payment.

<a id="captures-and-attribution"></a>

## Understand captures and first attribution

A **capture** is someone attributed to your referral when they join the campaign using your code. It does not necessarily mean they completed the qualifying action or that money is due.

[Captures](https://frenzy.zone/me/captures) shows your direct referrals, campaign, join time, and reward status. You do not get another participant's full account or private credentials.

The first campaign join fixes attribution. Frenzy does not promise first-click or last-click cookies, a tracking duration, automatic credit without a code, or cross-device matching. Another person's later join with your code does not override their existing attribution.

For a dispute, keep the campaign identifier, approximate time, and original link. Ask the owner to review the recorded action rather than collect someone else's private account information.

<a id="social-data-and-consent"></a>

## Choose profile collection and AI review separately

[Profile consent](https://frenzy.zone/me/connect) lets you supply a public Bluesky handle for a campaign. Fetching that profile and recent public posts requires collection consent. A supplied handle does **not verify that you own the account**; provide only a profile you control or are authorized to submit.

AI audience review is a separate optional consent choice. If selected, the owner may submit profile facts and post text to the configured assessment service. Joining a campaign alone does not provide this consent.

You can remove the saved connection, evidence, and stored assessment from this page. Existing campaign actions and reward records remain separate; withdrawal does not claim to erase data already held by a provider.

X, Instagram, Facebook, LinkedIn, and TikTok require approved account connections and are not available here. Frenzy does not collect social passwords. A stale, private, or unavailable source stays missing evidence rather than receiving an invented low score.

<a id="understanding-your-score"></a>

## Read influence and forecasts in their own units

### Influence score: an assessment index

A score out of 100 combines a campaign's evidence and assessment criteria. Observed facts, such as a follower count, differ from model judgements, such as campaign fit. A judgement is an estimate with context and confidence, not a verdict on your personal worth.

### Forecast: future outcomes

“4.2 captures in 30 days” is an expected count, not 4.2 out of 100 and not a promise of four referrals. Forecasts require a supported service and enough completed campaign outcomes. Missing support stays unavailable.

The landing-page sliders and forecast band use illustrative data. The current direct referral reward is the fixed amount in the campaign's offer; it is not secretly multiplied by the sample AI formula.

<a id="ranks-and-leaderboards"></a>

## Choose whether to appear on the board

Your links includes a leaderboard preference for each campaign. Opting in makes your display name and attributed referral count visible on `/board/:campaign`. Leave it off to keep your name off the public board. You can change the preference later.

The board does not show private email, account credentials, or a guaranteed earnings amount. A count indicates attributed joins, not completed payments.

Lurker, Stalker, Hunter, Apex, and Whale are proposed visual progress markers. Their illustrations do not establish implemented rank multipliers or automatic bonuses. A badge alone is not a payment promise.

<a id="reward-statuses"></a>

## Follow the actual reward states

Local beta reward states

| State | Meaning |
| --- | --- |
| Pending | A qualifying action has created a direct reward awaiting owner review. |
| Approved | The owner accepted the reward within the campaign budget and cap. It is not yet paid. |
| Held | Review pauses the reward; read the reason and ask for clarification. |
| Rejected | The owner declined it with a reason. You may record an appeal. |
| Transferred | A supported provider transfer may move funds into a connected provider account. This is not proof of bank settlement. |
| Paid | A verified provider confirmation supports the payment record. Approval alone cannot create this state. |

Your links separates waiting review, approved but unpaid, and provider-confirmed payments. A large local ledger total is not a bank balance. For example, a reviewed $10 reward is still unpaid until the appropriate provider evidence is recorded.

<a id="receiving-payouts"></a>

## Check the payment requirements

[Rewards & payouts](https://frenzy.zone/me/payouts) shows recorded amounts, review reasons, and any verified provider payment reference. It also reports payout availability on this installation.

Bank details, tax forms, recipient onboarding, withdrawal controls, and a payment schedule are not collected by this beta page. The owner must publish requirements and configure a supported provider before promising payment. Never send financial credentials through an appeal.

Buying an owner plan does not make a participant payout available. Check the difference between approved, transferred to a provider account, and settled to a bank. A returned page or success-looking button is not settlement proof.

<a id="holds-and-appeals"></a>

## Ask for review of a specific reward

1. Open Captures and read the held or rejected reward's reason.
2. Check the relevant rule and whether the qualifying action is confirmed.
3. Use the appeal form to explain what should be reviewed. Keep it factual and relevant.
4. Include a useful event reference or approximate time. Redact private information.
5. Reload the record to follow the owner's later decision.

An appeal is saved on your own held or rejected reward. It does not automatically approve it or promise a reply deadline. A shared network, unavailable profile, or model warning does not by itself establish wrongdoing.

Do not create another account to bypass a hold. Ask the campaign owner using the contact route published in the offer.

<a id="privacy-and-account-controls"></a>

## Understand what stays in the records

The installation retains campaign membership, attribution, qualifying actions, reward decisions, and appeals so the referral loop can be checked. Owners and reviewers see their own campaign records; participants see their own data and direct referrals. Public leaderboard names require opt-in.

Profile collection and AI consent are scoped to a campaign organization. Removing evidence stops that saved connection from being used by future requests and removes its stored assessment. Existing campaign records and provider-held information are separate.

Automatic account export, deletion, and scheduled retention are not implemented. Contact the installation operator about access, correction, removal, backups, and any record needed to resolve a reward. The [privacy notice](https://frenzy.zone/privacy/) explains the local beta's data and unresolved public operator details.

<a id="troubleshooting-and-support"></a>

## Find the next useful step

**I cannot sign in.**

 Check whether account sign-in is configured. Local participant invitations are private, one-use testing links and are not emailed automatically.

**I cannot join.**

 Check that the campaign is active, you are signed in, and the referral code is valid. A repeated join preserves existing attribution.

**A referral is missing.**

 Check the full link, code, campaign, and the person's first campaign join. Credit is not inferred from clicks alone.

**My profile is unavailable.**

 Check collection consent, the handle, network availability, and whether the service returned usable evidence. Missing evidence is not a low score.

**My reward has not arrived.**

 Check its review status, reason, provider availability, and the owner's payment requirements. An approved amount is not proof of payment.

Use the campaign owner's published contact route. Frenzy has no working participant support inbox or guaranteed response time in this beta. Recording-library integration is deferred.
