Skip to Content
Quick Start

Quick Start

Get your first beet running in under 5 minutes.

1. Create an account

Go to heartbeet.downfall24.com/sign-up . No credit card required.

2. Create a beet

After signing in, you’ll be prompted to name your organisation and create your first dashboard.

Then click + Add Beet in the sidebar. Give it a name that describes the event you want to monitor — e.g. checkout.complete, cron.nightly_report, or payment.webhook.

Each beet gets a unique ingestion token.

3. Embed the snippet

Heartbeet accepts a GET or POST request to its ingestion endpoint. Three integration options:

HTML (no JavaScript)

Drop a 1×1 pixel image anywhere in your HTML — a page, an email, a server-rendered template:

<img src="https://heartbeet.downfall24.com/api/v1/beet/YOUR_TOKEN" width="1" height="1" alt="" style="display:none" />

Works everywhere that loads images. No JavaScript required.

JavaScript (fetch)

Call from any JavaScript context — browser or Node.js:

fetch('https://heartbeet.downfall24.com/api/v1/beet/YOUR_TOKEN', { method: 'POST', keepalive: true, })

Use keepalive: true in browser contexts so the ping completes even if the page unloads immediately after.

Shell / cron

Add to the end of any shell script or cron job:

curl -s "https://heartbeet.downfall24.com/api/v1/beet/YOUR_TOKEN" > /dev/null

4. Verify the first ping

After embedding the snippet and triggering the event once, return to the Heartbeet dashboard. Your beet’s Last Seen widget should show “just now”.

5. Add widgets

Click the beet in the sidebar to open its detail page, then add widgets to your dashboard to visualise the data. See Dashboard Guide → Widgets for the full widget reference.

6. Wait for your baseline

Heartbeet needs 14 days of data before it can establish a reliable baseline and begin alerting. During this period, the status widget shows Learning. You can see the countdown on the beet detail page.

Once the baseline is established, Heartbeet will alert you automatically when the event rate drops below normal for the current time window.

What’s next?