Skip to main content

Market Center

📖 Best for: Marketing directors, operations managers, and department heads who need to break down marketing plans into executable tasks and track results

📖 Reading time: 8 minutes

📖 In one sentence: Market Center is the execution hub that decomposes marketing plans into trackable department- and individual-level KPI tasks. Through six core modules — Plan Workspace, Marketing Plans, Task Tree, Dispatch & Notification, Metric Dictionary, and Org Versions — it delivers real-time completion tracking, exception closure, and cross-team coordination.

Key Capabilities​

1. Marketing Plans & Plan Templates​

  • Full plan lifecycle: from draft, review, and active to archive — every plan keeps a complete version trail
  • Template library: convert proven plays (618, Double 11, product launches) into reusable templates that new plans can build on
  • Plans linked to task trees: each plan has a dedicated task tree that drills goals down to department and individual levels

2. Plan Workspace & Task Tree​

  • Unified dashboard: all in-flight marketing plans in one view — see completion, blockers, and owners at a glance
  • Three-level drill-down: from plan goal → department KPI → individual task, with drag-and-drop orchestration
  • Dependency mapping: parent-child and predecessor-successor dependencies visualized to prevent execution conflicts
  • Real-time status sync: when executors report progress in the client's "My Tasks" view, the workspace refreshes automatically

3. Department Dispatch & Cross-Team Collaboration​

  • Department dispatch: bulk-assign tasks by department or unit, auto-routed to individuals via the org version
  • Cross-team collaboration: multi-department tasks with separate primary and supporting roles, each with independent progress tracking
  • Task handoff: smooth ownership transitions with full historical traceability

4. Metric Dictionary & Unified Definitions​

  • Central registry: every KPI is registered with a unique name, unit, and formula in the Metric Dictionary
  • Cockpit metrics: six default metrics (sales conversion rate, gross margin, delivery cycle, inventory turnover days, complaint rate, labor cost-to-revenue ratio) auto-populated on first access
  • Three metric categories: result / process / people
  • Definition mapping: when the same metric has different definitions across departments or systems, record the differences in the definition mapping

5. Org Versions & Unit Management​

  • Org version snapshots: every org change (merger, split, addition) creates a new version for historical traceability
  • Unit tree: tree-structured org units with multi-level nesting
  • Members & definitions binding: every member is bound to their unit and the metric definitions that apply
  • Auto-bootstrap: org versions are created automatically when a department Agent is enabled — no manual setup needed

6. Dispatch & Notification​

  • Task dispatch: create a task under the current enterprise and assign an executor — the client's "My Tasks" view renders the report form
  • Rich task types: numerical (KPI, fill-in numbers) and milestone (checklist / progress) cover the full marketing spectrum
  • Custom report forms: beyond auto-generated fields, add custom fields (amount, progress, checklist) for mixed-metric tasks
  • Manual notification: send a one-off notification to a specific client (user or device) for testing or manual re-send
  • Idempotent overrides: use notification IDs to make repeat sends safe

7. Exception Closure & Offline Backfill​

  • Exception closure: automatic alerts for task blockers, metric anomalies, and collaboration conflicts, with time-bound response flows
  • Offline backfill: log marketing actions completed offline (field visits, trade shows, customer calls) after the fact
  • Audit trail: every exception and backfill action is recorded for audit

Typical Use Cases​

Use Case 1: Breaking Down a 618 Promotion Plan​

A marketing director creates a "618 Promotion Plan" using the "Big Promotion" template, with goals of 100M GMV and a 20% lift in sales conversion. In the task tree:

  • Marketing: 200 pieces of pre-launch content, 50 influencer partnerships
  • Sales: 50,000 cleaned leads, ≥ 80M closed deals
  • Customer Service: complaint rate < 0.5%, response time < 30s

Department owners report weekly progress in "My Tasks"; the marketing director monitors completion in real time on the Plan Workspace.

Use Case 2: Monthly KPI Dispatch to the Sales Department​

At the start of each month, the operations manager uses "Department Dispatch" to push monthly KPI tasks (sales conversion, new customers, collected revenue) to sales members. Task type is "numerical" — the form auto-generates number fields. Executors fill in daily; month-end summary rolls up automatically.

Use Case 3: Cross-Department New Product Launch​

Marketing, Sales, and Customer Service jointly execute the "Q4 New Product Launch" task. Marketing is primary; Sales and Customer Service are supporting. The task tree shows the dependency chain (marketing push → sales conversion → CS handover), and a collaboration group is auto-created. Each team's progress is tracked independently but rolled up into the plan's total completion.

Use Case 4: Logging Offline Marketing Actions​

A salesperson signs 30 leads at a trade show without a device. Afterward, they log the activity via "Offline Backfill" with customer name, contact, product interest, and follow-up status. The data rolls into the task tree without disrupting overall plan progress.

Use Case 5: Smooth Task Migration After Org Restructuring​

After the company splits Marketing into Brand and Growth teams, a new org version v2 is created. Tasks under v1 auto-migrate to the corresponding members in the new units, and historical attribution remains traceable by version number.

Interface and Operations​

1. Market Center (Left Navigation)​

The unified entry point for the Market Center module. Left nav includes: Market Center tasks, Plan Workspace, Marketing Plans, Plan Templates, Task Tree, Department Dispatch, Collaboration, Offline Backfill, Exception Closure, Metric Dictionary, Org Versions, Dispatch & Notification.

2. Plan Workspace​

  • Top data board: in-flight plans, pending tasks, exception tasks, and this-month completion rate
  • Plan card list: each card shows completion, owner, and due date
  • Quick actions: new plan, view task tree, view exceptions, export report

3. Marketing Plans​

  • Plan list: filter all plans by status, date, or department
  • Plan detail: basics, target metrics, linked task tree, and completion timeline
  • Create plan: select template → fill in goals → generate task tree draft → review → activate

4. Task Tree​

  • Tree view: multi-level structure from plan goal to individual tasks
  • Drag-and-drop orchestration: reorganize parent-child tasks by dragging
  • Dependency lines: visualize predecessor-successor relationships
  • Filters: by department, status, owner, or time window

5. Department Dispatch​

  • Department selection: choose target department from the org version
  • Bulk dispatch: upload an Excel task sheet or add manually; tasks auto-route to department members
  • Progress tracking: see how each department has received and completed tasks

6. Metric Dictionary​

Header note: this is the single source of truth for metric definitions — KPI task metric names MUST come from this dictionary; ad-hoc names are not allowed. The six cockpit metrics are auto-populated on first visit — skip the entry step and this hard check silently degrades, defeating the purpose.

List fields: metric name, category, unit, data source, formula, cockpit metric, enabled, actions.

Available actions:

  • Add metric: enter name, unit, formula, and select data source (biz / crm / ...)
  • Edit metric: adjust the formula or unit
  • Delete metric: only metrics not in use can be deleted
  • Enable / disable: disabled metrics cannot be referenced by new tasks; existing references are unaffected

7. Org Versions​

  • Versions tab: all version numbers, status, effective date, change type, and notes
  • Units tab: editable tree of the current version's org structure
  • Members tab: all members in the current version and their units
  • Definition mapping tab: record definition differences for the same metric across departments or systems
  • New version: create a new version after org changes to regenerate units, members, and definition mappings

8. Dispatch & Notification​

8.1 Dispatch Task Tab​

Create a task under the "current enterprise" and assign an executor. The client's "My Tasks" view renders the report form.

Form fields:

  • Task title (required)
  • Task description (required)
  • Task type: numerical (KPI, fill-in numbers) / milestone (checklist / progress)
  • Cycle type: daily / weekly / monthly / quarterly
  • Metric name (selected from Metric Dictionary)
  • Target value + unit
  • Executor (if not selected, the task is created at the enterprise level only and NOT pushed to any device)
  • Due time (optional)
  • Report form fields (optional): leave empty to auto-generate by task type; add custom fields (amount, progress, checklist) for mixed-metric tasks

8.2 Manual Notification Tab​

Send a one-off notification to a specific client (by user or device) — for testing and manual re-send scenarios.

Form fields:

  • Target type: online user (device follows the user) / online device (push to a specific device)
  • Select online user (multi-select)
  • Refresh online list: refresh the current list of online users / devices in real time
  • Notification title (required)
  • Notification content (required)
  • Category: Market Center (lands in the "..." category)
  • Level: normal / important / urgent
  • Notification ID (optional, for idempotent override): repeat sends with the same ID will be overwritten

Best Practices​

  1. Templates before customization: convert proven plays (618, Double 11) into templates first, then let new plans adapt them as needed
  2. Register before referencing: every KPI metric must be registered in the Metric Dictionary before it can be used in tasks — keeps definitions company-wide consistent
  3. Always create a new org version on changes: any org structure change (merger, split, personnel shift) must produce a new version to preserve historical attribution
  4. Pick the right task granularity: use "numerical" for KPIs filled by cycle; use "milestone" for multi-step tasks with checklists / progress
  5. Always select an executor explicitly: when dispatching a task, the executor is required; without one, the task stays at the enterprise level and never reaches any device
  6. Reserve manual notifications for testing and re-send: day-to-day notifications flow through "Dispatch Task"; use "Manual Notification" only for QA and exception recovery
  7. Set IDs on bulk notifications: for batch pushes, set a notification ID so repeats are overwritten instead of duplicated
  8. Bound exception response time: exception tasks (blocker, timeout, data anomaly) must be closed within 24h and counted into the owner's monthly review
  9. Backfill offline actions promptly: log offline marketing activities within 24h to avoid gaps in plan-level completion
  10. Verify cockpit metrics on first access: confirm the six cockpit metrics are auto-populated on first entry; otherwise the hard check silently degrades