Resolve · Step 1
Sources & intake
Upload taxonomy exports from each system. Resolve detects fields, values, and conflicts across all sources — then recommends how to reconcile them into a single canonical vocabulary.
Taxonomy sources
Upload CSV or XLSX exports from each system — HubSpot, Salesforce, Marketo, DAM, or any tool with a picklist or field schema
📋
No sources yet — upload taxonomy exports to begin
CSV or XLSX · HubSpot properties, Salesforce picklists, Marketo tokens, DAM schemas
No existing taxonomy?
Resolve will propose a standard starting vocabulary based on industry best practice
Add at least one source to analyze
Resolve · Step 2
Conflicts
Cross-system mismatches detected. For each conflict, accept the recommendation, choose a source, or define your own canonical value.
0
Conflicts detected
0
Resolved
0
Pending
Run source analysis to detect conflicts
Resolve · Step 3
Canonical taxonomy
The locked vocabulary — terms your team and all downstream tools (Visualize, Execute) use. Add, edit, or mark each term as defined or pending.
Run analysis or propose a standard taxonomy to populate this view
Resolve · Governance
Naming convention
The canonical naming pattern enforced across all campaigns, assets, and records. Approve, reject, or edit before locking.
Pattern
[Product] — [Region] — [Motion] — [Quarter]
Example
Strategy Sprint — North America — Referral — Q3 2026
Advisory Retainer — EMEA — Content — Q4 2026
Advisory Retainer — EMEA — Content — Q4 2026
Status: Pending approval
How naming is used
The naming convention flows into Execute — all generated campaign names, asset filenames, and CRM record names follow this pattern automatically. Approving it here locks the pattern across all downstream tools.
Resolve · Governance
Governance rules
Rules enforced at tagging time. Blockers prevent an asset from being published. Warnings flag for review. Info rules are advisory only.
Resolve · Final Step
Approve & Lock
Complete the readiness checklist below before locking the taxonomy. Once locked, Execute and Visualize will use this as the canonical vocabulary for all campaign and content outputs.
Readiness checklist
All four signals must be green to lock
Complete all readiness checks to lock