Skip to main content
A publishable key lets approved websites send client-side tracking events to a workspace. It starts with biqli_pk_ and is different from a secret workspace API key.

​
Configure browser tracking

1

Open Tracking

Select the workspace, then open Workspace settings -> Tracking.
2

Add allowed hostnames

Add every website that is allowed to use the key. Enter only a hostname, such as example.com, not https://example.com/pricing.
3

Generate the key

Generate a publishable key and copy it into the approved website installation.
4

Save changes

Select Save changes. Unsaved hostname and key changes are discarded when the page reloads.
An exact rule such as example.com does not include its subdomains. A wildcard rule such as *.example.com includes subdomains but not the apex domain, so add both rules when you need both. You can include a port for local development, such as localhost:3000.

​
Rotate or revoke the key

Regenerate the key if someone who should not have it may possess it, or if an old deployment still contains it. The previous key stops working immediately after the regenerated value is saved. Revoke the key when the workspace should no longer accept browser tracking. Remove hostnames that the workspace no longer controls.
Never put a biqli_... workspace API key in browser code. It is a server secret. Only the limited biqli_pk_... publishable key belongs in a website.
Developers can read Tracking credentials and the browser quickstart for installation details.