Developer overview
The browser SDK, the tracking endpoint, the REST API and the MCP server at a glance, with install methods and the architecture.
On this page · 4 sections
Convultra has two surfaces for writing data and two for reading it. The browser SDK and the tracking endpoint record events. The REST API and the MCP server (both Beta) read them back. This page is the map.
Writing events
| Method | Install |
|---|---|
| CDN | https://cdn.convultra.com/ultra.min.js (production) or ultra.js (development) |
| Custom domain | https://track.yourdomain.com/v1/ultra.js, configured under Settings → Tracking → Custom tracking domains |
| Server-side | POST https://tracking.convultra.com/v1/track with your project key. See Server-side tracking explained |
| WordPress | The official plugin, downloaded from the Tracking health page |
There is no npm package. The browser SDK is a single script that defines a global Convultra object; in a bundled app load it from the CDN and call the global.
The browser SDK is about 10KB gzipped and loads asynchronously.
What you can do with it:
- Track conversions: purchases, leads, signups, subscriptions, downloads, contacts, bookings and custom events. See Tracking conversions.
- Enhanced conversions: send SHA-256 hashed customer data so ad platforms match more conversions. See Enhanced conversions in the SDK.
- E-commerce events: product views, add to cart, checkout, payment info, wishlists and search. See E-commerce events.
- Traffic analytics: pageviews, sessions, referrers, UTM parameters, click IDs and device data, all automatic.
- Server-side forwarding: conversions go to Google Ads and OpenAI Ads through their APIs today. Meta, Microsoft Ads and TikTok forwarding are coming soon.
Authentication for writes is the public project key (proj_...). It is write-only.
Reading data (Beta)
| Surface | URL | For |
|---|---|---|
| REST API | https://data.convultra.com/v1 | Warehouses, BI tools, scripts, cron jobs |
| MCP server | https://mcp.convultra.com/mcp | Claude, ChatGPT, Cursor and your own agents |
Both expose the same 21 operations and return the same numbers. Authentication is a secret sk_ key created under Settings → Developer, or OAuth for hosted assistants. Start with the API overview.
Architecture
Browser (SDK) Convultra server Ad platforms
------------- ---------------- ------------
Convultra.trackPurchase() ----> tracking.convultra.com/v1/track ----> Google Ads API (live)
OpenAI Ads API (live)
Meta, Microsoft Ads, TikTok (coming soon)
Your warehouse / assistant <---- data.convultra.com/v1
mcp.convultra.com/mcp
The browser SDK captures events and sends them to Convultra. The server enriches each one with the stored click ID, session context and hashed user data, deduplicates it, and forwards it to each connected platform through that platform’s server-side API. The read surfaces query the same store the dashboard uses.
Quick links
- Developer quickstart: first conversion in 5 minutes
- Installing the tracking script: stub + async, sync, async-only, bundled apps, custom domain
- Server-side tracking explained: click IDs, forwarding, and posting events from your backend
- Custom tracking domains: first-party tracking with one CNAME record
- API operations: all 21 operations and their traps
- Connect Claude: the MCP server in two clicks