Skip to content
Analytics & scaling

OnlyFans Metrics to Track Every Week: 6 Checks

DylanFounder, Aura ManagementPublished Updated 5 min readPromotionAbout the author
On this page

The OnlyFans metrics to track every week are six: qualified visits, paid starts, revenue by type, eligible renewals, delivery promises, and hours worked. Reviewing those six over one consistent seven-day window turns scattered numbers into decisions, because every movement gets attached to a question or an action. Keep the count, time zone, and gross-versus-net basis identical from week to week.

Which six numbers cover the operation, and nothing else?

Start with attributable visits, new paid starts, receipts by revenue type, actual continuation for eligible subscribers, and hours spent producing or supporting the account.

Add unanswered questions, complaints, and delivery delays as a weekly quality check, because those three predict next month's renewals before the revenue does. Every metric needs its count and period written beside it — unique visits per seven days, not just 'visits'. If a source cannot reliably produce a number, mark it unavailable instead of estimating it silently. Good records make this possible: they help you monitor the progress of the business and identify sources of income (IRS: Recordkeeping), and weekly receipts double as return evidence, because net self-employment earnings of $400 or more carry a filing requirement (IRS: Self-employed individuals tax center).

  • Attributable visits: unique people, labeled by the channel that sent them.
  • New paid starts: first-time paying subscribers this week, not total fans.
  • Receipts by revenue type: subscriptions, renewals, tips, and priced messages, kept separate.
  • Eligible renewals: qualifying payments divided by subscribers who actually faced the decision.
  • Hours: producing, editing, messaging, and administration, so effort carries a number.

How do you compare this week against last week fairly?

Use the same seven-day window, time zone, and gross-versus-net basis before reading anything into a change.

Separate a campaign spike from a normal week, and note price changes, outages, or a new release beside the affected dates. A fictional increase from $400 to $600 is 50%, but that statement needs the actual dollar change and its context: one unusual $200 purchase could explain all of it. Numbers only compare cleanly when the inputs were produced the same way.

Weekly comparison inputs to hold constant
InputKeep constantWhy it matters
Window and time zoneSame seven days, same clockA shifted window invents or hides a spike
Revenue basisGross or post-fee, labeledMixing bases exaggerates growth
Known eventsLogged beside the datesPrice changes and outages explain jumps
Unusual purchasesFlagged, not averaged awayOne $200 order can carry a whole week

How do you check renewals without double counting?

Count only subscribers who actually faced a renewal decision inside the window, then divide the qualifying payments by that eligible group.

A renewal setting, a current subscriber total, and a completed payment are three different measures, and only the completed payment among eligible subscribers is renewal evidence. Keep the timing rule identical every week so the percentages stay comparable. The full eligibility rules and a worked example sit in how to calculate churn and renewal rate.

  1. Step 1

    List the eligible group

    Everyone whose paid period reached a continuation point inside the window.

  2. Step 2

    Count qualifying payments

    Completed payments from that group, not renewals switched on in settings.

  3. Step 3

    Divide and date it

    Payments over eligible, recorded with the week and the timing rule used.

  4. Step 4

    Compare like cohorts

    Only against weeks with similar offers, prices, and acquisition sources.

What separates a traffic problem from a conversion problem?

Read the six numbers in sequence, because each one hands its output to the next.

If qualified visits fell, the question is discovery, not content. If visits held but paid starts fell, the page is failing to convert the people who arrived. If starts held but continuing receipts fell, retention and delivery are the suspects. Two components can move in opposite directions while the total looks calm, which is why the weekly note records each one separately.

Weekly readings and where they point
ReadingMore likely explanationNext check
Visits down, starts steadyDiscovery weakenedRelabel and retest the channel that slipped
Visits steady, starts downPage fails to convertReread the promise a stranger sees first
Starts steady, renewals downPaid experience or deliveryCheck promises against what shipped
All stable, hours risingOperating inefficiencyTime one routine task and simplify it

How does the review end in one useful action?

A short review might read: qualified visits were steady, starts fell, and the public profile now describes an outdated release schedule.

The action is to fix the promise and observe comparable traffic, not simply publish more. Record the owner, the change, and the next review date beside the note. Most weeks need one action, not five, because a single change is the only way to know what moved the following numbers. When the same gap survives three weeks, it usually belongs in a structured test rather than another weekly note — the revenue plateau diagnosis is that format.

  • State the week's three movements in one sentence each.
  • Name one owner and one change, with the next review date.
  • Keep the raw records so a corrected figure can be traced later.
  • Leave the bigger structural test for the quarterly plan, not the Friday note.

Why do raw records outrank the summary chart?

Preserve the underlying records so any total can be rebuilt and a corrected number traced to its source.

Summaries drift: imports fail, categories get renamed, and a filter silently hides rows. Ten minutes spent reconciling one week's revenue against the source records tells you whether the whole history is trustworthy. Once the sheet and the source disagree, stop explaining trends and isolate the discrepancy first — the revenue dashboard guide covers the views that keep this organized.

  1. Step 1

    Pull one month's total

    From the sheet as displayed, including any filters a reader would hit.

  2. Step 2

    Rebuild from source

    Sum the raw transaction records for the same period and basis.

  3. Step 3

    Reconcile the difference

    Every dollar of gap gets a cause: missing import, refund, or formula.

  4. Step 4

    Fix at the source

    Correct the import or formula, then re-issue the summary with a dated note.

Frequently asked questions

How many metrics should a creator review each week?

Six is enough for most accounts: qualified visits, paid starts, revenue by type, eligible renewals, delivery promises, and hours worked. A longer list collects numbers without decisions. Each metric still needs its definition and period written down before it earns a column.

Should weekly numbers be gross or after fees?

Pick one basis, label it, and stay on it. Gross shows what fans paid; the post-fee figure shows what reaches you. Switching bases between weeks makes every percentage meaningless.

What time window should the weekly review use?

The same seven days and time zone every week, such as Monday to Sunday. A rolling window that shifts makes week-over-week comparison unreliable, because the periods no longer contain the same kinds of days.

Do I need software to run a weekly review?

No. A dated sheet with six columns and a notes field covers most accounts. What matters is the consistency of definitions and the raw records behind them, not the tool that displays them.

What is a normal renewal rate for a small account?

There is no verified industry benchmark worth planning around. Compute your own renewal rate among eligible subscribers each week and treat the week-over-week direction as the signal, not an outside average.

How long should a weekly review take?

About twenty minutes once the sheet exists: reconcile one total, read the six numbers, write one action. Reviews that take hours usually mean a missing definition or a broken import, not a bigger task list.

Build your next step

Continue with a related guide

Sources and further reading

How this guide is produced: Editorial policy · Methodology · Authors · About · Disclaimer

Need support with your next step?

Choose promotion channels deliberately, respect their rules, and measure which traffic becomes subscribers — then read the numbers to find the bottleneck before adding spend or workload.

Keep learning

Related guides