Overview
Verified impressions over time
By campaign
| Campaign | Impressions | Clicks | CTR | Est. spend | Last served |
|---|---|---|---|---|---|
| No verified impressions in this range yet. | |||||
Campaigns
New campaign
Your campaigns
No campaigns yet — create one above to start serving.
Ad Groups
A lightweight, organizational layer over campaigns — for grouping creative variants under one name for reporting. It doesn't change targeting or serving; every campaign still competes for slots independently in adselect.js.
New ad group
Your ad groups
No ad groups yet.
Assets
Upload an image
Your assets
No assets yet — upload one above.
Reports
Verified impressions & clicks
| Group | Impressions | Clicks | CTR | Est. spend |
|---|---|---|---|---|
| No data in this range yet. | ||||
Docs & API
Everything below matches the deployed worker exactly — there's no separate "real" API behind it.
/v1/adFetch a raw JSON ad payload. Always $0 — nothing is billed on a fetch, only on a verified impression.
curl https://worker.lemprage.cobinar.com/v1/ad \ -H "X-Lemprage-Api-Key: YOUR_KEY"
Response includes headline, body, image_url, cta_link, brand_name, category, and a security block with a single-use impression_id + signing_key your SDK uses to sign the Proof-of-Impression, a click_signing_key + click_expires_at for the independent click credential below, plus a hidden _canary_pixel — never request it from real code.
/v1/impressionsSubmit a signed Proof-of-Impression once an ad has been ≥50% in viewport for ≥1s with window focus. This is the only call that results in a charge. content_hash is optional — the default card's renderer sends a hash of what it actually rendered, so the Worker can catch the creative being altered after it was served; a custom onRender integration has no reliable way to compute this and omits it, which the Worker treats as "not checkable," not invalid.
POST /v1/impressions
{
"impression_id": "...",
"poi": { "viewportRatio": 0.8, "dwellMs": 1400, "windowFocused": true, ... },
"signature": "HMAC-SHA256(signing_key, JSON.stringify(poi))",
"content_hash": "sha256 hex, or null"
}
-> { "status": "verified", "billed": true, "content_verified": true|false|null }
/v1/clicksSubmit a signed click credential, issued alongside the ad and independent of the impression proof — a visitor can click before, after, or without ever triggering a verified impression. Analytics only for now; billing is still impression/CPM-based. Same content_hash as above, same purpose — for a click this is the one that matters most, since a swapped cta_link here means sending a visitor somewhere the advertiser never approved.
POST /v1/clicks
{
"impression_id": "...",
"signature": "HMAC-SHA256(click_signing_key, 'click:' + impression_id)",
"content_hash": "sha256 hex, or null"
}
-> { "status": "verified", "tracked": true, "content_verified": true|false|null }
/v1/billing/payment-intentAdvertiser-authenticated. Requires Authorization: Bearer <Firebase ID token>. Creates a Stripe PaymentIntent for an embedded, in-page payment form — not a redirect. The Billing page mounts a Payment Element with the returned clientSecret and confirms it without leaving the dashboard.
POST /v1/billing/payment-intent
Authorization: Bearer <id token>
{ "amountCents": 2500 }
-> { "clientSecret": "pi_..._secret_..." }
Client SDK
Published at https://lemprage.cobinar.com/sdk/lemprage-sdk.js — a plain script, no build step. Wraps everything above end to end: fetches the ad, renders a default card (or hand it onRender to fully control the markup), watches real viewability and visual safety, and signs + submits both the Proof-of-Impression and a click credential automatically. See /sdk/test.html for a working example against your own key.
Settings
API key
No key yet. Generate one to start requesting ads from worker.lemprage.cobinar.com.
Shown once. Store it now — Lemprage can't show it to you again.
Key active and ready.
Test a key
Allowed domains
Your key won't serve any ads until at least one domain is added here — this isn't optional, it's the difference between "anyone who finds this key can use it anywhere" and "only your site can."
No domains yet.
Ad categories
Only these categories will ever be served on your site. Leave everything unchecked to accept all categories.
Billing
Ad balance
Spent against campaign delivery. Balance updates a few seconds after a payment confirms — Stripe's webhook, not this page, is what credits it.
Add funds
Payment received — your balance updates automatically once Stripe confirms it, usually within a few seconds.
Admin
Publishers
—
Campaigns
—
Verified impressions
—
Verified clicks
—
Fraud blacklist
IPs blocked by the canary honeypot, ASN filtering, bot score, or a signature mismatch — see fraud.js.
| IP | Reason | Blocked | |
|---|---|---|---|
| Loading… | |||
Grant admin
Promotes another signed-up account to admin. They'll need to sign out and back in for it to take effect.