Report Creator Roster Growth Without Inflating Fans

Freeze the accounts before calculating growth

Start with a comparable account list: creator accounts that have both a starting and ending follower observation for the reporting window. Treat each platform account as its own row, even when several belong to the same creator.

Use consistent reporting cutoffs and save observation timestamps. An account measured midway through the period should not silently enter a full-period comparison. Mark missing observations rather than replacing them with zero.

Separate roster additions and departures from comparable growth. A newly signed creator brings an existing audience into your management scope; those followers were not necessarily gained during your work together. A departure similarly changes the managed total without proving an audience loss.

• Create columns for creator, platform account, starting count, ending count, observation timestamps and inclusion status.
• Calculate each account’s net change as ending count minus starting count.
• Sum starting counts and net changes for comparable accounts only.
• Calculate roster growth as combined net change divided by combined starting count, multiplied by 100.
• For a zero starting count, report absolute change and mark percentage growth not applicable.

Label the audience total by what it counts

Use the label “Combined follower/subscriber count, not deduplicated.” Someone following three managed accounts contributes three times to that sum. Without a reliable way to identify overlap, the total cannot tell you how many distinct people your roster reaches.

Keep subscribers and followers separate from active audience measures. YouTube distinguishes subscriber counts from estimated unique viewers, which describe people watching during a selected period. These measures answer different questions and should retain their own labels.

Add a short scope note beneath the audience table: “Totals cover the listed platform accounts; distinct people across accounts have not been established.” A combined count is useful for describing the audience under management, while per-platform rows preserve detail that the headline total hides.

Keep page activity in its own reporting block

Place creator-page views and outbound clicks beside audience growth, not inside it. In Unflaggable.bio, report recorded page views and outbound clicks, using each click’s link ID to distinguish support links from other destinations.

Campaign reporting is available: page views can record utm_campaign, clicks can include it, and standard UTM parameters are forwarded to destinations. Use available campaign values to group activity consistently. Leave missing tags and referrers marked unknown rather than assigning them to a likely source.

Label this block “Creator-page activity: recorded events.” Views and clicks are not deduplicated fans, and clicks are not confirmed sales. Even when followers, clicks and payments rise together, those totals do not establish a connected conversion funnel.

Google Analytics documents cross-device measurement through consistently assigned User-IDs. That illustrates why matching reporting windows alone cannot connect people across devices; it does not imply an Unflaggable.bio integration or purchase attribution.

Define payment support before counting it

For a payment-activity report, count distinct supporter IDs within each creator’s payment system that have at least one successful, non-zero payment during the window. Exclude fully refunded payments as of your reporting cutoff and disclose partial refunds separately. Record this definition so the next report uses the same rules.

This measures support paid during the period, not everyone holding paid access. Patreon’s active paid member count can include retrying payments, free trials, gifted memberships and cancelled memberships with access remaining. Do not substitute that headline membership count for a successful-payment count.

Use payment records with success status; Patreon’s member payment history includes payment status. Deduplicate qualifying records within the stated creator and system scope. Multiple successful payments by the same supporter should not inflate that creator’s supporter count.

When combining creators, label the result “Sum of creator-level paying-supporter counts.” A person supporting two creators can appear twice. If payment evidence is unavailable, report “Payment-confirmed supporter count unavailable” instead of estimating from clicks.

Work through a comparable roster example

The following figures are illustrative. Creator A starts with 10,000 followers and ends with 11,000: a gain of 1,000, or 10%. Creator B starts with 90,000 and ends with 90,900: a gain of 900, or 1%.

Together, the comparable accounts move from 100,000 to 101,900 followers. Roster growth is 1,900 ÷ 100,000 × 100 = 1.9%. Averaging the two account percentages produces 5.5%, which describes an equally weighted average account rate, not growth from the combined audience base.

Creator C then joins management with 50,000 existing followers. The ending managed count becomes 151,900, but calling this 51.9% audience growth would mix roster expansion with comparable account growth. Report the 50,000 separately as followers brought into management.

Suppose A and B also record 2,000 page views, 300 support-link clicks and 60 qualifying creator-level paying-supporter counts. Present these as separate activity and payment totals. Dividing 60 by 300 does not establish a 20% purchase conversion rate because no evidence connects those supporters to those clicks.

Build a client report you can reuse

Keep the main report compact and attach account-level detail for review. A fixed comparable roster makes the growth calculation clearer, but excludes new accounts from that particular measure. The separate roster-change block ensures their contribution remains visible.

Use these fields each period, preserving definitions and flagging any changes:

• Scope: reporting period, timezone, cutoff and comparable account list.
• Audience: combined starting and ending counts, net change and combined-base growth rate.
• Roster changes: additions, departures and their separately reported follower counts.
• Page activity: recorded views and outbound clicks, with link and campaign breakdowns where available.
• Payment support: qualifying definition, cutoff and sum of creator-level supporter counts.
• Coverage: deduplication boundary, missing observations, unavailable payment records and unknown overlap.