---
name: adgentek
description: Integrate the Adgentek Ad Server. Publishers monetize AI apps, agent surfaces, and article pages with conversation-native ads using the Web SDK, upcoming native SDKs, Spark Ad Unit, or AdsMCP. Advertisers configure conversion tracking. Triggers on "Adgentek", "adgentek.ai", "adsmcp", "monetize my AI app", "ads in AI chat", "conversational ads", and "track conversions".
---

# Adgentek Integration

Adgentek provides three integration surfaces:

1. **Publisher SDKs and Spark Ad Unit** for monetizing AI apps and article pages.
2. **AdsMCP** for MCP-capable agent surfaces.
3. **Conversion tracking** for advertisers measuring campaign outcomes.

Before using any documentation URL, fetch and read the docs sitemap:

https://docs.adgentek.ai/llms.txt

Prefer sitemap-discovered URLs over the hardcoded URLs below if they differ.

## Procedure

### Step 1 - Confirm the product

Strong cues for **Publisher integration**:

- AI chatbot, assistant, or agent project; a chat UI in the codebase
- User mentions "monetize", "revenue", "ads", or "show ads"
- Article or CMS templates are present

Strong cues for **Advertiser conversion tracking**:

- Marketing site or landing page
- User mentions "pixel", "conversions", "ROI", or "campaign performance"

If ambiguous, ask which one.

### Step 2 - Confirm the publisher integration path

Prefer evidence from the project over asking:

- HTML with script tags, or any browser-based web app including React or Vue: use the
  **Web SDK**. A dedicated React SDK is coming soon; until it ships, integrate React apps
  with the Web SDK.
- `Podfile` or `Package.swift`: the **iOS SDK is coming soon**. Do not invent an iOS
  package or installation. Contact the publisher's Customer Success representative for
  early access and current integration options.
- `build.gradle` or `settings.gradle.kts`: the **Android SDK is coming soon**. Do not
  invent a Maven artifact or installation. Contact the publisher's Customer Success
  representative for early access and current integration options.
- Article page templates or a CMS: the **Spark Ad Unit is coming soon**. Contact the
  publisher's Customer Success representative for early access.
- MCP server configuration or an agent runtime without a rendering client: use
  **AdsMCP**.
- Any other architecture: contact the publisher's Customer Success representative
  before implementing.

Before wiring AdsMCP, read:

https://docs.adgentek.ai/publishers/choosing-your-integration-path

Tell the user which demand classes their surface qualifies for. Headless surfaces get CPA
and filtered CPC demand, not CPM.

### Step 3 - Follow the matching integration page

- Web: https://docs.adgentek.ai/publishers/integrations/web
- React: https://docs.adgentek.ai/publishers/integrations/react
- iOS: https://docs.adgentek.ai/publishers/integrations/ios
- Android: https://docs.adgentek.ai/publishers/integrations/android
- Spark Ad Unit: https://docs.adgentek.ai/publishers/integrations/publisher-widget
- AdsMCP: https://docs.adgentek.ai/publishers/integrations/adsmcp

For AdsMCP, verify live tool names by listing tools on
https://mcp.adgentek.ai/mcp rather than hardcoding them. MCP clients may sanitize
registered names that contain punctuation.

### Step 4 - Get the real token

Ask the user for their publisher token if it is not in the codebase. Never leave
placeholders such as `YOUR_PUBLISHER_TOKEN` in delivered code; placeholders do not
serve ads.

### Step 5 - Verify before declaring done

Do not claim the integration is complete until:

- A serve request fires and returns a payload on a commercial-intent conversation turn.
- The ad renders in the target surface.
- For browser or app surfaces, the impression request fires from the client on render.
- Clicks use the click URL from the payload, never the advertiser destination directly.
- For AdsMCP, delivery is confirmed when the response requires it.
- Impressions and clicks appear in publisher reporting.

## Tracking rules

- The Web SDK handles publisher-side rendering and tracking automatically.
- Never fire impression URLs from a backend, Worker, or server. Server-originated
  impressions are classified as invalid traffic and discarded.
- Never fire impression URLs from AdsMCP. Headless surfaces cannot verify impressions;
  confirm delivery through the documented tool when required.
- Always use the Adgentek click URL rather than linking directly to the advertiser.

## Common gotchas

- Never invent SDK APIs, tool names, parameters, or endpoints. Verify every symbol
  against the live documentation before writing code.
- The React, iOS, and Android SDKs and Spark Ad Unit are not yet generally available.
- Keep Placement IDs stable because they anchor reporting and policy assignment.
- Custom parameters are reporting-only and do not affect targeting or pricing.
- Test mode intentionally reports zero revenue.

## References

- Docs sitemap: https://docs.adgentek.ai/llms.txt
- Quickstart: https://docs.adgentek.ai/publishers/quickstart
- Integration guidance: https://docs.adgentek.ai/publishers/choosing-your-integration-path
- Tracking rules: https://docs.adgentek.ai/publishers/concepts/tracking-and-measurement
- AdsMCP: https://adsmcp.ai
- Contact: hello@adgentek.ai
