Signals

Web Signals

Track website page views, identity, company association, and shared artifact engagement from the browser.

#Overview

Web signals are browser-side events sent with a public write key. By default, the SDK only sends events after a visitor is identified or grouped to an account.

#Authentication

Use a public write key in browser code:

Authorization: Bearer public_wk_your_key_here

Public write keys can only ingest events through /v1/events and /v1/events/batch. Use secret sk_... keys for server-side API access.

#Source

When creating a browser-side custom signal, set the signal source to web. This keeps browser-generated events separate from server-side API events and makes the signal available for web tracking flows.

#Identity Model

The browser tracker stores a generated anonymous visitor ID in local storage. You can then attach a known user and/or a company group:

bigmindWeb.identify("person@example.com", {
  email: "person@example.com"
});

bigmindWeb.group("example.com", {
  domain: "example.com"
}, { type: "account_domain" });

To allow anonymous events, opt in explicitly:

bigmindWeb.configure({
  anonymousEvents: true
});

#Built-in Web Signals

Signal When it fires Required data fields
web-page-viewed A known visitor views a page. anonymous_id, page_url, page_path
web-identity-identified A visitor is identified. anonymous_id, user_id
web-group-associated A visitor is linked to an account. anonymous_id, group_type, group_id
web-share-email-identified A share visitor is identified. anonymous_id, email, account_domain, share_id, source
web-share-page-opened A shared page is opened. anonymous_id, share_id, account_domain

#Common Data Fields

All built-in web signals include the shared browser context below when available:

  • anonymous_id — stable browser visitor ID
  • user_id and user_email — known identity after identification
  • group_type and group_id — company or account group after association
  • page_url, page_path, and page_title — current browser page context
  • referrer and user_agent — browser attribution context

#Custom Web Events

You can create your own event signals with source web and emit them from the browser:

bigmindWeb.event("pricing-calculator-used", {
  plan: "enterprise",
  seats: 120,
  source: "pricing_page"
});

Custom web events use the current known identity: account domain if grouped, then known user. Anonymous events are skipped unless anonymousEvents is enabled.

Trackable links add a short, one-time k parameter to a URL. When opened, the browser redeems the token, stores the identity or company association locally, removes the parameter, and then emits the regular web signals for the page.

A trackable link can target either one known recipient email or anyone at a company domain. Subsequent page views use the locally stored identity; anyone else receiving the already-redeemed link must identify normally.

Updated 5/22/2026