1 min lesson
Instrument at the source
Walk through the worked example in "Instrument at the source", then explain what it demonstrates.
Step 1 of 2
Instrument at the sourcethe workflow emits the events
You can't measure what the workflow doesn't emit. Build the event emission into the automation itself, so every enrichment, score and route writes a structured record at the moment it happens. Bolting analytics on afterward gives you gaps exactly where the system failed.
{
"event": "lead.routed",
"lead_id": "ld_8f21",
"account_id": "ac_03b9",
"score": 82,
"owner": "rep_14",
"rule": "segment_round_robin_v3",
"sla_target_min": 15,
"routed_at": "2026-06-15T17:04:22Z",
"idempotency_key": "ld_8f21:routed:v3"
}A program that re-scores itself from real outcomes and re-orders its enrichment waterfall by cost-adjusted hit rate is a self-improving primitive, not a one-off campaign. That's the difference between "I ran a program" and "I built infrastructure the next ten programs reuse."
"I instrument every workflow step to emit a structured event, join outcomes back to the original score weekly and let the model re-fit against what actually converted. The same emission feeds drift alerts, so a slipping match rate pages me before it dries up pipeline."
Learn more
Optional practice