Design source-tagging and attribution conventions
Defines the lightweight scheme for capturing awareness data — channel taxonomy, source-tag fields for intake forms or CRM, and logging rules — sized to a micro-firm so it is actually maintained.
In / outFirm channels, CRM or intake-form setup → attribution convention document (channel taxonomy, source-tag field definitions, logging rules)
You might say…
“I set up a tracking system once before and it collapsed in three weeks because it was too complicated — this designs the version that's just enough to be useful without requiring a full-time person to maintain it.”
What it does
Defines the lightweight scheme the team will use to capture awareness data — the channel taxonomy, the source-tag fields to add to intake forms or CRM, and the rules for how each inbound is logged consistently — sized to a micro-firm so it is actually maintained. Used when establishing or repairing the tracking system. Single human-in-loop design judgement; the qualitative setup decision behind the mechanics.
Trigger: Use when establishing or repairing the awareness tracking system from scratch.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation