Skip to main content
Biqli shows which short-link visits become customers, leads, and sales. You can add tracking with a browser SDK, a server SDK, a direct REST request, or a supported integration. This guide helps you choose the safest path before you write code.

​
Start with the journey

  1. A visitor opens a conversion-enabled Biqli short link.
  2. Biqli records the click and forwards its click identifier as bq_id.
  3. Your website captures that identifier.
  4. Your application identifies the visitor with a stable customer ID.
  5. Your browser or server reports a lead or sale.
  6. Biqli connects the conversion to the workspace, customer, click, and link.
A click is the attribution starting point. A customer is your stable identity for a person or account. A lead is a meaningful non-revenue action. A sale is a confirmed revenue event.

​
Choose an implementation

Browser tracking

Capture bq_id, track browser-side events, and support single-page applications.

Server tracking

Send trusted leads and sales from Node.js, Next.js, PHP, Laravel, or REST.

Stripe

Attribute confirmed Stripe payments from verified webhooks.

Shopify

Connect a Shopify store and use Biqli’s managed conversion flow.

​
Browser versus server tracking

Most production applications use both. The browser captures the click ID and forwards it to your backend. The backend sends the trusted conversion. If this is your first tracking integration, read these pages in order:
  1. How attribution works
  2. Choose the correct credential
  3. Understand customers and events
  4. Complete the browser quickstart
  5. Move trusted events to the server quickstart
  6. Use Debug tracking before launch

​
What Biqli protects for you

  • Workspace-scoped credentials and data isolation
  • Allowed-origin checks for browser tracking
  • Permission checks for secret API keys
  • Stable public resource identifiers
  • Idempotent lead and sale creation
  • Preserved attribution when a link is later deleted
  • Structured errors and request IDs
You still need to protect secret keys, choose stable customer and event identifiers, request consent where required, and send only events your application has verified.