> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spineworkspace.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Marketing System Flow: Data Journey from Source to Workbench

> The ten-step system path for Marketing: how Spine ingests automation, analytics, and CRM data, normalizes it, and projects it into campaign and funnel views.

The Marketing system flow describes how raw data from your marketing automation, advertising, analytics, and content tools becomes the unified context you see in SpineWorkspace. It runs continuously, but understanding the path helps you diagnose reporting gaps and trust the projections.

<Steps>
  <Step title="Intake">
    Spine polls or receives webhooks from HubSpot, Marketo, Salesforce, Google Analytics, LinkedIn Ads, Segment, and Notion.
  </Step>

  <Step title="Load">
    Raw records are ingested into Spine staging with source metadata and ingestion timestamp.
  </Step>

  <Step title="Normalize">
    Records are mapped to the Spine entity schema: Campaign, Audience, Content, Lead, Attribution, Channel, Program, and Event.
  </Step>

  <Step title="Schema Mapping">
    Cross-system matching links UTM parameters to campaigns, emails to leads, and page paths to content assets.
  </Step>

  <Step title="Context Assembly">
    Spine builds campaign graphs by joining performance metrics, lead flow, content assets, and revenue data.
  </Step>

  <Step title="Projection">
    The assembled graph is filtered and shaped into domain views: Campaign Performance, Attribution Funnel, Content Pipeline.
  </Step>

  <Step title="OODA">
    Twin observes projected state, orients to campaign health models, and decides whether to surface an alert.
  </Step>

  <Step title="Governance">
    Every projected view respects source-system permissions and domain guardrails before rendering.
  </Step>

  <Step title="Execution">
    When you invoke a capability, Spine routes the call to the correct connector with scoped authorization.
  </Step>

  <Step title="State Update">
    Writeback responses update the local projection, trigger events, and refresh dependent views.
  </Step>
</Steps>

## Related

* [Marketing Overview](/internal-docs/domains/marketing/index)
* [Spine Fabric](/internal-docs/domains/marketing/spine-fabric)
* [Execution Flow](/internal-docs/domains/marketing/execution-flow)
* [Spine Fabric Platform](/platform/spine-fabric)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.