Skip to content
Automatizav1
CONNECTOR · SEGMENT

Segment — Web + mobile event router. We normalise, deduplicate, and fold into the warehouse marts.

CONNECTOR · SEGMENT

Segment

Web + mobile event router. We normalise, deduplicate, and fold into the warehouse marts.

  • categorySource · Event tracking
  • freshness targetHourly batch by default; minute-grain Personas if needed.
  • auth modelSource write key per environment.
  • sync modeWarehouse loader → staging → dbt → marts.
TABLES SYNCED

tracks, identifies, pages, screens. Per-event tables auto-created.

SCHEMA · SAMPLE
schema.sqlSQL
0
CREATE TABLE segment.signup_completed (
  id            TEXT,
  user_id       TEXT,
  received_at   TIMESTAMP,
  context_ip    TEXT,
  properties    JSONB
);
QUERY · SAMPLE
query.sqlSQL
SELECT date_trunc(0, received_at) AS d, COUNT(*) AS signups
FROM segment.signup_completed
WHERE received_at >= now() - interval 1
GROUP BY 1 ORDER BY 1 DESC;
OPS NOTES

The single biggest pitfall: anonymous_id ↔ user_id stitching across sessions. We test it on every PR with a deterministic fixture.

Wire a real pipeline to your warehouse

30-min stack review. We come back with a scoped plan, an owner, and a freshness contract. No SDR, no slide deck.