Marketing analytics

DenialOS captures a small set of marketing conversion signals: demo CTAs, enterprise CTAs, integration/documentation views, form submissions, contact CTAs, and calendar clicks.

The browser creates a pseudonymous local session identifier. The server hashes it before storage. Marketing events store only event type, path, optional referrer, and bounded non-PHI metadata.

No patient, claim, clinical, or authentication data is intentionally accepted by this endpoint. Analytics failures fail open and do not block the public user journey.

Production reporting requires the configured PostgreSQL database.

Lead requests

The public contact form accepts business contact information, a monthly denial-volume range, role, integration interest, and a problem statement. The submitter must attest that the message contains no PHI. The server validates this input, stores a minimal lead record when PostgreSQL is available, and sends a sales notification through the configured email provider.

If email delivery is temporarily unavailable after durable lead persistence, the API returns an accepted/delayed state so a qualified request is not lost.