Enablement Kit 01
Account Data Foundation
Targeting works consistently only when your systems agree on the account. This kit installs a governed foundation to increase match rates, eliminate misroutes, and ensure cleaner measurement.
Governance Modules
PROTOCOL_01
Domain Resolution
Why it matters: Signals often float unresolved due to aliases or subdomains.
Example: 'subsidiary-app.com' auto-resolving to 'GlobalParent.com'.
+ Domain Normalization Ruleset+ Alias Registry
PROTOCOL_02
Hierarchy & Buying Units
Why it matters: Enterprises buy at the P&L level, not just the brand level.
Example: Routing activity to the 'Cloud Security' owner vs. 'Global IT' owner.
+ Hierarchy Mapping Spec+ Buying Unit Definitions
PROTOCOL_03
ICP Fit Tiers
Why it matters: Treating every target the same dilutes your highest-potential plays.
Example: Tier 1 accounts trigger 1:1 ads; Tier 3 trigger 1:Many.
+ ICP Tier Rubric+ Fit-to-Play Mapping
PROTOCOL_04
Suppression & Exclusions
Why it matters: Marketing to current customers or competitors creates brand friction.
Example: Automating a 'Do Not Target' flag when an Opportunity hits 80%.
+ Suppression Registry+ Exclusion Governance Rules
PROTOCOL_05
Data Contracts & Lineage
Why it matters: Systems disagree over time without clear field-level ownership.
Example: CRM owns 'Stage', 6sense owns 'Intent Keyword'.
+ Field Ownership Matrix+ Lineage Map
What You Get
Strategic Specs
- Account Hierarchy Mapping Spec
- Buying Unit Definition Guide
- ICP Tiering & Fit Rubric
Operational Rules
- Domain & Alias Normalization Logic
- Suppression & Exclusion Registry
- Field-Level Data Contracts
