Signals
What people watched, searched for and subscribed to, sent as signed webhooks to the tools you already run.
01 · Customers interact
Product Hub, live events
14:07:02update_center_viewed
14:07:04release_page_viewed
14:07:09update_video_started
14:07:21update_video_progress
14:07:26search_performed
14:07:27search_result_clicked
14:07:44cta_clicked
14:07:58subscribe_form_submitted
14:08:02subscriber_created
14:08:10chapter_clicked
14:08:19update_video_completed
14:08:31crawler_visit
14:08:40filter_applied
14:08:52latest_page_viewed
14:07:02update_center_viewed
14:07:04release_page_viewed
14:07:09update_video_started
14:07:21update_video_progress
14:07:26search_performed
14:07:27search_result_clicked
14:07:44cta_clicked
14:07:58subscribe_form_submitted
14:08:02subscriber_created
14:08:10chapter_clicked
14:08:19update_video_completed
14:08:31crawler_visit
14:08:40filter_applied
14:08:52latest_page_viewed
02 · Signals signs and sends a batch
{ "events": [
{ "event": "update_video_progress", "progress": 50, … }
{ "event": "search_performed", "query": "sso", … }
{ "event": "subscriber_created", "consent": {…}, … }
{ "event": "cta_clicked", "host": "app.acme.com", … }
] }
Up to 50 events per delivery · event_id stable across retries
X-DemoBites-Signature
t=1788703651,v1=5f1c9a0e4d7b…b27d
HMAC SHA256 with your endpoint secret
03 · Your systems decide
An example delivery · Names and fields from the event reference
Near real time, about a minute
GPTBot, ClaudeBot, PerplexityBot and others.
Subscriber events also carry the email and its consent record.
X-DemoBites-Signature
t=1788703651,
v1=5f1c9a0e…b27d
Signed payloads
Verify each one with your secret.
DemoBitesupdate_video_completedsearch_performedsubscriber_createdfilter_appliedPick the events
Per event, never all or nothing.
Test event
Check your receiver before real traffic.
{ "events": [
… up to 50
] }
Batched
Up to 50 events per delivery, in one array.
Six attempts, then auto pause
Retries
A dead receiver never retries forever.
Delivery log and replay
Failed ones replay from the log.
event_id stays stable across retries
Dedup on event_id
Safe to process twice, counted once.
Three endpoints
Warehouse, staging and an alert relay.
Unknown visitor
no name, no email
A visitor stays anonymous
Session context only. No identity invented.
dana@example.com
subscriber_created
consent.granted_at 14:08:02Z
consent.source update_center
A subscriber is known
They gave an email, with a consent record.
demobites
session_id
event_id
your warehouse
user
account
You join the rest
Match events to your users in your own data.
Endpoints that receive subscriber events process personal data
What we claim
What we never claim
No backfill. Streaming starts when the endpoint connects
Analytics in DemoBitesSignals · Part of Growth, from $20 a month