Creator business

Count Paying Fans Once Across Your Paid Offers

Build a simple payment ledger to count repeat supporters once across memberships and workshops, while keeping follower growth and page clicks separate.

AI generated editorial image of hands grouping matching account tokens beside two trays of payment discs in a ceramics studio.

Someone joins your membership, then buys a workshop through your profile page. That is two payments, but not two paying fans. Count each reliably identifiable payer once within a stated reporting period, regardless of how many offers they support. Build that count from successful payment records, not followers or clicks. If you cannot reliably match accounts across services, report each service’s payer accounts separately rather than presenting their sum as a unique person total.

Choose labels that describe your records

Follower growth, page activity and paid support answer different questions. Keep them separate from the start. YouTube, for example, distinguishes subscribers from its monthly audience of unique viewers. Neither measure tells you who paid you. Likewise, someone appearing in a membership audience does not automatically establish a successful payment.

Use successful payments for completed payment records and unique payer accounts for distinct accounts with qualifying payments. Reserve unique paying people for a count where duplicate accounts have been reliably resolved. Your label should describe the evidence, not the level of certainty you would like to have.

Choose a completed reporting period and use the same boundaries for every offer. This count means paid during the period, not currently has membership access. Avoid calling it active members, especially when your offers include workshops, downloads or other purchases without ongoing membership.

Build one small payment ledger

Create a spreadsheet with one row per payment record. Keep follower totals on a different sheet so that audience size never becomes an input to your payer count. Start with the destination service’s payment history rather than purchase notifications or your memory of who attended.

Include these columns: service, payment ID, payer ID, payment date, offer, payment status, refund status, internal supporter key and match evidence. The service identifies where the record came from; the payment ID helps prevent importing the same transaction twice.

The internal supporter key is your own reference, such as FAN014. Once you establish that two accounts belong to the same supporter, give them the same key. In match evidence, record the reason briefly, such as supporter confirmed both accounts. Keep personal details out of the summary you share.

  • List every paid offer included in the report and its payment service.
  • Collect payment records covering the same reporting period for each service.
  • Check repeated payment IDs within each service before counting anything.
  • Add supporter keys only where the available records support the grouping.

Decide which payments qualify

Write your counting rule before calculating the total. A practical convention is to include successful payments with a positive amount, exclude pending and failed attempts, and exclude fully refunded payments as of the report’s preparation date. Keep refund status visible so you can explain later changes.

Patreon’s payment history distinguishes successful, declined and refunded payments. Those distinctions matter: a declined attempt is not another supporter, and a payment notification alone is not a substitute for checking the final record. Apply your stated convention consistently across the services you use.

Apply exclusions to payments first, then count the remaining payers. If someone’s workshop payment was fully refunded but their membership payment still qualifies, they remain one payer. This preserves their valid support without counting the refunded purchase.

Resolve repeat accounts before adding totals

First group repeat payments within each service using a stable payer or member ID where available. Stripe supports associating payments and subscriptions with an existing Customer object. When that record is reused, it can help group payment activity; it does not establish identity across unrelated services.

Next review overlap between services. Prefer an established internal supporter record or a match the supporter has confirmed. Matching display names and social handles are clues, not sufficient evidence on their own. Leave uncertain matches unresolved rather than collecting extra personal information just to produce a cleaner total.

There is a useful tradeoff here: separate account totals are less compact than one headline number, but more accurate when overlap is unknown. Report membership payer accounts and workshop payer accounts separately, with overlap not established. If only some matches are resolved, do not present the remaining combined count as unique people.

  • Group qualifying payments by stable account ID within each service.
  • Review potential overlap using existing records or supporter confirmation.
  • Assign a shared supporter key to confirmed matches.
  • Keep unresolved accounts separate and describe the remaining overlap accurately.

Work through a membership and workshop example

This numerical example is illustrative. A music creator links to a listening club and a songwriting workshop from their profile page. During one completed month, the club records 12 successful payments from 12 accounts. The workshop records eight successful payments from seven accounts because one account paid twice.

Three workshop accounts are reliably matched to club supporters. There are also two failed attempts and no refunds. Successful payments total 20: 12 plus eight. The reconciled payer count is 16: 12 club accounts plus seven workshop accounts, minus the three confirmed overlaps. The failed attempts add nothing.

A useful summary is: During the month, 16 distinct identified payers completed 20 qualifying payments across the listening club and workshop. Three supported both offers. This recognises repeat support without treating additional payments as additional people.

Do not describe those 16 as new fans unless earlier records establish that they are first time payers. With incomplete history, first observed paying is the more accurate label. Any follower growth belongs in a separate statement.

Keep profile page activity beside the ledger

Unflaggable.bio analytics record page views and outbound clicks, with individual link IDs and referrer hostname and utm_campaign where available. Standard UTM parameters are forwarded to destinations. Use those records to understand which paid offer links received clicks, not to populate your supporter ledger.

The distinction is simple: page records show activity, payment records establish qualifying payments, and reliable identity matches connect payments to supporters. A click is not a confirmed sale. Missing referrers and campaign tags remain unknown, and a click and payment occurring in the same month do not prove they belong together.

Finish your report with separate lines for audience change, qualifying payments and identifiable payers. Add whether overlap across services is resolved, partly resolved or unknown. Save the counting rule with the ledger so the next report uses the same definitions.

Put your next idea on the page.

Explore 20 creator page layouts, learn about independent domains, or compare the creator plans.

Start my free trial