Trackfluence

Analytics platform for creators with real-time link insights.

Overview

Trackfluence is a creator analytics product focused on link performance. Creators share a lot of links — bio pages, launches, affiliate posts, newsletter CTAs — and most of that traffic disappears into analytics tools that were built for websites, not for portable short links.

I wanted a dashboard that answered three questions quickly: which links are getting traction, where the clicks are coming from, and how engagement changes over time. Trackfluence puts those answers in one place, with summary metrics, per-link breakdowns, and a map view for geographic reach.

The problem

Creator tools often split “link in bio,” UTM tracking, and audience geography across different products. That makes it hard to notice when a single link is carrying most of a campaign, or when a region suddenly shows up after a post goes live. Trackfluence treats every tracked URL as a first-class object with its own history.

What I built

  • A dashboard for tracking link clicks and visits in near real time
  • Summary metrics for total links, clicks, and active links
  • Per-link breakdowns with referrers and device context
  • Trend charts so week-over-week changes are easy to spot
  • A map view for visualizing audience spread across regions
  • Caching around the heaviest read paths so the UI stays responsive as click volume grows

How it works

Each tracked link gets an identifier and a destination URL. When someone hits the link, the hit is recorded with referrer, device, and rough location signals, then aggregated for the dashboard. The UI favors scanability: big numbers up top, a list of links in the middle, and deeper charts when you need them.

Stack

Next.js on the frontend, a PostgreSQL-backed API for events and rollups, and charting for trend views. Deployed on Vercel with caching around the heaviest read paths.

What I learned

Real-time dashboards are mostly about honest aggregation. Showing every raw click looks busy; showing nothing until midnight feels broken. The useful middle is rolling windows, clear “last updated” state, and queries that stay cheap as the event table grows.

What's next

Cohort views, exportable reports, and deeper attribution so creators can connect a spike back to a specific post or platform.