foothint
Log inStart free

Every event. Every account. The ones about to leave, up top.

A founder opens Pulse once. Quiet accounts sit at the top. The feed keeps moving underneath.

Copy a key, send one request from your server, and the event is on Pulse. No website domain to connect.

Start freeRead the docs

Three steps. Then you are on Pulse.

  1. Copy the key

    It lives on the first screen after you sign up. Put it on your server.

  2. Send one event

    Paste the command, or send it from that screen. The event shows up immediately.

  3. Name the account

    Add account_id on the next request. Health starts from that, not from a domain.

See which customer went quiet.

Health is a score on the account row, worst first. Under 50 is overdue. When an account goes quiet for 7 days, an alert fires on its own.

The feed is whatever you send.

You do not set the event list up first. The first request creates the row. Later ones with the same name count.

Funnels show where people stop.

Name the steps as events you already send. Conversion is against the previous step. Dropped people are listed, not hidden in a chart.

Alerts

A line was crossed, or an account went quiet. The note stays in the app. Slack is optional.

People

Every person behind an account, last seen, and how far they reached in a funnel.

Keys

Live and test API keys in Settings. Rotate either without leaving the workspace.

Seats

Invite the CS lead. Free, Starter, Pro, and Enterprise, billed monthly.

The request is the product.

Channel, event name, and the account it belongs to. Pulse, the feed, and health follow from that.

Start free
POST /v1/log
Authorization: Bearer ft_live_...

{
  "channel": "payments",
  "event": "Invoice Paid",
  "account_id": "harbor-freight",
  "notify": true
}

Start today. First event in five minutes.

Open a workspace, copy the key, and send the first event.