Lead source taxonomy governance teams can maintain
Keep acquisition definitions useful across marketing, sales, reporting, and system changes.
Name the decision the taxonomy supports
State whether the team needs acquisition reporting, routing, budget learning, partner credit, or seller context. One field rarely answers every attribution question. Write definitions with inclusions, exclusions, examples, owner, and effective date. Keep original source separate from latest interaction and campaign membership.
Design for observable evidence
Choose values people and systems can assign from evidence such as referral data, submitted forms, event attendance, partner registration, or seller creation. Include an unknown path. Honest uncertainty is safer than forcing each record into a favored channel or inferring source from a company name and memory.
Map every creation path
Inventory forms, imports, integrations, enrichment, events, partner portals, manual entry, APIs, and product signups. For each path, record raw evidence, mapping, fallback, overwrite behavior, owner, and monitoring. Preserve raw values when systems disagree instead of selecting whichever value makes a dashboard look cleaner.
Control definition changes
A proposed value needs a business question, clear boundary, source evidence, expected volume, reporting impact, routing impact, and migration decision. Publish who approves changes and when they take effect. Backfilling old records requires its own evidence standard because a current definition does not prove historical meaning.
Monitor assignment quality
Sample records from every creation path and compare assigned values with raw evidence. Track missing, overwritten, contradictory, and overused fallback values. Give frontline teams an exception route with record, evidence, expected value, and affected process. Operations owners decide whether the record or the definition is wrong.
Report with honest limits
Show source with confidence, time period, collection gaps, and attribution method. A CRM field is an operational classification, not causal proof of why buyers engaged. Quarterly governance should retire unused values, repair mappings, review unknowns, and confirm that each remaining category still supports an actual decision.
When a leader asks for a new breakdown, test whether existing campaign or interaction fields already answer it before expanding the primary taxonomy. Keeping the main classification stable helps sales and marketing compare periods while detailed analysis can use the more specific evidence stored elsewhere.
Include a definition link beside recurring reports so a reader can check what each value means for that period. When collection changes, annotate the effective date and affected creation paths. This prevents a mapping repair from being mistaken for a sudden channel shift. If the unknown share rises, investigate which source stopped providing evidence before reallocating attention or budget. The taxonomy should help operators ask better questions; it should not hide collection failures behind a complete-looking chart.
Sources
- Traffic-source dimensions, Google Analytics Help. Distinguishes source, medium, campaign, and attribution scopes.
Related GTM guides
Frequently asked questions
Should original source change?
Usually it remains historical. Corrections need source evidence, a reason, and approved policy.
How many values should a lean team use?
Use the smallest set that supports decisions and can be assigned consistently from evidence. A value should have a distinct operating meaning, an owner, and examples that separate it from neighboring categories. Put campaign detail in the appropriate fields instead of expanding the primary source list until operators cannot apply it reliably.