Analytics and measurement for devtools marketing

What measurement actually delivers

Most early-stage devtools marketing is judged on feel. Someone says the blog is doing great, someone else says the ads are a waste, and nobody can prove either one. Measurement replaces that argument with a number everyone can see. That is the whole point. Not a prettier dashboard, but a shared source of truth so you stop relitigating the same debate every planning meeting.

In 12 plus years running GTM inside 30 plus companies, the pattern is always the same. The teams that grow efficiently are not the ones with the most tactics. They are the ones who know which tactics to kill. You cannot kill what you cannot see, and you cannot see it without instrumentation that is set up correctly and read honestly. I build both.

What you get out of this is boring in the best way. Clean data, dashboards that answer real questions, and a reporting rhythm that tells you where to put the next dollar. Decisions get faster because they stop being opinions.

The metrics that matter, and the ones that flatter you

Raw sessions, pageviews, impressions, and follower counts are vanity metrics. They go up and to the right no matter what you do, and they never tie to revenue. A post can rack up ten thousand pageviews and source zero pipeline. If your reporting leads with those numbers, it is decoration, not measurement.

The metrics I care about are the ones a CFO would recognize. Signups. Activation. Sourced pipeline. Booked meetings. These connect marketing effort to money, which is the only connection that keeps a marketing budget alive. Everything I build is oriented around making those numbers visible and making the gaps between them obvious.

This is also where a lot of dashboards quietly lie. They show you the top of the funnel because that is the easy part to instrument, then go dark exactly where the money is. I build for the parts that are hard to measure, because that is where the decisions actually live.

Why attribution breaks for developer buyers

Developers do not click your ad, fill out a form, and convert in a tidy line. They read your docs at work, see your name in a Slack community, catch a conference talk, star the repo, lurk for three months, then sign up directly by typing your URL. None of that shows up in last-touch attribution. This is the dark funnel, and for devtools it is not an edge case, it is most of your influence.

So I stop pretending a tracking pixel can see everything, because it cannot. Instead I lean on the sources that do work. Signup surveys that ask how did you actually hear about us. Self-reported sourcing on demo requests and sales calls. These are qualitative and slightly messy, and they are also far closer to the truth than a clean attribution model that confidently credits the wrong channel.

The honest version of attribution for a developer audience is a blend. Use the hard data where it is reliable, use self-reported data where the hard data goes blind, and be transparent about which is which. I would rather give you a directionally correct answer you can trust than a precise number that is precisely wrong.

Defining activation and reading a self-serve funnel

Activation is the first time a user does the thing your product is actually for. Not signup. Not a confirmed email. The moment they get the point, the first successful query, the first deployed agent, the first trace they can read. If you have a product-led, self-serve funnel and you are not measuring activation, you are flying blind through the exact stretch where users decide whether to stay.

Reading a self-serve funnel means watching the drop-offs between signup and activation and treating each one as a question, not a verdict. Where do people stall. What did the ones who activated do differently. A funnel report is only useful if it points at a specific step you can go fix, so that is how I build them.

I define activation with you, based on your product, not on a generic template. Then I instrument it so it is tracked consistently, because an activation metric that shifts definition every quarter is worse than none at all.

What I build, with the Grepr dashboard as proof

The foundation is a correct GA4 setup, because most of the ones I inherit are quietly broken. From there I build dashboards that answer questions instead of just displaying data, plus the funnel and attribution design and the reporting cadence that keeps it all honest over time.

For Grepr, a Series A observability company, I built a GA4 blog performance dashboard from scratch. They had 83 posts live and were judging all of it on gut feel. The dashboard had four views. Posts ranked by engagement rather than raw pageviews, so the loudest post was not automatically the winner. Traffic sources with nested channel detail. Performance over time with anomaly detection, so a spike or a cliff got noticed instead of buried. And path analysis showing where readers went next.

It lives in the shared workspace, so everyone opens the same view and gets the same answer. No more dueling spreadsheets. Most importantly, it made the traffic-to-conversion gaps measurable, which is where content strategy stops being a guess and starts being a decision.

How an engagement runs

I start with an audit. What is instrumented, what is broken, what questions you actually need answered, and which of your current metrics are vanity in disguise. Nothing gets built until we agree on what good looks like.

Then I set up or repair GA4, define your activation and funnel events, and build the dashboards in a shared workspace so the whole team lives in the same data. I wire in the self-reported sourcing mechanisms that cover the dark funnel, because for a developer audience that is not optional. After that we settle into a reporting rhythm so the numbers get read and acted on, not admired once and forgotten.

Retainers start at $3,500 a month. I run a US S-corp, work Monday through Thursday, and I am American, based in Spain, covering EMEA and North America. Solo, which means the person doing your audit is the person building your dashboards and the person you talk to. No handoffs to a junior you never met.

What this covers

“She excels at running our weekly marketing calls, organizing events, reporting on web analytics, and keeping everything organized to ensure we all stay aligned. I highly recommend Summer.”

Questions on this service