Skip to main content
Biqli gives your consent manager explicit controls. Biqli does not decide which consent category or legal basis your site requires.
Grant consent after your consent manager approves the relevant category:
Withdraw it with:
The SDK:
  • clears stored click attribution;
  • clears queued browser events;
  • does not decorate outbound links;
  • rejects tracking calls with consent_required.
Granting consent captures an eligible bq_id still present in the current URL and resumes queue delivery. It cannot recover a click ID that has already been removed from both the page and storage.

​
Script-tag setup

These options solve different problems:
  • consent: false prevents attribution storage, outbound decoration, and event delivery.
  • manualStart: true delays navigation listeners and automatic queue flushing until start() is called on the SDK instance.
Use the consent setting to represent consent state. Use manual startup when your application controls SDK lifecycle explicitly.

​
Server-side tracking

Browser consent state does not automatically control your backend. Before calling @biqli/sdk, biqli/sdk, or the server tracking API, your application must check the consent or legal-basis state stored for that user. Do not trust a browser checkbox alone for this decision. Persist consent through your authenticated application flow, enforce it again on the server, and retain any records your applicable policy requires.