Skip to content
Buzz Crafter

Data Methodology

How Buzz Crafter defines, calculates, compares and limits campaign metrics and Famez Creators dataset statistics.

Buzz Crafter uses campaign measurements, calculated metrics, modeled scenarios and aggregated creator-directory statistics. This methodology explains how those evidence types are separated, how calculations are performed, how attribution limits are handled and how first-party Famez Creators data should be interpreted.

1. Evidence classes

Class Definition Editorial treatment
Measured A value recorded directly by a campaign, analytics or source system. Reported with its source context and time window.
Calculated A value mathematically derived from measured inputs. Formula or derivation should be clear enough to reproduce.
Modeled A scenario using one or more assumptions. Assumptions must remain visible; output is not described as observed performance.
Dataset aggregate A count or distribution generated from a defined set of creator records. Snapshot date, source scope and coverage limits accompany interpretation.

2. Core campaign funnel

Buzz Crafter separates creator campaign measurement into sequential layers:

Impressions→Clicks→Visitors→Conversion→Retention / Value

Each stage answers a different question. Impressions describe distribution opportunities. Clicks describe response to the campaign link or placement. Visitors describe recorded arrival at the destination. Conversion describes a defined action such as a follow, subscription or purchase. Retention and value describe what happened after acquisition.

3. Metric definitions

Metric Definition Important limitation
Impressions Recorded opportunities for a placement or creative to be displayed. An impression does not prove attention.
Clicks Recorded click events on the campaign destination link. Clicks are not automatically unique people.
CTR Clicks ÷ impressions × 100. CTR does not measure destination conversion or revenue.
Visitors Destination visits or users under the destination analytics definition. Definitions vary by analytics system and privacy settings.
Conversion rate Target actions ÷ a defined upstream stage × 100. The denominator must be stated: clicks, visitors or another stage.
Daily intensity Total metric ÷ active campaign days. Useful for pacing comparison, not a quality score by itself.

4. Campaign examples used on Buzz Crafter

Two measured campaign examples are used repeatedly because they illustrate the difference between totals, duration and response rate. One five-day boost recorded 18,240 impressions, 146 clicks and 139 direct visitors. One 30-day placement recorded 70,986 impressions, 171 clicks and 156 direct visitors. Calculated CTRs and daily averages are derived from those measured inputs.

These datasets do not include enough reliably attributable subscriber and revenue data to make claims about final economic performance. Buzz Crafter therefore uses them to discuss visibility, traffic intensity, clicks and destination arrivals rather than inventing downstream outcomes.

5. Attribution boundaries

Campaign and destination systems can observe different parts of the funnel. An external placement may record an outbound click while the creator platform records a visitor, follow or subscription. Browser privacy controls, repeat clicks, redirects, loading failures, time-zone differences and session definitions can create gaps between systems.

When two systems cannot be connected with defensible attribution, Buzz Crafter keeps their results separate. A close click-to-visitor ratio can indicate that the handoff is broadly consistent under the measurement setup, but it is not proof that each click represents one unique person or one conversion.

6. Famez Creators dataset source

Buzz Crafter reads the public, read-only Famez Network statistics endpoint and stores a local cached snapshot. The endpoint exposes aggregated statistics from published creator-directory profiles. It does not expose visitor identities, raw click logs or private profile-level diagnostics.

The cached data can include unique creator count, platform-profile count, new creators over 7- and 30-day windows, platform distribution, countries, genders, languages, topics, DACH totals, taxonomy coverage and 30-day dataset changes.

7. Snapshot freshness

Buzz Crafter records when it fetched the public Famez Creators statistics API. Famez Creators itself is refreshed daily. Internal source metadata such as snapshot generation or validity timestamps can describe aggregation mechanics and are not used by Buzz Crafter to label the public dataset as stale.

8. Dataset scope

Famez Creators statistics describe the records represented in the Famez Network directory. They are not a census of every creator, every profile or every platform worldwide. Dataset composition can be influenced by supported imports, acquisition sources, publishing rules, quality filters, verification, synchronization timing and cleanup.

For that reason, a platform with a large count in the dataset is described as having a large representation in the Famez Creators snapshot. Buzz Crafter does not convert that number into a global platform-market-share claim.

9. Unique creators vs. platform profiles

One creator can be represented by more than one platform profile. Therefore unique creators and platform profiles answer different questions. Platform shares on the data pages use platform-profile counts as the denominator when discussing the composition of platform records. They should not be divided by unique creators and described as exclusive creator shares.

10. Taxonomy coverage

Country, gender, language and topic fields may be incomplete. Buzz Crafter calculates coverage as:

classified profiles ÷ unique creators × 100

A country table should therefore be interpreted together with country coverage. If only part of the directory has country classification, the visible country distribution describes the classified subset rather than every creator in the database.

11. Zero values

A zero for a platform or taxonomy value means that no published record was counted for that field in the specific snapshot. It does not prove that the platform or category has no creators globally. Zero values can also reflect source coverage, synchronization, taxonomy mapping or platform support at the snapshot date.

12. 7-day and 30-day additions

New-creator fields describe additions recorded by the directory over the defined source windows. They measure dataset acquisition or publication activity, not necessarily the number of people who became creators during that period.

13. 30-day trend percentages

Trend fields compare the dataset against the source comparison date. A positive platform change describes growth in represented records between those snapshots. It should not be rephrased as worldwide platform growth unless an external market dataset independently supports that conclusion.

14. Translation and normalization

The source API can contain German taxonomy labels or country names. Buzz Crafter preserves the original cached values for auditability and translates labels only at presentation time on the English frontend. Numeric values are not changed by translation.

15. Comparison rules

  1. Compare the same metric definition.
  2. Align campaign or snapshot windows.
  3. Use the correct denominator.
  4. Distinguish measured values from calculations.
  5. Keep modeled conversion or revenue separate from observed outcomes.
  6. Check taxonomy coverage before interpreting category distributions.
  7. Record when Buzz Crafter retrieved the published dataset.
  8. Do not turn directory composition into global market share.

16. What the data can and cannot answer

Question Supported?
How many platform profiles were represented in this Famez Creators snapshot? Yes.
Which countries appear most often among profiles with a country classification? Yes, with coverage context.
Which platform has the largest global creator market share? No; this dataset is not a global census.
Did a campaign generate a recorded number of impressions and clicks? Yes, when those values are source measurements.
How much revenue did a campaign create when destination revenue attribution is missing? No; a model can illustrate scenarios but not replace missing measurement.

17. Current network snapshot

First-party network dataset

Famez Creators network statistics snapshot

Snapshot: 2026-09-01

Unique creators48.563Published creator records represented in this snapshot.
Platform profiles49.231Platform-profile records across represented creators.
New creators · 30 days19.7179.814 added in the latest 7-day window.
DACH profiles2.2484,6% of the represented dataset.

Platform distribution

GroupProfiles
OnlyFans20.826
4Based15.769
F2F6.440
Maloum2.406
FansyMe2.220
Visit X1.382
Famez159
Fansly0
BestFans0
Fanvue0

Zero values: A zero means no published profile was counted for that platform in this Famez snapshot. It does not mean the platform has no creators globally.

Country distribution

GroupProfiles
Netherlands2.699
Germany1.933
Belgium996
Colombia501
Argentina406
USA335
Austria225
Ukraine178
Philippines172
Spain156
Malta142
France130

Gender distribution

GroupProfiles
Female17.919
Male2.924
Trans338
Diverse85
Couple17

Language distribution

GroupProfiles
German8.942
English1.384
Spanish477
Portuguese37
Dutch30
French23

Creator topics

GroupProfiles
MILF1.747
Dominatrix1.378
Curvy1.080
Tattoo954
Cosplay933
Feet601
Everyone390
Toys330
BDSM288
Dirty Talk288
Beaches287
Feet280
English (English)273
German (Deutsch)268
Natural267

Taxonomy coverage

FieldProfiles classified
Country10.200 (21,0%)
Gender21.283 (43,8%)
Language10.893 (22,4%)
Topic6.963 (14,3%)

30-day dataset trend (comparison: 2026-08-26)

MeasureChange
Total creator count23,1%
Onlyfans2,0%
4based109,3%
F2f0,3%
Fansyme24,3%
Fansly0,0%
Bestfans0,0%
Maloum0,1%
Visitx0,8%
Fanvue0,0%

Evidence boundary: Aggregated data from published creator profiles in the Famez Network directory. It does not represent the entire global creator market.

Privacy: No IP addresses, visitor identities, raw click logs, profile-level private data or admin diagnostics are exposed by this endpoint.

Related data pages