Core Concepts

1DB is easiest to reason about when you separate capture, normalization, and delivery. These concepts show how the product is structured.

Websites

A website is the top-level workspace for a public lead source. It owns domains, forms, source settings, CRM connections, and the leads captured from that surface.

Forms

Forms define the shape of data you accept. They map front-end field names to the canonical lead record stored in 1DB and can fan out to notifications, webhooks, and CRM sync.

Leads

A lead is the normalized record written after submission. It keeps the submitted data plus metadata like timestamps, source website, form slug, attribution parameters, and delivery state.

Delivery and Sync

After capture, 1DB can route the record to HubSpot, Salesforce, webhooks, email notifications, or internal workflows. Delivery configuration lives alongside the website and form.

Typical Request Flow

  1. A visitor submits a form or a server sends a lead payload.
  2. 1DB validates the incoming fields against the form definition.
  3. The lead is written with normalized fields and attribution metadata.
  4. Configured sync targets and webhooks run after the record is accepted.
  5. Your team searches, filters, and routes the resulting lead inside the dashboard.

Plan your schema before shipping

Keep field names stable, prefer canonical keys like `email`, `name`, and `phone`, and treat custom fields as extensions rather than your primary model.

Authentication

Secure your API keys and server-side submission flow.

Webhooks Guide

Push lead events into your own systems after capture.