Organisation: codebar.io — UK registered charity (no. 1187776) Role: Marketing Volunteer Tools: Plausible Analytics, Notion Duration: April 2026 — ongoing Focus: Conversion tracking, funnel design, cross-functional delivery
Data in this case study has been adjusted for confidentiality. All analysis and recommendations are my own.
codebar is a charity running free programming workshops for underrepresented groups in tech. It operates across multiple cities in Europe and runs virtual workshops globally.
When I joined as a volunteer, Plausible Analytics was installed on the site but not configured. There were no conversion goals, no funnels, and no structured tracking of any kind. The team had no data on:
My objective was to build a complete analytics foundation — goals, funnels and a tracking strategy — that would give the team actionable visibility into their most important user journeys.
Before starting, I identified three constraints that shaped the approach:
1. Privacy-first tool Plausible Analytics does not use cookies and does not collect personal data. This is appropriate for a charity and GDPR-compliant by default. It also means no user-level tracking — all analysis is aggregate.
2. Growth plan — no property filtering The account is on Plausible’s Growth plan. Filtering funnel steps by custom properties (for example, filtering outbound link clicks by destination URL) requires the Business plan. Every tracking decision had to work within Growth plan constraints.
3. External OAuth dependency codebar uses GitHub OAuth for all registrations. The moment a visitor clicks “Join as a student”, they are redirected to github.com — a domain entirely outside our control. This step is untraceable by any analytics tool. The funnel strategy had to account for this gap explicitly.