Advertisers
Reach developers inside
the tools they already opened.
Category-targeted CPC campaigns across free utilities, generators, and side projects. You submit four lines of copy. You pay your bid on valid clicks, and nothing on impressions.
Context
Why the slot matters more than the reach.
A yeld unit sits on a primary screen of a free tool in a known category, while the reader is mid-task in that category. Someone exporting an SVG is, at that moment, a person who works on design. That is the whole targeting signal, and it needs no profile of the person to be useful.
Publishers place one unit per screen across every primary screen of the app, not a single banner at the bottom of one page — so a campaign reaches the same reader at more than one point in the work, including the moment they finish something.
- One unit per screen, on every primary screen of the app, visible on load
- Native text rendering — yeld controls the markup, you never ship a banner
- Styled to match each publisher app's own type, color, and radius, so it reads as part of the product
- Labeled Sponsored and attributed to yeld on every impression, in every app
- Contextual only: no cookies, no retargeting, no cross-site profiles
Creative
Four fields. yeld renders them.
Text and an optional logo — no markup, no scripts, no image dimensions to chase. The same creative adapts to the host app's light or dark theme, to its type and color tokens, and to the compact and card variants. One submission renders natively everywhere it runs.
{
"headline": "A Postgres branch for every pull request",
"body": "Tidebase forks your …",
"cta": "Create a branch",
"logoUrl": null
}headline
≤ 80 chars
body
≤ 140 chars
cta
≤ 24 chars
Without a logo, yeld draws a monogram from your company name. No creative text is edited or rewritten.
Rendered — card variant
A Postgres branch for every pull request
Tidebase forks your database in about a second, so preview deploys run on real data. Free below 5 GB.
Create a branchStatic example. Tidebase is a fictional product.
Campaigns
What you control.
- Targeting
- One or more app categories, or all of them. Publishers can attach optional context —
page,event,keywords— and your tags get a modest weight boost when they overlap. Context can only broaden a match, never gate one. - Categories
- developer-toolsai-toolsproductivitydesignmarketingbusinessfinanceeducationgamescreator-toolslifestyleother
- CPC bid
- What you pay for one valid click. It is also your selection weight: among eligible campaigns, yeld picks one at random weighted by bid.
- Budgets
- A total budget, and optionally a daily budget. Serving stops when the total is spent. The daily cap is approximate — it is checked against spend recorded so far that day.
- Schedule and state
- Optional start and end dates. Pause and resume at any time; eligibility is evaluated on every request, so a pause takes effect on the next one.
- Destination
- One URL per campaign, stored server-side. Clicks route through yeld attribution and 302 to it.
Reporting
Six numbers, one table.
Every campaign reports impressions, clicks, CTR, spend, and effective CPC, plus delivery broken out by publisher app — so you can see which app is actually producing the clicks you are paying for.
A duplicate click on the same impression redirects but is never billed twice; the constraint is in the database, not in a filter.
Delivery by app
Illustrative shape of the table, not real data.
Current phase
What is not built yet.
- Billing
- Manual and invoiced. There is no self-serve card funding, so a campaign is set up with us and settled outside the product for now.
- Selection
- Not a real-time auction. Eligibility is filtered by category, status, schedule, and remaining budget, then one campaign is chosen at random weighted by bid. No second-price mechanics, no pacing model.
- Conversion tracking
- Not available. yeld measures clicks; attribution past the click is yours to instrument on your own landing page.
- Inventory
- Early. Set a small budget first and read the delivery-by-app report before committing more — see the publisher side for how apps join.
Put the product where the work happens.
Pick your categories, write four lines, set a bid and a budget. Pause it the moment the numbers stop making sense.