Dashboard

The Dashboard answers three questions: how much traffic arrived, what visitors clicked, and which Fanvue outcomes were connected to that traffic.

When to use this

Use Dashboard when you want to compare links or understand where visits stop turning into clicks and Fanvue outcomes. Keep the date range and model filters consistent when comparing placements.

If views are high but CTA clicks are low, inspect the page, button copy, and images. If clicks are high but matched subscriptions are low, inspect the Fanvue destination and attribution before assuming the page design is the cause.

Use live activity for a quick test visit. Use a longer reporting period to judge a campaign; a handful of visits is not enough to pick a winner.

Where to find it

Choose Dashboard in the top navigation. Use the date, model, and link filters before interpreting any result.

How it works

Profile views - counted landing-page visits after Snackle’s duplicate-view protection.

Button clicks - Fanvue CTA and social-link clicks; CTR is button clicks divided by profile views.

Revenue - Fanvue value matched back to tracked Snackle traffic.

Geographic traffic, live activity, clicks over time, the click-to-fan funnel, and traffic sources.

Fanvue linked data - matched followers, subscribers, purchases, revenue, and the model involved.

Conversion delivery - whether enabled advertising or analytics providers received each event.

How to use it

  1. Choose Today, 7, 30, or 90 days, All time, or enter a custom date range.
  2. Select one model for a creator-level view, then optionally narrow to one link.
  3. Compare Profile views with Button clicks and CTR to judge the landing page.
  4. Use Traffic sources and Geography to understand where visitors came from.
  5. Use Fanvue linked data and Conversion delivery to validate downstream results.
  6. Press Refresh when you expect new Fanvue activity or recent traffic.

Good to know: A low view count means fewer counted visits reached the Snackle link. Optional consent controls external tags; it does not stop necessary first-party profile-view and click counting.