Sometime in mid-2022, sneaker drop coordination was a frustrating problem. Releases on SNKRS, Adidas Confirmed, and resale platforms moved fast, alerts were scattered across Twitter and Reddit, and most people in the buyer community were finding out about drops minutes too late to participate. The information was out there, but it wasn't where the customers were.

A friend was running a sneaker drop community on Discord called Jersey Supply — about 350 members deep, mostly young buyers tracking releases. The dynamics interested me as a CS major minoring in Entrepreneurship at Rutgers, and they gave me permission to study it as my first analytics case study. The question I wanted to answer: what actually drives engagement and retention inside a niche product community?

The work was non-commercial: no monetization, no transactions, no compensation involved on my end. Just observation, a lightweight tracker, and time.

What I studied

Over roughly eleven months, I tracked four things across the community as drops happened in real time: which channels saw the most member activity, how alerts performed against drop windows, what posting cadence correlated with retention, and where members fell off after their first week.

The setup was deliberately simple. A Google Sheets workbook with two tabs — one for inventory and drop tracking, one for member activity and engagement — held together by about ten formulas pulling member counts, message-rate proxies, and a cohort retention view. Not enterprise tooling. The simplest thing that would let me ask honest questions.

What the data showed

Three things kept showing up across the eleven months.

The activity distribution was lopsided in the way most consumer communities are. Yeezy and Jordan channels saw a wildly higher message rate per member than every other channel combined. The "long tail" of brand channels (Adidas non-Yeezy, New Balance, niche collabs) was almost entirely silent. A useful early signal: when you can pick fewer drops to support and go deeper, do it.

Missed alerts hurt retention non-linearly. A member who missed a single drop alert came back at almost the same rate as everyone else. A member who missed three consecutive drop alerts dropped off a cliff — the odds of them being active a month later fell sharply, regardless of when they joined. The implication: posting cadence and reliability of alerts mattered more than total alert volume.

The day of the week someone joined predicted whether they stayed. Saturday joins were far stickier than Tuesday or Wednesday joins, which mapped onto a Saturday content cadence we'd accidentally fallen into. The takeaway wasn't that Saturdays are magic — it was that matching a member's first-experience moment to your strongest content moment is a retention lever sitting in plain sight.

Posting cadence and reliability of alerts mattered more than total alert volume.
350+
friend-run sneaker
community studied
10+
tracker formulas
across two tabs
11mo
observation
window

What I'd do differently

Three things I'd build into the framework from day one if I were doing this analysis again today.

i
Event-level tracking, not member-level.
I tracked who was in the community. The richer signal was always what they did — which alerts they clicked, which drops they engaged with, which content kept them around. The shift from member-centric to event-centric measurement is the same shift product analytics teams make at scale.
ii
Cohort retention from day one.
A cohort view — members grouped by join week, plotted by share still active N weeks later — would have surfaced the third-missed-alert cliff six months earlier than I caught it. It's the single most useful framing I'd add now.
iii
Better data hygiene from the start.
No consistent way to log new joins or tag which drops generated activity. A simple intake structure and consistent event tagging would have made the spreadsheet ten times more useful by month three. The first lesson of any analytics work is that you can only answer the questions your data was set up to answer.

Why I'm still talking about it

Jersey Supply was small. Non-commercial, niche, eleven months. By the metrics that matter to most people, it was nothing. But it taught me something that's still pulling me forward years later: the questions that get asked of data are wildly more interesting when you have skin in the user's experience.

That's the thread that runs from this case study to my Gametime Vault analytical case study now, and to the kind of product analytics co-op I'm targeting after Northeastern. Sneakers, sports cards, sports betting, live commerce — the businesses I'm drawn to are the ones I'd be a customer of anyway. That's not a coincidence. It's the whole point.

About this case study. This is a portfolio analysis of a friend-run sneaker drop Discord community, conducted with their permission as an academic-style learning project during my time at Rutgers. I do not own, operate, or run the community. No compensation, transactions, or commercial activity is involved on my end. It is included here as a portfolio reflection on what studying a small consumer community taught me about retention, content cadence, and lightweight analytics — not as employment, business ownership, consulting, or a commercial venture.