Skip to main content
Conversion tracking connects a lead or sale to an earlier Biqli visit. Enable conversion tracking on the short link, then use the workspace publishable key or a supported commerce integration to report the conversion. The publishable key is designed for client-side conversion events. Restrict it to the websites that are allowed to send events. Do not use a secret workspace API key in browser code. After setup, test with a real visit through the short link before sending the conversion. A conversion without a usable attribution visit might not appear under the expected link.

​
Set up tracking

  1. Enable conversion tracking on the short link that starts the journey.
  2. Create or review the workspace publishable key.
  3. Add the website origins allowed to send browser-side events.
  4. Install the supported event call or commerce integration on the conversion page.
  5. Visit the short URL in a clean browser session and complete a test lead or sale.
  6. Confirm the event appears under the expected link and customer report.
Lead and sale events should use stable external identifiers so retries can be handled safely by the implementation. Revenue and currency must describe the actual eligible sale value supplied by the integration.

​
Protect the integration

The publishable key is limited but should still be origin restricted. Workspace API keys are secrets and must remain on a trusted server. Never include either kind of key in a URL or analytics parameter. If attribution is missing, confirm that the visitor first passed through the Biqli link, storage was not blocked, and the event was sent from an allowed origin.