Server tracking is the recommended path for events your backend can verify, especially payments, subscriptions, renewals, and account creation.
Before you start
- Open Workspace settings -> Tracking and enable conversion tracking.
- Open Workspace settings -> API Keys.
- Create a Restricted key with Conversions -> Write.
- Store the
biqli_... key in a server secret or environment variable.
- Capture the browser’s
bq_id during signup or checkout.
Never return this key to a browser or place it in a client bundle, URL, cookie, public repository, screenshot, or log.
TypeScript and Node.js
PHP
Forward the click ID safely
Read bq_id in the browser and associate it with the authenticated signup, checkout, or customer session on your server. Do not accept a browser-supplied customer owner ID without authenticating it.
After Biqli has attributed that customer, later events may omit clickId and use the same customerExternalId.
Retry safely
Official server SDKs retry temporary network errors and retryable HTTP responses with bounded backoff.
- Give each lead a stable
eventId.
- Give each sale a stable
paymentProcessor and invoiceId.
- Keep the payload identical across retries.
Do not create a new identifier on every attempt.
Confirm the event
Open Customers, select the matching customer, and confirm the timeline shows the expected click, lead or sale, attribution link, amount, and source. 
