Test

Events and metrics — is it working?

Track what your users actually do — events and metrics, built in, so you can tell a validated idea from a dud.

shovelbase.signals.track("round_logged", {
holes: 18, course_id,
})
// no third-party pixel · it's your data
Events

Track what happens in your app without a third-party pixel.

Metrics

Signups, activation, retention — the numbers that say whether it's working.

One place

No separate analytics product to wire up. It's already in the console.

1Signals

See what people actually do

Track the moments that matter in your app and watch them add up — no third-party pixel, it's your own data.

  • Track real events Log what happens without bolting on a tracker.

  • It's your data No vendor in the middle — the backend already knows.

Events this week+24%
MTWTFSS
2Signals

The numbers that tell you it's working

Sign-ups, activation, retention — the handful of numbers that separate a validated idea from a dud, all in one place.

  • Signups to retention The metrics that say whether the idea has legs.

  • Already in the console No analytics product to wire up.

Sign-ups
1,248
+8%
Activation
63%
+4%
Retention
41%
+2%
Active now
312
live

What you'd build with it

The kind of problem Signals is there to solve.

Use case
See if the new feature landed

Track whether people actually use the scorecard you just shipped — in your own data, not a vendor’s.

Use case
Watch activation climb

See how many sign-ups reach the first real moment of value, and whether last week’s change moved it.

Use case
Know before you build more

Tell a validated idea from a dud before you pour another month into it.

No analytics vendor to bolt on. The backend already knows what's happening — Signals just shows you.

Compare shovelbase →

The rest of the stack