Quick answer
The daily.dev Digest is the personalized email newsletter each developer on daily.dev tunes to their own topics, cadence and delivery time. For advertisers it is the newsletter placement: a sponsored slot inside the digests sent to a chosen topical audience.
daily.dev Digest
DefinitionMost developer newsletters are one editor's picks sent to everyone at the same hour. A personalized digest is assembled per reader from what they follow, sent daily or weekly on the day and time they chose, with a handful of posts each. The open is deliberate, because the reader built the newsletter.
Also called: Developer newsletter digest, Personalized digest.
How does the Digest differ from a regular developer newsletter?
A regular newsletter is one editor's picks sent to everyone at the same hour. The Digest is assembled per reader from the tags and sources they follow, sent daily or weekly on the day and at the time they chose, with a handful of posts each. The open is deliberate: the reader built the newsletter, and it arrives when they asked for it.
For a sponsor the difference is the audience. Instead of a list defined by one writer's topic, the Digest is tracks defined by what readers follow, so a slot reaches developers who chose the topic rather than a list that happens to overlap it.
How is a Digest slot bought and targeted?
By audience track and week. There are 5 Digest audience tracks, such as web development, AI and machine learning, DevOps and cloud, security, and data; a slot runs in every digest sent to the chosen track for that week. It is included in every daily.dev Ads plan as an alternative to the in-feed campaign, and most advertisers pair it with the feed on the same tags.
Pick the track your first developer follows, not the biggest one. A security product in the security track reaches the readers who chose security; the same slot in the web track reaches more people and fewer buyers.
Common mistakes
- Picking the biggest track instead of the one your buyers follow.
- A banner-style image that is unreadable at email size.
- Judging the week on opens, which automatic opens inflate.
- Running the Digest without the feed on the same tags, and losing the repetition.
How developers experience it
- They built the Digest themselves, so they open it on purpose.
- They scan headlines and give the ad the same second as each post.
- They click from the phone and sign up from the desk later.
What should a Digest ad look like?
- An image that reads at email size: a product screenshot, a diagram, a clear graphic.
- A logo, so the reader knows who is speaking.
- A headline that states the result in one line.
- One call to action and one tracked link, with UTM parameters unique to the week.
Keep it to a glance. A reader opening the Digest is scanning headlines; the ad gets the same second each post gets, and a specific headline wins it.
How do you measure a Digest campaign?
Sends to the track, clicks on the tracked link, and what happened after: visits, sign-ups and activations with a window of weeks, because email is opened late and acted on from another device. Compare weeks against each other by creative, and compare the Digest against the feed campaign on the same tags by cost per activated developer. Opens are reported where available but inflated by automatic opens, so clicks are the honest unit.
On daily.dev
How it works on daily.dev
Newsletter Ads on daily.dev are a slot in the Digest for a chosen audience track, covering every digest sent to that track that week. It is included in every plan as an alternative to an in-feed campaign.
Explore my optionsThe daily.dev Digest vs an editorial developer newsletter
| Capability | daily.dev Digest | Editorial developer newsletter |
|---|---|---|
| Who picks the content | Each reader, from what they follow | One editor |
| When it arrives | The day and time each reader chose | The same hour for everyone |
| Sponsor targeting | By audience track | The whole list |
| Bought as | A weekly slot inside the plan | Per issue from the writer |
| Pairs with | In-feed ads on the same tags | Nothing by default |