Capture

Track events from your backend

Send signups, upgrades, billing changes and other events the browser never sees.

Get an API key

Read the docs ↗

Input

An event

Output

Event recorded

Against the same identity as web and email

Not affected by ad blockers

Request parameters

Dataset

si: the dataset the event belongs to.

Session

sid: ties the event to a browsing session.

User

uid: your own identifier for the person.

Email

email: identifies the person directly.

Web, email and server events are stored in one stream against one identity.

One GET request from any backend

// send an event from your backend
export async function track({ sessionId, userId, email }) {
  const url = new URL("https://log.leadboxer.com/")
  url.searchParams.set("si", process.env.LEADBOXER_DATASET_ID)
  url.searchParams.set("sid", sessionId)
  url.searchParams.set("uid", userId)
  url.searchParams.set("email", email)
  await fetch(url)
}

// send an event from your backend
export async function track({ sessionId, userId, email }) {
  const url = new URL("https://log.leadboxer.com/")
  url.searchParams.set("si", process.env.LEADBOXER_DATASET_ID)
  url.searchParams.set("sid", sessionId)
  url.searchParams.set("uid", userId)
  url.searchParams.set("email", email)
  await fetch(url)
}

Use cases

Track product usage

Send the events the browser cannot see.

Backfill history

Load past activity into a profile.

Add billing signals

Join revenue events to behaviour.

Avoid ad blockers

Browser extensions cannot block server requests.

Where this sits

One stage of a five-stage pipeline. The same platform captures behaviour, identifies the company, enriches the record, scores the fit and sends the result to your systems.

Capture

website
email
forms
server

↑ you are here

Capture

website
email
forms
server

↑ you are here

Identify

IP → company
identity
stitching

Identify

IP → company
identity
stitching

Enrich

firmographics
contact data