--- title: "What are in-feed ads? | daily.dev Ads glossary" url: https://business.daily.dev/glossary/in-feed-ads/ description: "In-feed ads are sponsored posts inside a feed, in the same card format as the posts around them and labelled as promoted. They are read as part of the feed, which is why they work on audiences that ignore banners." lastUpdated: "2026-10-20" llmsTxt: https://business.daily.dev/llms.txt --- ## What are in-feed ads? In-feed ads are sponsored posts inside a feed, in the same card format as the posts around them and labelled as promoted. They are read as part of the feed, which is why they work on audiences that ignore banners. Also called: In-feed native ads, Feed ads. The format is the native ad's most common form: a card with a cover image, a headline and a source, inserted among organic posts at a set frequency. The reader meets it the way they meet everything else in the feed, by reading, which is the point. Three things decide whether an in-feed ad works. Targeting: the feed has to be the one your audience actually reads, and the ad has to reach the part of it that cares. Creative: the headline and cover have to meet the feed's standard, because they sit next to the best posts of the day. Landing: what the developer finds after the click has to match what the card promised. Feeds compound. A developer who sees a company's posts over weeks starts to recognise it, follows it, and reads the next one without the ad. That is why in-feed placements are usually bought as always-on campaigns rather than bursts. ## How do in-feed ads work on a developer platform? A promoted post is inserted into the feed at a set frequency among the organic posts, in the same card: cover image, headline, source name, and a "promoted" label. Targeting decides whose feed it appears in, usually by the tags and topics a developer reads, their seniority and their region. The developer reads it the way they read everything else, and clicks through to your page or your post. On daily.dev the card is a 1024 × 512 image and a headline of up to 80 characters, shown in the feed developers open 6–7× a day, 90% of the time on a desktop at work (daily.dev platform analytics, cited in "Where to advertise to developers"). Frequency capping keeps the same card from showing up too often to one person. ## What makes an in-feed ad perform? - **A headline that states the result:** "Trace requests across 40 services without changing code" beats "Observability, reimagined". - **A cover that looks like the post:** a screenshot, a diagram, a terminal, not a stock photo with a logo. - **Targeting to the tags where the problem lives,** not to the whole platform. - **A landing that delivers the headline:** the tutorial, the benchmark, the quickstart. - **A company page behind it,** so a developer who liked the post has something to follow. The card competes with the best organic posts of the day, so the bar is "would a developer upvote this", not "does it look like our brand". ## How should in-feed ads be bought and run? As an always-on monthly placement with a few creatives in rotation, reviewed weekly: the headline that is read most stays, the one that is not gets rewritten. Recognition builds over weeks, and the following on the company page is what the campaign leaves behind, so a two-week burst wastes the ramp. Pair the feed with [the Digest](https://business.daily.dev/email.md) slot on the same tags to reach the same developers in the inbox. Measure by reads and clicks per thousand served for the creative, and by sign-ups and activations with a weeks-long window for the channel. ## What should you promote in the feed? Posts developers would read anyway: a release with a changelog, an engineering story, a tutorial, a benchmark with its method, an open-source announcement. A product page can work when the headline is specific. A "book a demo" page does not; developers in a feed are reading, not shopping, and the card has to respect that. When in doubt, promote the post the engineering team is proudest of this month. **Common mistakes** - Banner creative in a card that was supposed to look like a post. - A headline about the brand instead of the result. - A two-week burst, then judging the channel before recognition built. - Landing on a demo form from a post about a tutorial. **How developers experience it** - The card is one more post; they read the headline and decide in a second. - They respect the "promoted" label and ignore anything that pretends otherwise. - They follow the company whose promoted post was actually good. ## On daily.dev [In-Feed Ads](https://business.daily.dev/feed.md) are the core placement on daily.dev: a promoted card in the feed developers open to keep up, targeted by stack, seniority and region, with a 1024 × 512 image and a headline of up to 80 characters. Our team shapes the creative with you. ## In-feed ads vs display ads vs sponsored content | | In-feed ads | Display ads | Sponsored content | | --- | --- | --- | --- | | **Where it sits** | Among the posts, in the same card | Around the content, in a banner | As a full post on the platform | | **Blocked by ad blockers?** | Rarely | Mostly | Rarely | | **Creative** | Cover and headline | Banner | A whole article | | **Bought as** | Always-on monthly placement | CPM flights | Per article, on reads | | **Measured by** | Reads, clicks, follows, activations | Impressions, clicks | Reads, engagement, activations | ## Go deeper - [In-Feed Ads on daily.dev](https://business.daily.dev/feed.md) - [Newsletter ads vs in-feed ads](https://business.daily.dev/resources/newsletter-ads-vs-in-feed-ads-choosing-formats-for-developer-campaigns.md) - [How native ads fit into developer workflows](https://business.daily.dev/resources/how-native-ads-fit-into-developer-workflows.md) Related terms: [Native advertising](https://business.daily.dev/glossary/native-advertising.md) | [Contextual targeting](https://business.daily.dev/glossary/contextual-targeting.md) | [Newsletter sponsorship](https://business.daily.dev/glossary/newsletter-sponsorship.md) ### Frequently asked questions **What is the difference between in-feed ads and display ads?** Display ads are banners placed around content; in-feed ads are posts placed within it, in the same format. Display is blocked or ignored by most developers; in-feed is read because it is part of the reading. **What should an in-feed ad look like?** Like the best post in the feed: a specific headline that states what the reader gets, a cover that matches, and a landing page that delivers it. Avoid anything that reads like an ad in disguise; the label already says it is promoted. **How long should an in-feed campaign run?** Long enough to be recognised. Developers rarely act on the first post; recognition builds over weeks, which is why in-feed is bought as an always-on monthly placement rather than a one-week burst. **How are in-feed ads targeted on daily.dev?** By the tags and topics a developer reads, by seniority inferred from activity, and by region. The card appears in the feed of developers who read about the stack your product serves. **What image and headline does an in-feed ad need?** On daily.dev, a 1024 × 512 cover and a headline of up to 80 characters. A screenshot or diagram outperforms a stock image, and the headline should state the result the reader gets. [All terms](https://business.daily.dev/glossary.md) | [Explore your options](https://business.daily.dev/schedule/?ref=glossary-in-feed-ads) | [How pricing works](https://business.daily.dev/pricing.md)