Zeekend is an ad network for AI apps. Millions of people now ask an assistant what to buy, book or try, and the answer usually leaves them with nothing to click. We add one relevant product to that answer and pay the app that showed it. We also work with coding agents, so a developer tool can show up when someone is deciding what to build with.
This page explains the formats, how we pick a product, what a campaign costs, and what we won't run.
The placement
You pick one of two formats for each campaign.
Card. This sits below the assistant's answer in a bordered box. It has a product image, a price, a link, and a headline and line of copy written for that conversation.

Illustrative. A card, as a publisher renders it.
Sponsored line. A short, labelled sentence at the end of the answer that names one product. The publisher writes the lead-in in their assistant's voice, your words go inside the link, and the "Sponsored" label comes right after. Anyone wondering which part was paid for can tell at a glance, because the paid part is underlined.

Illustrative. A sponsored line, as a publisher renders it.
Both carry a disclosure the publisher can't restyle or remove. Publishers render placements in their own interface, so the styling differs from app to app. The label is always there, and we never present a placement as the assistant's own recommendation.
How a product is matched
We match on what the conversation is about. Who is asking doesn't come into it.
A language model reads the conversation and your catalogue and scores how well each product fits that moment. Only products above a relevance threshold compete, and only one gets shown. If nothing fits well enough, we show nothing. That happens on roughly 85% of requests, and it's deliberate.
We use no cookies, device identifiers or advertising identifiers (IDFA/GAID), and we don't build profiles of users across apps. That also means no retargeting and no audience segments to buy. You're paying to appear when someone has just said what they want.
Commercials
| Model | You set | Best for |
|---|---|---|
| Target CPA | a flat dollar amount per order | most DTC and affiliate offers |
| Target ROAS | a ratio, e.g. 4 | catalogue advertisers with margin targets |
| CPC | a price per click | offers where the click is the product |
| CPM | a price per thousand placements | brand and awareness buys |
We don't price on a percentage of order value.
Internally we convert every bid to an effective CPM, so what counts is how much an offer earns per thousand placements. As a rough guide, a flat CPA of about $3 per order or a CPC of about $0.06 clears at typical match quality. Higher-ticket categories like travel, financial services, software and home clear comfortably.
You're only billed for placements people actually saw. An impression counts once it's 50% visible for one continuous second, which is the IAB standard. If a placement was issued and never seen, you don't pay for it.
Attribution and reporting
Every click carries a unique slot ID. If you work through an affiliate network, it also carries a sub-publisher ID for each app and placement, so you can trace traffic and conversions to a named property instead of an opaque redirect.
You can see which of your products ran, how well each one matched, and whether it was seen or clicked.
Counting sign-ups and sales
Every click lands on your page with utm_source=zeekend, utm_medium=ai_chat and utm_campaign=<your campaign ID>, so Zeekend shows up in Google Analytics, PostHog or whatever you already use, with no setup. Tags you set yourself are kept. The click ID rides along as zk.
To see sign-ups in your Zeekend dashboard, add the Zeekend Pixel to every page. You'll find it, ready to copy, in your dashboard under Settings → Zeekend Pixel:
<script async src="https://exchange.zeekend.com/v1/tag.js"></script>
<script>window.zeekend=window.zeekend||function(){(zeekend.q=zeekend.q||[]).push(arguments)};</script>
Then, where a sign-up succeeds:
zeekend("track", "signup", { id: user.id });
Use any event name (signup, trial, purchase, lead) and add value and currency for a sale. The pixel remembers the click for 30 days in a first-party cookie, shared across your subdomains, so a visitor who lands on www and signs up on app still counts.
For numbers nobody can tamper with, report from your server instead. The pixel stores the click ID in the zk_click cookie, which your backend can read at sign-up. Send it with the conversion key from your dashboard's Settings:
curl https://exchange.zeekend.com/v1/convert \
-H "Authorization: Bearer zkc_..." \
-H "content-type: application/json" \
-d '{"click":"<zk_click>","event":"signup","id":"user_123"}'
A conversion counts once per click and event, and once per id within a campaign, so a person who clicked twice and signed up once is one sign-up. Only a click we recorded, in the last 30 days, can be credited. Conversions are reporting only: you pay for views, never for a conversion.
Trials that turn into paid plans. If the payment happens later, in your billing system, the browser isn't there to send it. Save the zk_click value on the user when they sign up, then report a purchase from your server when the first payment succeeds (with value, currency, and the payment's ID as id), within 30 days of the click.
Check your install before launch. Settings → Zeekend Pixel gives you a test link with your own test click ID (zk_test_...). Open it, sign up, and the test conversions appear there within seconds, showing whether each came from the pixel or your server, and whether your server's key is right. Test conversions are never counted.
You never see what a user wrote, and you never see another advertiser's bid. Publishers only agree to carry this format because of that rule, so we don't make exceptions.
Category controls
Publishers decide what they'll run. These are the categories they block most often: financial, crypto, gambling, pharma, supplements, alcohol, tobacco, cannabis, adult, dating, weapons, politics, religion.
Ticketing, events, subscriptions and services usually run without restrictions. Fintech counts as "financial", so expect some publishers to opt out. Tell us your category and we'll tell you how much of our current inventory would accept it.
What we don't do
- No coupon, cashback, loyalty or deal placements
- No toolbar, browser extension or downloadable software
- No incentivised clicks
- No bidding on advertiser brand terms
- No cookie stuffing, and no clicks without a real user action
- No placement presented as the assistant's own recommendation
Where it runs
Consumer AI assistants. Chat apps on web, iOS and Android where people ask for recommendations as part of a normal conversation.
Coding agents. Tools developers use to write and ship software. When someone asks one where to deploy or which database to use, a relevant developer tool can appear in the answer.
Getting started
Send us your product catalogue as a Shopify store, a product feed or a CSV, and we'll generate the matching keywords and copy. Campaigns go live the same day. You don't need to place a tag or produce any creative.
hello@zeekend.com · https://www.zeekend.com
Technical detail, if your team wants it: https://exchange.zeekend.com/rest