| name | sales-kevel |
| description | Kevel platform help — API-first ad server infrastructure for building custom ad platforms (sponsored listings, native ads, email ads, retail media networks), Decision API, Campaign Management API, Inventory API, UserDB, Audience segmentation, Forecast API. Use when setting up Kevel to serve ads in your newsletter or app, Decision API requests are returning empty or wrong ads, campaign management API calls are failing or flights aren't pacing correctly, email ad impressions are inaccurate due to Gmail caching or image proxying, ad reporting is too basic and you need custom analytics from raw logs, or building a custom ad server for your marketplace or publisher network. Do NOT use for general newsletter monetization strategy (use /sales-newsletter) or programmatic email ads without engineering resources (use /sales-admailr or /sales-paved). |
| argument-hint | [describe your Kevel ad server question or custom ad platform goal] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","newsletter","advertising","ad-server","retail-media","platform"] |
| github | https://github.com/adzerk |
Kevel Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
-
What are you trying to do?
- A) Build a custom ad server for my app, marketplace, or publisher network
- B) Serve ads in email newsletters via Kevel
- C) Integrate the Decision API to request and render ads
- D) Manage campaigns, flights, and creatives via the API
- E) Set up audience segmentation and targeting
- F) Troubleshoot ad serving, reporting, or pacing issues
-
What type of ads are you serving?
- A) Sponsored listings / native ads (marketplace, ecommerce)
- B) Display ads (banners, image ads)
- C) Email ads (newsletter ad insertion)
- D) Video / DOOH / audio ads
- E) Internal promotions / house ads
-
Technical context: Language/framework, current ad serving setup (if any), scale (daily requests)
Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
Step 2 — Route or answer directly
| If the question is about... | Route to... |
|---|
| Newsletter monetization strategy (not ad serving infra) | /sales-newsletter [question] |
| Programmatic email ads without building a custom server | /sales-admailr [question] or /sales-paved [question] |
| Email deliverability (SPF/DKIM/DMARC) | /sales-deliverability [question] |
| CRM integration patterns | /sales-integration [question] |
If the question is Kevel-specific, continue to Step 3.
Step 3 — Kevel platform reference
Read references/platform-guide.md for the full platform reference — capabilities, pricing, data model, email ad setup, integration recipes, code examples.
Read references/kevel-api-reference.md for API endpoint details, authentication, request/response formats, and SDK links.
Answer the user's question using only the relevant section. Don't dump the full reference.
Step 4 — Actionable guidance
Focus on the user's specific situation:
