RESEARCHED · 2026.09.12-g40 · not deployed

G26 — Search-to-lead and customer-journey graph

179 words. Researched design, reviewed 2026-09-12: a library view or proposed design with its sources stated; not a deployed system, a live audit or a provider requirement. Source: Graph/G26-search-to-lead-and-customer-journey-graph.md. Graph systems, shelf 5 of 8; library release 2026.09.12-g40.

Status
NEW RESEARCHED DESIGN; not deployed
Reviewed
2026-09-12
Nature
custom measurement view
Priority
P1
Accountability
R16, R03, R12, R20

Question

Which observed discovery events connect to actual business outcomes?

Nodes

Referral; Session; Event; Durable inquiry; Qualified lead; Outcome

Relationship sketch

  • permitted session → observed event
  • inquiry → qualification decision
  • outcome → attributed evidence

Evidence inputs

Authorized analytics and backend events, consent-aware identifiers, actual qualification and outcome records.

Implementation

Start from accurate business-state transitions. Preserve attribution uncertainty, unknown origin, and missing identifiers; do not stitch anonymous people across contexts without authority.

Acceptance checks

  • Submit success does not substitute for durable acceptance
  • Lead definitions are explicit
  • Unknown attribution remains unknown rather than allocated to AI

Do not infer

A crawler request, indexed page, citation, click, and sale are different observations.

Publication boundary

Private by default; aggregate only with appropriate review.

Source basis

S22, S14, S42. See Research/sources.json. Sources support the primitives or named technology. The organization, labels, actions, and acceptance contracts in this catalog are this library's design, not claimed provider requirements.

Back to the shelf in the room · Graph systems