Quick answer
Developer engagement is what developers do with your content and product beyond seeing it: reading to the end, upvoting, commenting, following, trying, returning. It is the measure that separates attention from impressions, and the one campaigns should be judged on.
Developer engagement
DefinitionAn impression says an ad was served; a view says it was on screen; engagement says a developer did something. For content, that is reading time, upvotes, comments, shares and follows. For a product, it is activation, repeat use and contributions. For a campaign, it is the share of people reached who read, clicked, followed or came back.
What counts as engagement, and what does not?
Counts: reading to the end, upvoting, commenting, saving, sharing, following a source, clicking through, signing up, coming back. Each shows a developer chose to spend attention. Does not count: impressions, viewable impressions, reach, and the "engagement rate" some networks compute from hovers and autoplay. If the developer did not choose it, it is delivery.
The gap between the two is large. Attention research finds 35% of "viewable" ads are actually looked at (Lumen / Adelaide attention research), so an impression report overstates attention several times over. Engagement is the correction.
What makes developers engage with a post or an ad?
- A specific claim: "Postgres 17 cut our p99 by 40%" is read; "Blazing fast database" is scrolled.
- The format of the place: a post in a feed of posts, a line in a newsletter of lines.
- Relevance to this week's work: targeting by what they are reading, not who they are.
- An author: an engineer's name on the post earns a read a logo does not.
- Somewhere to go next: a page to follow, a repo to star, a quickstart to run.
Engagement is therefore a creative signal. A campaign with reach and no engagement has a creative problem; one with engagement and no sign-ups has a landing problem.
Common mistakes
- Reporting impressions as reach and reach as attention.
- Judging creative by clicks alone, which rewards clickbait.
- A campaign with nothing to follow, so engagement cannot compound.
- Treating comments as a risk instead of the most useful signal a campaign produces.
How developers experience it
- They upvote what taught them something, and remember who wrote it.
- They comment when the post made a claim they can test.
- They follow a company after the second useful post, not the first.
How do you report engagement to a team used to clicks?
Show the chain: reached, read, engaged (upvotes, comments, follows), clicked, signed up, activated. Clicks sit in the middle, which is where they belong. Add the following on the company page as a cumulative line, because it is the one number that keeps rising after the campaign stops. And compare creative by engagement per thousand reached, which tells you what to write next.
How does engagement compound over time?
A developer who upvoted one post sees the next in their feed with your name on it; a developer who followed the page sees every post without promotion. Over months a campaign that keeps engaging builds an audience it no longer pays to reach. That is the difference between buying attention and earning it, and it only happens when there is a page to follow and a cadence to follow it for.
On daily.dev
How it works on daily.dev
daily.dev reports engagement, not only delivery: reads, upvotes, comments, follows on your verified company page, and what developers did next, every week.
Explore my optionsImpressions vs viewability vs engagement
| Capability | Impressions | Viewable impressions | Engagement |
|---|---|---|---|
| Means | The ad was served | The ad was on screen long enough to count | A developer did something |
| Proves attention? | No | No | Yes |
| Examples | Served, reach | Viewable rate | Reads, upvotes, comments, follows, clicks, sign-ups |
| Tells you about | Delivery | Placement quality | Creative and relevance |
| Compounds? | No | No | Yes, through follows |