--- title: "What is contextual targeting? | daily.dev Ads glossary" url: https://business.daily.dev/glossary/contextual-targeting/ description: "Contextual targeting shows an ad based on what a person is reading now, not on who they are or where they have been. For developers it means targeting the stack, topic and seniority they read about, with no third-party cookies." lastUpdated: "2026-10-20" llmsTxt: https://business.daily.dev/llms.txt --- ## What is contextual targeting? Contextual targeting shows an ad based on what a person is reading now, not on who they are or where they have been. For developers it means targeting the stack, topic and seniority they read about, with no third-party cookies. Also called: Contextual advertising. Behavioural targeting builds a profile of a person from their history across sites and follows them; contextual targeting looks at the page, feed or topic in front of them and places an ad that fits. The first needs third-party data; the second needs only the content. It has come back because the data behind behavioural targeting is going away: browser restrictions on third-party cookies, privacy law, and audiences that block tracking. For developer audiences it was always the better signal. A developer reading about Kubernetes is interested in Kubernetes now, whatever their job title says. The precision comes from the taxonomy: tags and topics fine enough to describe a stack, and the ability to combine them with seniority and region. The trade-off is that you reach a moment of interest rather than a named person, which for most developer products is the moment that matters. ## How does contextual targeting work on a developer platform? A developer platform knows what each reader follows and opens: the tags on every post, the sources they subscribe to, the topics they return to. Contextual targeting uses that reading as the audience definition. You do not pick people; you pick the reading, and the campaign is shown to whoever is doing it. On daily.dev that reading is described by 800+ tags: languages, frameworks, tools and topics. A campaign for a Postgres monitoring tool targets #postgresql, #observability and #sre; the feed shows the promoted post to developers reading those tags, in the same card as the posts they came for. Seniority, inferred from on-platform activity rather than declared, and region narrow it further. Nothing about the individual is bought or inferred from third-party data. The signal is the content in front of them, which is both the privacy-safe choice and, for developers, the more accurate one. ## Which signals can an advertiser target by? - **Stack and topic.** The tags a developer reads: a language (#python), a framework (#react), a tool (#kubernetes), a practice (#testing) or a domain (#security). - **Seniority.** Junior, mid-level, senior or leadership, from how and what the developer reads over time, not from a title they typed once. - **Region.** Country or region, for licensing, compliance or where your sales team can follow up. - **Newsletter track.** For [the Digest](https://business.daily.dev/email.md), a topical audience such as DevOps and cloud or AI and machine learning. The strongest campaigns combine two: a stack plus a seniority (senior developers reading #kubernetes), or a stack plus a region (React developers in the EU). A stack alone is broad; a stack with a buying signal is a persona. ## When should you choose contextual over behavioural targeting? Choose contextual when the moment matters more than the person. A developer reading about database migrations is a better prospect for a migration tool this week than someone who visited a database site three months ago, whatever their title. Choose it, too, when behavioural data is not available or not trustworthy: 67% of developers run an ad blocker (MarketingTech News, developer ad-blocking survey), which also blocks the trackers behavioural targeting depends on, so the profiles it builds of developers are thin and skewed toward the ones who do not block. Behavioural targeting still earns its place for retargeting your own visitors, where the signal is first-party and the intent is proven. The two are not rivals; most developer campaigns run contextual for reach and first-party retargeting for the follow-up. ## How do you write a creative for a contextually targeted campaign? Match the context you bought. If the placement is next to posts about Kubernetes, the headline should say Kubernetes, name the specific problem (certificate rotation, cost, noisy alerts) and state what the product does about it. A generic "the modern platform for teams" card loses the one advantage contextual targeting gave it. Write for a reader mid-task. Developers reading a tag are solving something; a headline that offers a result ("Cut Kubernetes alert noise by routing on labels") outperforms one that offers a brand. Run several variants per tag so the system can find the one that reads best beside that content. ## How do you know contextual targeting is working? Look at the response by tag, not just in total. A campaign across five tags usually has two that carry it; the report should show reads, clicks and follows per tag so budget moves toward the context that responds. Then look past the click. Developers read, remember and sign up later, so the [conversion pixel](https://business.daily.dev/pixel.md) and view-through conversions show what the context produced in the following weeks. If a tag drives reads and follows but few immediate clicks, it is often doing its job: those are the developers who will arrive through the docs next month. **Common mistakes** - Targeting a stack so broad (#javascript alone) that the context says nothing about intent. - Buying a precise context and running a generic creative that ignores it. - Judging a tag on first-week clicks when developers on that tag convert weeks later. - Stacking seniority, region and five tags until the audience is too small to learn from. **How developers experience it** - An ad that matches what they are reading reads as relevant, not as tracking. - An ad that follows them from another site reads as surveillance, and gets blocked. - They notice when a card names their actual tool and version; it earns the click. ## On daily.dev Targeting on daily.dev is contextual by construction: 800+ targetable keywords (languages, frameworks, tools and topics) drawn from what developers read, plus seniority from on-platform activity and region. Nothing is inferred from third-party data. ## Contextual vs behavioural targeting | | Contextual targeting | Behavioural targeting | | --- | --- | --- | | **The signal** | What the person is reading now | What the person did on other sites | | **Data needed** | The content and its tags | Third-party cookies or a purchased profile | | **With cookie limits and tracker blocking** | Unaffected | Shrinking reach, patchy profiles | | **Precision** | Precise about interest, blind to identity | Precise about identity, stale about interest | | **Fits developers because** | Reading about a stack is the intent signal | Titles and past visits predict little | ## Go deeper - [Why context beats cookies for developers](https://business.daily.dev/resources/contextual-advertising-for-developers-why-context-beats-cookies.md) - [Interest-based vs contextual targeting](https://business.daily.dev/resources/interest-based-marketing-vs-contextual-targeting-which-drives-better-roi.md) - [Contextual targeting tips for native ads](https://business.daily.dev/resources/native-ads-for-developers-contextual-targeting-tips.md) Related terms: [Native advertising](https://business.daily.dev/glossary/native-advertising.md) | [Developer audience platform](https://business.daily.dev/glossary/developer-audience-platform.md) | [B2D marketing](https://business.daily.dev/glossary/b2d-marketing.md) ### Frequently asked questions **What is the difference between contextual and behavioural targeting?** Behavioural targeting follows a person based on their past activity, usually through third-party cookies. Contextual targeting places an ad based on the content someone is engaging with right now. Contextual needs no personal data and survives cookie restrictions and tracker blocking. **Is contextual targeting less precise?** It is precise about interest and imprecise about identity. For developer products that is the right trade: you reach people reading about your category at the moment they care, rather than people who once visited a related site. **Can I combine contextual targeting with my own retargeting?** Yes, and most developer campaigns do. Contextual placements bring new developers in from the tags they read; your own first-party retargeting follows up with the ones who visited your site. Each uses a signal it legitimately has. **Which signals does daily.dev target on?** The tags developers read (800+ languages, frameworks, tools and topics), seniority inferred from on-platform activity, and region or country. No third-party cookies or purchased profiles. **How narrow should a contextual audience be?** Narrow enough that the context implies intent (a tool, a practice, a problem), wide enough to learn from in a week. Start with a stack plus one qualifier, read the per-tag results, then narrow or widen. [All terms](https://business.daily.dev/glossary.md) | [Explore your options](https://business.daily.dev/schedule/?ref=glossary-contextual-targeting) | [How pricing works](https://business.daily.dev/pricing.md)