← How it works

Signal data flow

SourcesWebsiteProduct usageCRMEmail and adsEventsSupportSignal data layerIdentityRecords linked conservativelyConsentPreferences and opt-outsIntentMeaningful signal patternsEvent streamOne timeline, people andagentsOnly eligibledata passesAgentic HubDecides what to dowith each signal,within guardrailsAgents and channelsSales alertsBriefs for accountownersLifecycleTimely, consentedmessagesPaid mediaAudiences and budgetsContentTopics buyers askaboutOutcomesMeetings,pipeline,retentionAttribution and results feed back into the data layer
  1. Sources
    • Website
    • Product usage
    • CRM
    • Email and ads
    • Events
    • Support
  2. Signal data layer
    • IdentityLinked conservatively
    • ConsentPreferences, opt-outs
    • IntentMeaningful patterns
    • Event streamOne timeline
  3. Consent gate: only eligible data passes
  4. HubAgentic HubDecides what to do with each signal, within guardrails
  5. Agents and channels
    • Sales alerts
    • Lifecycle
    • Paid media
    • Content
  6. ResultOutcomesMeetings, pipeline, retention
  7. Attribution and results feed back into the data layer.
Signal data flow. A consent gate sits between the data layer and the hub, and results feed back into the data layer.

How data moves from its sources, through identity, consent, and intent processing, to the Agentic Hub and the agents and channels it coordinates, and how outcomes flow back as learning.

What each part does

01

Sources

Website, product usage, CRM, email and ads, events, and support all produce signals about buyers and customers.

02

Identity

Records are linked conservatively, because a false merge is worse than a missed one, and opt-outs propagate across linked records.

03

Consent

Preferences and opt-outs are stored reliably and applied before data reaches any agent.

04

Intent

Individual events are interpreted in combination, so a meaningful pattern is distinguished from noise.

05

Event stream

Human and agent actions share one timeline with consistent identifiers.

06

Consent gate

Only data eligible for the intended use passes to the hub. This check is enforced in code.

07

Hub, agents, and channels

The hub decides what to do with each signal within guardrails, often a brief for a person rather than an instant automated message.

08

Outcomes and feedback

Meetings, pipeline, and retention are attributed to the decisions that preceded them, and the results feed back into the data layer.

See the architecture in the product

Marketix is built on these diagrams: specialist agents, governed connectors, and a hub that plans, routes, and records every run. Sign up for early access.