Kickin
Detect broken tracking, missing events, and event mismatch
6 followers
Detect broken tracking, missing events, and event mismatch
6 followers
Kickin is pixel health monitoring for performance marketers. Add one script tag and Kickin automatically detects events, watches for missing/broken tracking, and flags cross-tracker mismatches (like GA4 firing a Purchase event but Meta doesn’t). Get alerted fast so you can fix measurement issues before they distort reporting and optimization.
👋 I’m David, a professional marketer and hobbyist developer, and I built Kickin after seeing one too many campaign go dark on conversion tracking and only discovering it hours later.
Kickin is pixel health monitoring for GA4, Meta, and Google Ads:
- Detects missing events / broken tracking
- Flags event mismatches between GA4, Meta, and Google Ads (more coming soon!)
- Gives you a clean view of what’s firing (and what isn’t) and from a single location instead of across platforms
It's early, but live. As I continue to build though, I'd love feedback on two things:
1. What’s the most painful tracking issue that you deal with today (missing purchases, dedupe issues, parameter drift, etc.)?
2. It's currently live for GA4, Meta, and Google Ads events. What should the next platform added be (TikTok, Shopify, Klaviyo, other)?
What exactly counts as a "mismatch" between GA4 and Meta-counts, timing window, parameters, or all of the above?
@mitchell_hinrichsen Good question. Right now, the system just focuses on operational mismatches - specifically when an event fires to one platform but not the other. For example: GA4 receives a purchase event, but Meta doesn't get the corresponding Purchase within the expected window.
It also catches parameter/schema changes (e.g., value or currency suddenly missing from a payload).
The system intentionally doesn't flag attribution mismatches. GA4 and Meta will always report different conversion counts because they use different attribution models.
The short version: if both platforms should receive the same event and one doesn't, that's what we flag.
How noisy are the alerts and how do you prevent false positives?
@derik_heidemann Thanks the questions! Alerts are limited to critical events with things like pixels stopping entirely. You can mute incidents you've seen or mark as resolved. I'm hoping to build threshold customization soon. It's early and it's really only been for personal use so far, but I've gotten 1-2 meaningful alerts per week that need attention. For false positives, Kickin is set to learn typical event patterns so any expected variation doesn't trigger them.
How does it handle different event names like GA4's "purchase" and Meta's "Purchase" ? Is mapping required?
@jacob_krasnov Yes, mapping is required and that feature comes built in.
GA4 uses purchase (lowercase), Meta uses Purchase (capitalized). They also expect different parameter structures (items vs contents, etc.). Kickin lets you define which events should be compared across trackers.
So you'd map GA4's purchase to Meta's Purchase and Kickin knows to flag it when one fires without the other. Without the mapping, we'd treat them as unrelated events.
The mapping also handles cases where you use custom event names that don't match standard conventions.