Skip to content

Sources

A source is any system Signals ingests customer data from. Website, app and messaging sources send events as they happen. CRM, database, warehouse, file and lead generation sources are pulled frequently by Signals, so changes reach your destinations without you triggering anything.

  1. In your project, go to Sources and pick the system from the catalog below.
  2. Authenticate it. Each source page documents exactly what access is required (OAuth, API key, database credentials, or bucket access).
  3. Choose what to read: objects, tables, event types, or file paths.
  4. Map fields to the Signals event model, including every identifier you can provide.
  5. Test with a limited sync or a test event, then enable it.

The full lifecycle is described in Connecting sources & destinations.

  • API: send events directly from your own backend over HTTPS.
  • App: stream in-app events from iOS and Android.
  • CRM: sync leads, contacts, and deal stages from your CRM.
  • Database: query customer and transaction tables where they live.
  • E-commerce: capture storefront and order events at the platform level.
  • File & storage: ingest CSV, JSON, and spreadsheet exports from buckets, drives, and FTP.
  • Lead generation: capture native lead form submissions in real time.
  • Warehouse: query modeled conversion and audience tables in BigQuery or Snowflake.
  • Web: collect browser events from your website with the Datahash tag.

Which categories fit which jobs is defined per use case; see the compatibility matrix on each use case page.