a click is a signal. a recorded payment is a different event.
A custom conversion tracking system built with Python and FastAPI, connecting Meta campaign activity to website visits, WhatsApp taps, saved enrolments and recorded payments.
01 · the short version
Ad-platform clicks tell only part of the story. Jardella needed a clearer view of whether traffic was turning into enquiries, enrolments and paying students. I built an internal reporting tool that puts Meta campaign performance alongside activity recorded on the website, with separate views for landing pages, leads and click events.
the problem
An ad click, a tracked website visit, a WhatsApp tap and a paid enrolment are different measurements. The challenge was making those differences visible without presenting activity as revenue, or assuming that Meta totals and website totals should match. Older and manually entered records also needed to remain distinguishable when their original source was unknown.
the approach
I used Python and FastAPI for tracking, Supabase for login, and integrations with Meta and Paystack. The dashboard separates campaign metrics from website activity, then exposes source, campaign, landing page, button location and enrolment status for investigation. The reporting explicitly treats a WhatsApp click as intent, not proof of a message or a payment.
Jardella / inside the build
follow the evidence.
not just the big number. ↙
Spend · impressions · ad clicks · CPC / CTR
Visits · button taps · leads · recorded payments
Inspect tracked visitors by source, campaign and landing page. Meta ad clicks and recorded website visits are separate measurements, so the dashboard keeps their totals separate.
An ad-platform click is not proof of a recorded website visit.
Conceptual walkthrough of the reporting, not live traffic. Visitors may take different paths; a WhatsApp tap is not required before enrolment. Dashboard figures are point-in-time records, not performance-uplift claims.
02 · my part
Custom conversion tracking development
Ad attribution reporting
Authentication integration
Payment integration
Internal dashboard
Lead and enrolment reporting
03 · from the archive
04 · okay, but did it work?
The team can inspect the gap between ad engagement and recorded business outcomes in one internal workspace: compare campaign activity, find landing pages generating intent, review saved leads and distinguish pending records from paid students. The screenshots document the tool in use; their figures are snapshots rather than a claim of increased sales.
I used Python and FastAPI for tracking, Supabase for login, and integrations with Meta and Paystack. The dashboard separates campaign metrics from website activity, then exposes source, campaign, landing page, button location and enrolment status for investigation. The reporting explicitly treats a WhatsApp click as intent, not proof of a message or a payment.
built with