Why I Write Long-Form Technical Content Instead of LinkedIn Posts
Go on LinkedIn right now. Scroll for 30 seconds. Count how many posts say something real about how marketing measurement actually works.
You'll find "5 tips for better attribution" with no mention of what attribution model, what platform, or what data source. You'll find "CAPI is the future!" from someone who has never inspected a server-side event payload. You'll find AI-rewritten versions of the same three ideas cycling through your feed.
None of it helps you fix the broken tracking stack you're staring at right now.
What I'm doing instead
I'm writing the technical content I wish existed when I was debugging client stacks at 11pm. Real problems. Real implementations. Real numbers.
Intelligence briefings. I read marketing science papers and show how the theory translates into a working system. How does a multi-touch attribution model from a whitepaper actually perform when you feed it messy GA4 data? What happens when you try to implement media mix modeling for a brand spending $40K/month instead of $4M? The goal isn't to be groundbreaking. It's to document what actually works versus what sounds good in a conference talk.
System blueprints. Step-by-step technical architecture for the marketing systems that consulting firms charge six figures to build. How to set up first-party tracking that works with HIPAA requirements. How to build a server-side measurement stack that survives the next browser privacy change. The implementation gotchas, the actual code, the things that break when you go from staging to production.
Why long-form matters for this
The problems I work on don't fit in a LinkedIn post. You can't explain why a client's Meta CAPI implementation was double-counting conversions, how we diagnosed it, and how the fix changed their ROAS by 35% in 300 characters. You can't walk through building a compliant tracking architecture in a carousel.
I recently audited a healthcare company's tracking setup. They had 14 tags firing on their patient portal. Three of them were sending PHI to Google. They had no idea. That's a six-figure compliance violation waiting to happen. Explaining how to find that, fix it, and prevent it from happening again takes 1,500 words, not a hot take.
Who this is for
If you're a marketing leader at a compliance-sensitive company — healthcare, finance, education — and you're not sure if your tracking infrastructure would survive an audit, this content is for you.
If you're a marketing ops person who just got told "set up server-side tracking" with no guidance on what that actually means for your stack, this is for you.
If you're spending real money on paid media and the numbers in your ad platform don't match your CRM, this is for you.
I'm not writing to build an audience. I'm writing to show how I think about measurement problems. If the way I think matches the problems you're dealing with, we should talk.