Send events from anything that can make an HTTP request.

A subscription renewal, a background job, a webhook from your payment provider, a purchase confirmed after the visitor closed the tab — none of these happen in a browser, and none of them will reach a page tracker. Post them yourself.

An event carries the project's ingest key, a name, and the properties you choose. Supply the same visitor identity the browser used when you want a server event to join an existing journey.

The query API answers with aggregates for one project: traffic, goals, funnels, retention, and revenue over a range you name. It is the same data the dashboard reads, so a number in your own tool and a number on the screen come from one source.

A read key is scoped to reading. It cannot send events, change a project, or reach another project — the key decides, not the request.

An ingest key writes events and can do nothing else. A read key reads aggregates and can do nothing else. Neither can administer anything. Create them per project, rotate them when you need to, and revoke one without touching the other.

Set the allowed origins before you send from a browser context. Choose your privacy settings before the first event, not after.

The query API publishes an OpenAPI description you can generate a client from. The event endpoint is documented in the manual with a worked request.

Send one event and confirm it arrives in the project's first-event status. Verify one goal before you build a report on it.

If you are measuring a website, use the browser tracker: it handles navigation, engagement and single-page routing that a server cannot observe. The API is for what the browser cannot see, and for reading results back out.