Usable now
Domain tables such as subscribers, purchases, memberships, comments, live notes, lesson bookings, and email events answer many durable business questions.
All Fanful features
First-party insight
First-party analytics for creator actions that actually matter.
Fanful analytics combine domain records with an event stream so creators can understand listeners, sources, playback, purchases, lessons, memberships, email, and recent activity. The useful dashboard is not raw traffic alone; it is fan behavior connected to the creator's operating data.
Status
ShippedAvailable in the current Laurel/Fanful stack.
Fan value
Fans get a product that can remember useful listening and account context without needing a third-party analytics script to be the source of truth.
Creator value
Creators can see acquisition, listening, conversion, recent signal, and email downstream activity in a first-party dashboard.
Current state
What is grounded today.
These claims come from the current production stack, feature docs, route handlers, and shipped screenshots. Anything still immature stays in the boundary list.
- Domain tables such as subscribers, purchases, memberships, comments, live notes, lesson bookings, and email events answer many durable business questions.
- analytics_events stores behavioral events such as page views, source/referrer context, playback, outbound clicks, conversion steps, and campaign/session context.
- listener_playback_state stores the current durable answer to the last track and moment reached by a listener identity.
- The shared layout records public page_view events with first-touch and last-touch UTM/referrer context.
- /admin/analytics aggregates source, listener, playback, purchase, membership, lesson, reply, and recent-event signals.
Fans
Why fans notice it
- Fans get a product that can remember useful listening and account context without needing a third-party analytics script to be the source of truth.
- Preference, purchase, membership, lesson, and playback state can be interpreted as part of one relationship.
- The platform can keep analytics scoped to creator operations instead of optimizing only for generic page views.
Creators
What artists can operate
- Creators can see acquisition, listening, conversion, recent signal, and email downstream activity in a first-party dashboard.
- Domain records and analytics events can be combined so actions like purchases, bookings, replies, and memberships matter more than vanity visits.
- The event model leaves room for native-app actions and agent-visible summaries without changing the public site first.
Evidence
Proof points in the current stack
Analytics plan
docs/features/analytics.md documents the hybrid model of domain records, analytics_events, and listener_playback_state.
Dashboard route
The analytics notes document /admin/analytics inside the shared admin shell with source, listener, playback, and conversion summaries.
First-party tracker
docs/features/analytics.md documents page_view tracking and outbound_click intent without making GA4 the dependency.
Boundaries
What this page should not overpromise
- Analytics should not claim perfect attribution or personal certainty from email open/click events.
- Some player intent work remains an integration point for the active player branch.
- Raw analytics should be interpreted with domain records before being treated as business truth.
Pricing notes
- Analytics uses Workers, D1, and app traffic, so pricing should account for fan-record scale and event volume.
- Higher fan counts, playback volume, and campaign traffic can increase storage and query work over time.
Next paths