Billing integration
This section covers the event collection used by a Billing integration. The Website SDK collects browser interactions; server events send configured business events from your backend.
Installing the SDK or creating an API Key does not create a billing contract or activate charges. Collection, event acceptance, attribution and billing are separate steps.
Choose a path
| Path | Use it for | Credentials |
|---|---|---|
| Website SDK | Collect website interactions with HTML or JavaScript, manage consent and obtain a visitor ID. | A public Website install ID; never a secret API Key. |
| Server events | Send an already configured business event from your backend with Python or Go, and retain the server receipt. | An API Key with Write permission and access to the brand, plus the configured event. |
Choose one reporting path for the same event. Do not send the same event through both paths. If the backend needs a website visitor ID, pass the ID to your backend without also reporting that same event from the browser. Your application decides when the event happens.
Before integration
- Select the intended brand and obtain its Website install ID.
- For backend reporting, create an API Key and confirm that the business event is configured. A measurement-only connection cannot accept server business events (
422 server_event_not_configured). - Follow the Website SDK or server events chapter, including consent, credentials and visitor association requirements.
- Check the API reference for responses and errors.
What a response proves
getVisitorId()only reads an ID; it does not report an event.- Browser collection does not verify a business outcome or prove site ownership. Its measurement response has no receipt ID.
- A server event receipt can support troubleshooting and retry handling.
202means accepted or queued, not that the business outcome, attribution or billing succeeded. - Whether an accepted event is billable depends on the configured event and contract, not on installing the SDK or creating a key.
MCP Server is a separate integration using OAuth. It is not one of these event-reporting paths.