Analytics QA Toolkit
Python/pandas toolkit that scans CSV or Excel dashboard exports for missing dates, null KPIs, duplicate rows, abnormal spikes, broken mappings and inconsistent naming.
GitHub projects
Tools a technical analytics delivery owner would actually use.
The point is not to look like a full-time software engineer. The point is to show I can build practical scripts, QA reports, templates and documentation that make analytics operations more reliable.
Datorama Data Stream Naming Validator
Validates stream naming conventions, country/category/source fields, campaign naming and taxonomy drift before dashboard operations become harder to maintain.
eCommerce KPI Framework
Documents KPI definitions, mock datasets, calculated metric logic and sample reporting checks for sessions, clicks, conversion rate, orders, revenue and retailer sales.
GA4 Tracking Validation Framework
Validates event taxonomy, conversion flags, ecommerce parameters, page types, UTM completeness and duplicate event IDs before reporting depends on GA4 data.
Vendor Handover Tracker
Tracks analytics handover owners, access gaps, dependencies, due dates, risk levels and next actions so vendor transitions are visible and survivable.
Dashboard Governance Playbook
Documentation-first governance system for KPI definitions, dashboard owners, filter logic, QA evidence, stakeholder sign-off and monthly reporting workflows.
Portfolio system
The repos map to real analytics delivery problems.
Each repo is intentionally small, practical and business-facing, so the portfolio supports analytics PM positioning instead of pretending to be a pure software engineering profile.
QA and trust
Analytics QA Toolkit, GA4 Validation Framework and Datorama Validator show how I turn reporting risk into evidence.
Definitions and governance
eCommerce KPI Framework and Dashboard Governance Playbook show how I structure metrics, filters and sign-off.
Delivery ownership
Vendor Handover Tracker shows how I manage owners, access gaps, dependencies and operational follow-through.
Repository standard
Every project will include the same business-facing proof.
Problem statement
What reporting or delivery pain the project solves.
Working example
Sample data, runnable code or a practical template.
Business value
Why the tool matters for stakeholders and delivery quality.
Roadmap
What would improve next in a real analytics operations environment.
Need a practical QA or governance tool for your reporting process?
I can help design the workflow, write the documentation and build a lightweight first version.