Serge developer hub

How Serge works with your account

You create and own the platform ad account (OpenAI Ads Manager first) and invite Serge with a role you control and can revoke. Serge never owns the account, never holds ad budget, and never marks up spend — the networks bill you directly. Campaign setup, targeting, and pacing run from the Serge cockpit on your account.

First-party measurement

The Serge tracking snippet is one line on your site. It follows every ad click onto your own surface — sessions, carts, orders — and counts what each click returned, first-party, independent of platform reporting. It sets no cookies of its own, and captures an allowlisted set of campaign-attribution parameters (utm_* values and advertising click identifiers) from any landing URL that carries them — including advertising you run outside Serge. Enable consent mode if you need that held until your visitor opts in.

Install happens in the app, under Site: copy the one-line script tag and your public token. A first-party proxy option serves the snippet from your own domain, which reduces the impact of third-party script blocking.

MCP server

The Serge MCP server connects your LLM client — Claude, Cursor — to your Serge workspace, so you can ask about your measured traffic and sessions in plain language. Authentication is via OAuth (your Serge login) or a workspace API key.

MCP server overview · Setup guide

Machine-readable resources

For LLMs and crawlers that want the product described in their own format: llms.txt is the concise product description, llms-full.txt the extended version. Both are kept current with the product.

llms.txt · llms-full.txt

What is coming

The dashboard that shows platform-reported numbers next to the first-party count — and campaign creation + reporting APIs (built on the platforms' Advertiser and Insights APIs) — are on the roadmap as the cockpit automates the concierge workflow. The snippet and the MCP server documented here are live today.