Getting Started
Proxy Quickstart
MonetizationOS proxy workers run at the edge on your CDN, intercepting HTML responses to apply server-side monetization decisions — no changes to your origin code required.
How it works
Every proxy implementation follows the same pipeline: fetch the origin response, resolve the user's identity, call the Surface Decision API, and apply personalization transforms to the HTML before it reaches the browser.
To learn more about what proxies are and when to use them, see the Proxies concept page. For a detailed breakdown of the shared proxy pipeline, see the Proxies reference.
Server-side vs client-side integration
| Approach | Best for | Trade-offs |
|---|---|---|
| Server-side (CDN proxy) | Static sites, edge-rendered HTML, consistent behavior for users and bots | Requires CDN setup and worker deployment |
| Client-side SDK | Rich SPA customization, browser-only interactivity | Depends on JavaScript execution in the client |
Use a CDN proxy when you want response transformation and monetization logic enforced at the edge.
Choose your provider
Select your CDN provider below to follow the quickstart guide.