$npx -y skills add sales-skills/sales --skill sales-advertserveAdvertServe platform help — cloud-hosted ad server since 1998 for B2B and niche publishers with display, video, mobile, and email ad serving, 101-tier zone prioritization, campaign management, geo/keyword/weather targeting, IVT filtering, header bidding via Prebid.js, white-label
| 1 | # AdvertServe Platform Help |
| 2 | |
| 3 | ## Step 1 — Gather context |
| 4 | |
| 5 | If `references/learnings.md` exists, read it first for accumulated platform knowledge. |
| 6 | |
| 7 | 1. **What are you trying to do?** |
| 8 | - A) Set up AdvertServe to serve ads on my website |
| 9 | - B) Serve ads in my email newsletter |
| 10 | - C) Manage campaigns and advertisers via the API |
| 11 | - D) Configure targeting (geo, keyword, weather, contextual) |
| 12 | - E) Set up header bidding with Prebid.js |
| 13 | - F) Compare AdvertServe to other ad servers |
| 14 | |
| 15 | 2. **Your role?** |
| 16 | - A) Publisher (monetizing my own site/newsletter) |
| 17 | - B) Advertiser (placing ads on publisher sites) |
| 18 | - C) Ad agency (managing multiple clients) |
| 19 | - D) Ad network operator |
| 20 | |
| 21 | 3. **Current plan**: 45-day free trial or paid ($299/mo base)? |
| 22 | |
| 23 | Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2. |
| 24 | |
| 25 | ## Step 2 — Route or answer directly |
| 26 | |
| 27 | | If the question is about... | Route to... | |
| 28 | |---|---| |
| 29 | | Newsletter monetization strategy (subscriptions, pricing models) | `/sales-newsletter [question]` | |
| 30 | | Programmatic/RTB ad serving | `/sales-epom [question]` or `/sales-adbutler [question]` | |
| 31 | | Self-serve advertiser portal | `/sales-adbutler [question]` | |
| 32 | | Direct-sold ad management for local publishers | `/sales-broadstreet [question]` | |
| 33 | | Free self-hosted ad server | `/sales-revive [question]` | |
| 34 | | Email deliverability (SPF/DKIM/DMARC) | `/sales-deliverability [question]` | |
| 35 | |
| 36 | If the question is AdvertServe-specific, continue to Step 3. |
| 37 | |
| 38 | ## Step 3 — AdvertServe platform reference |
| 39 | |
| 40 | **Read `references/platform-guide.md`** for the full platform reference — capabilities, pricing, email ad setup, API overview, integration recipes, code examples. |
| 41 | |
| 42 | Answer the user's question using only the relevant section. Don't dump the full reference. |
| 43 | |
| 44 | ## Step 4 — Actionable guidance |
| 45 | |
| 46 | Focus on the user's specific situation: |
| 47 | |
| 48 | - **Publisher getting started**: Create zones (Banner/Text/VAST Video/Dynamic), create campaigns with media, assign campaigns to zones via tiers (1-100 priority), generate ad tags via Code Wizard, paste into your site. Ads rotate automatically. |
| 49 | - **Email newsletter ads**: Use the Code Wizard to generate "E-mail" code (Banner type). This produces a static `<a>` + `<img>` tag (no JavaScript). Paste into your ESP template. Image-only creatives — no HTML5 or rich media in email. |
| 50 | - **API automation**: Enable API in Settings > Basic > API. Get your secret key. Make HTTP GET/POST requests to `/servlet/control/api/{module}/{action}` with the `secret` parameter. Responses in JSON (`output=json`) or XML (default). |
| 51 | - **Choosing AdvertServe vs alternatives**: AdvertServe is best for mid-to-large publishers wanting a feature-rich hosted ad server with video, header bidding, and white-label. For budget hosting, use AdSpeed ($9.95/mo). For self-hosted free, use Revive. For self-serve portal, use AdButler. |
| 52 | |
| 53 | If you discover a gotcha, workaround, or tip not covered in `references/learnings.md`, append it there. |
| 54 | |
| 55 | ## Gotchas |
| 56 | |
| 57 | > *Best-effort from research — review these, especially items about integration gotchas that may be outdated.* |
| 58 | |
| 59 | 1. **Email ads must use the E-mail code format** — the Code Wizard generates JavaScript tags by default. For newsletters, explicitly select the "E-mail" code type to get static IMG tags. JavaScript won't render in email clients. |
| 60 | 2. **Image format restrictions** — code-based images are not accepted. Creatives must be JPEG, GIF, or PNG files. If a client provides HTML5 or code-based images, you'll need to convert them. |
| 61 | 3. **Click tags can be confusing** — understanding how to use tracking pixels and click tags has a learning curve. Use the Code Wizard's generated tags rather than building manually. |
| 62 | 4. **API documentation is technical** — the docs assume familiarity with HTTP APIs and programming. Non-technical users should use |