Docs

How Analytics Works

Analytics combines confirmations and check runs, and can be filtered by site, form, and date range. At form level, metrics focus on one form; at broader scope, data is aggregated.

About Email Processing

We use Resend for receiving form confirmation emails. When an email arrives:

• Resend temporarily stores the email (per their retention policy)
• We extract only the timestamp and sender metadata
• We never read, store, or process the email body or attachments
• The email content is not accessed or used by us in any way

What Data Is Tracked

• Confirmations: form ID, source (manual/email/webhook), timestamp, and small metadata.
• Check runs: check type, status, timestamps, HTTP status, response time, and error details.
• Alerts: type, severity, message, created/resolved timestamps.
• Configuration: site/form settings, thresholds, learning state, tags, and notification preferences.

Alerts older than about 60 days are removed automatically, keeping your alert list focused on recent issues.

Whitelisted Emails (Ignored Activity Emails)

At organization level you can define a list of email addresses to ignore for activity monitoring. If any ignored email appears in an inbound confirmation payload, that event is skipped entirely.

• No confirmation record is created.
• No analytics/event tracking is added for that inbound email.
• No downstream alert behavior is triggered from that ignored inbound message.

This is useful when customers or internal teams submit test entries using known email addresses.

Privacy Notes

FormPulse is designed to monitor operational signals, not store full submission content. For inbound activity filtering, payloads can be inspected in-memory to match ignored/whitelisted emails, then discarded without creating a confirmation.