LeadPass.
One pass of the beat that walks signals to leads: every rung of every kind of buyer bound to a brand run over its population, a candidate made or lifted for each entity a rung admits, judged when it holds what the qualifying rung asks, a lead made from a qualified candidate with its temperature, and each lead…
Figure 1LeadPassspecified
- kind
- work
- scope
- platform
- key
- the beat’s tick
- store
- postgres
- family
- rules_engine
Fields#
| field | type | required | note |
|---|---|---|---|
kinds_of_buyer | count | yes | bound to a brand and ready |
rungs_run | count | yes | |
rungs_not_ready | count | yes | a rung whose predicate is not kept, or does not compile |
units_read | count | yes | |
candidates_lifted | count | yes | made or moved up a rung |
qualified | count | yes | |
not_a_buyer | count | yes | |
leads_made | count | yes | |
delivered | count | yes | |
withheld | count | yes | at the plan’s limit, or with no plan |
deferred | count | yes | left for the next tick by the beat’s budget |
tenants_served | count | yes | |
at | time | yes |
Routes that use it#
No route takes or returns LeadPass directly. The record holds it, and the objects that point at it reach it.