Every marketing team that adopted MQLs built a machine that measures activity, not intent. The number it reports to the board has almost nothing to do with whether someone is actually going to buy. Signal-based marketing is the operational framework that fixes this. Instead of waiting for a prospect to fill a form, signal-based marketing detects behavioral and contextual signals and routes prospects into the right program automatically. This article covers the marketing-owned half of that system: four concrete workflows that replace MQL-based programs, a paid activation playbook, and a signal-level attribution model that holds up in a CFO conversation.
One scope note before we start: this article does not cover signal types, tiering models, or the Clay build walkthrough. Those live in the signal-based GTM pillar post, and linking to that post rather than duplicating it is how we build cluster authority. What follows is the marketing execution layer only.
The MQL Was a Workaround, Not a System
The MQL was not designed to measure buying intent. It was invented to solve a coordination problem between marketing and sales teams that were arguing about lead quality, and it became the dominant metric because it was easy to count, not because it was accurate.
What the MQL actually measures is marketing activity: a contact filled a form, downloaded a PDF, attended a webinar, and crossed a point threshold. That activity is a proxy for interest at best. At worst, it captures competitive researchers, students, and SDRs doing prospect research, and treats them the same as a VP of Revenue actively evaluating solutions.
According to Forrester Research, a significant share of MQLs are never contacted by sales, and MQL-to-pipeline conversion rates at most B2B companies hover below 1%. Sales teams have learned to ignore MQL alerts because the quality variance is too high. A VP of Marketing who just attended your webinar and a junior analyst doing a school project both generate an MQL in most legacy setups.
The deeper structural problem is that MQLs create a hand-off trigger without encoding context. When a sales rep receives an MQL, they know a contact did something. They don't know why the account is interesting, which signals preceded that action, or how likely this account is to convert compared to others in the queue. Signal-based demand gen fixes that by making the why explicit in the trigger condition.
Why MQL Volume Is the Wrong North Star
There is a specific incentive problem embedded in MQL-based marketing programs. If MQL volume is the metric that marketing reports to leadership, marketing optimizes for form-fill volume. That means more gated content, more webinar registrations, more "download the guide" CTAs. None of these actions reliably predict pipeline.
Gartner research on B2B buyer behavior estimates that buyers spend only 17% of their total purchase process meeting with potential vendors. The rest happens in research they do independently: analyst content, peer reviews, community discussions, category forums. That dark funnel activity is real buying behavior, and the MQL completely misses it.
An account with three employees each downloading a whitepaper registers as three MQLs in most marketing automation platforms. That same account reading your pricing page four times over two weeks while comparing you on G2 registers as zero MQLs if none of those employees fill a form. Signal-based marketing captures the second scenario and acts on it.
The Specific Coordination Failure
The MQL hand-off tells sales that someone did something. A signal-based hand-off tells sales that an account is in-market. Those two things drive completely different outreach approaches.
When a signal bundle fires, the CRM entry includes the trigger conditions: this account is ICP-matched, has accumulated third-party intent on your category, visited the pricing page twice this week, and has two known contacts in the system. Sales does not need to start cold. Marketing has already moved the account into a retargeting campaign. The context travels with the alert.
How signal-based marketing changes the demand generation trigger, measurement, and reporting model compared to the MQL system.
| Dimension | MQL System | Signal-Based System |
|---|---|---|
| Trigger | Contact fills a form | Account hits a defined signal bundle |
| What it measures | Marketing activity | Buying intent signals |
| Downstream action | Sales follows up on contact | Sales receives account context; marketing activates in parallel |
| Reporting metric | MQL volume, MQL-to-SQL rate | Signal-touched accounts, signal-to-opportunity rate |
| Data encoded | Contact action | Account-level signal stack plus ICP fit |
What Signal-Based Marketing Actually Means
Signal-based marketing is the practice of triggering every marketing program action from a behavioral or contextual signal rather than from a time-based batch or form fill. When an ICP account hits your pricing page, that signal fires a paid retargeting action. When an account's intent score crosses a threshold, that signal fires a nurture sequence. When a combination of signals accumulates, that signal fires a sales hand-off alert.
This is the marketing-owned definition. For the signal taxonomy, tiering model, and the technical build in Clay, the signal types, tiering model, and Clay build walkthrough covers all of that in depth. What this article addresses is what the marketing team does with signals once they exist.
Signal-driven marketing is distinct from traditional marketing automation in one important way: automation fires on schedules, signal-driven marketing fires on triggers. A drip sequence sends email 2 on day 7 regardless of what the contact did or didn't do after email 1. A signal-driven sequence sends email 2 when the contact opens email 1 and visits a case study within 48 hours. The timing shifts from calendar-based to behavior-based, and that shift in timing is where the performance difference comes from.
The Marketing-Side Signal Stack
Marketing teams own three categories of signals, distinct from the sales-side signals (job changes, funding rounds, outreach responses) that belong to the outbound motion.
First-party behavioral signals come from your own properties: website visits to high-intent pages (pricing, case studies, competitor comparison pages), email opens and click patterns, return visit frequency, and session depth on category-specific content. These signals are free, highly accurate, and available to any team running basic analytics or a CRM with behavioral tracking.
Third-party intent signals tell you that an account is researching your category on properties you don't own: review sites, analyst content, industry forums, and topic-monitoring platforms. Intent data providers aggregate this activity and surface it as account-level scores. Bombora, G2 Buyer Intent, and Demandbase are common sources. The key is treating intent data as one input into a signal stack, not as a standalone action trigger.
Firmographic context is not a signal in itself, but the filter that determines whether a signal warrants a marketing action. An ICP account hitting your pricing page gets entered into a paid retargeting audience. A non-ICP account hitting the same page gets nothing. ICP filters prevent wasted spend on accounts that will never convert regardless of how many signals they generate.
What Signal-Based Marketing Is Not
Three clarifications that prevent common implementation mistakes.
Signal-based marketing is not the same as "using intent data." Intent data is one input into the system. A team that buys Bombora and uploads a monthly CSV to LinkedIn has intent data, but does not have signal-based marketing. The difference is orchestration: signals need to trigger automated marketing actions, not manual list uploads.
Signal-based marketing is not account-based marketing. ABM is a targeting strategy that defines which accounts to pursue. Signal-based marketing is the triggering mechanism that determines when and how to pursue them. The two complement each other, but they answer different questions.
Signal-based marketing is not outbound sequencing. When a signal fires a sales hand-off, sales takes the account through an outbound motion. That motion is a separate discipline covered in the outbound pillar. This article covers what marketing does in parallel: the programs, targeting, and attribution on the marketing side.
The marketing-side signal stack: signals are filtered through ICP criteria and routed to the correct marketing program automatically.
The Four Marketing-Owned Signal Workflows
Signal-based demand gen replaces four categories of batch-and-blast marketing programs with four signal-triggered equivalents. Each workflow has the same structure: a trigger condition, a marketing action, and a clear difference from the legacy approach.
Workflow 1: Signal-Triggered Paid Audience Sync
The legacy paid marketing approach: upload a static account list to LinkedIn or Meta, run campaigns against it for 30 days, update the list once a month. The result is that you're running ads to accounts that were in-market last month, not accounts that are in-market today.
Signal-triggered paid activation changes the audience membership criteria from "this account is on our target list" to "this account is on our target list AND has hit a signal threshold in the last N days."
The trigger condition example: account matches ICP firmographic criteria (industry, headcount, revenue range) AND has visited the pricing page at least once in the last 14 days AND has no active opportunity in CRM. When those three conditions are true, the account enters the LinkedIn Matched Audience for your "pricing consideration" campaign. When any condition becomes false (opportunity created, page visit drops off, 30 days expire), the account exits the audience automatically.
Tools that make this work: HubSpot's LinkedIn integration for CRM-based audience sync, RB2B or Clearbit Reveal for identifying anonymous visitors and pushing them into HubSpot, and Clay for managing enriched account lists that feed into paid platforms. The sync cadence matters: daily is ideal, weekly is the minimum for this to function as a signal-based system rather than another slow list upload.
Workflow 2: Signal-Triggered Website Visitor Routing
Every website visitor should have a routing decision applied to them. Who is this account? What signals have they shown? What is the right next action?
The legacy approach: all website visitors see the same experience and enter the same generic nurture sequence, if they enter anything at all.
Signal-based routing applies different downstream actions based on visitor signals. An identified ICP account visiting the pricing page gets a sales alert fired and enters a paid retargeting campaign. An anonymous visitor from a known target company domain gets passed to an identification tool (RB2B, Clearbit Reveal, or KickFire) and, once identified, routed to the appropriate workflow. An existing customer visiting a competitor comparison page triggers a customer success alert, not a marketing campaign.
Trigger condition example: company domain identified via RB2B, company record in HubSpot matches ICP criteria, contact property "Last High-Intent Page Visit" is within the last 7 days. Action: enroll in HubSpot workflow that fires a sales alert and simultaneously adds the company to the LinkedIn Matched Audience for retargeting.
The routing decisions happen in HubSpot workflow branches, Segment event triggers, or directly in your CMS if it supports behavioral rules. Each visitor category gets a defined action, not a default to "do nothing."
Workflow 3: Signal-Driven Lifecycle and Nurture Triggers
Time-based nurture is one of the highest-leverage things to replace with signal-based triggers.
The legacy approach: email 1 at day 0, email 2 at day 7, email 3 at day 14. The sequence fires on a calendar, not on the contact's behavior. The result is emails landing when the contact is not paying attention and irrelevant follow-up when the contact has already moved on.
The signal-driven approach: each nurture step fires when a specific behavioral signal occurs. A contact opens email 1 and visits a case study within 48 hours. That pattern of signals fires email 2, which references the specific case study they read and asks a relevant question. If the contact opens email 1 and does nothing, the system waits for a return visit signal before sending email 2.
This is not more complex to build in HubSpot than a traditional sequence. It requires behavioral triggers in workflow enrollment conditions and branch logic that checks for the presence or absence of a signal event. The practical setup: create contact properties for "Last High-Intent Page Visit Date" and "Last Signal Event Name," and use those properties as branch conditions in your nurture workflows.
The timing difference matters: HubSpot's research on email timing consistently shows engagement peaks when follow-up aligns with the prospect's own research activity. Signal-triggered sends naturally align with that activity because they fire in response to it.
Workflow 4: Signal-Based MQL Replacement (The Hand-Off Threshold)
This is the most direct structural replacement for the traditional MQL. Instead of "contact filled a form and crossed a point threshold," the hand-off trigger is "account has accumulated a defined signal bundle."
A signal bundle example for a mid-market B2B SaaS company: ICP firmographic match (confirmed) + Bombora intent score above 60 for primary category + pricing page visit in last 30 days + at least two known contacts engaged in last 60 days. When all four conditions are true, the marketing-to-sales hand-off fires automatically.
What gets logged in CRM at hand-off: the specific signal that completed the bundle (which condition triggered the alert), the entry date for each condition, the list of engaged contacts, and the account's current position in any active paid or nurture campaigns. Sales receives an account package, not a contact record with a single form-fill note.
Dynamic lead scoring is the infrastructure underneath this workflow. The signal bundle uses the same lead scoring architecture but replaces static point values with dynamic, time-windowed conditions. If you already have a lead scoring model, the migration path is to convert each scoring criterion into a time-windowed signal condition. The detailed approach to building that model is at the lead scoring architecture post.
Signal-Triggered Paid Activation: The Full Mechanics
Paid audience syncing based on real-time signals is the most underused marketing workflow in B2B. Most teams use LinkedIn or Meta for top-of-funnel awareness and manage audiences with monthly manual uploads. Signal-triggered activation turns paid media into a precision instrument that concentrates spend on accounts actively in a buying cycle.
Three paid activation patterns cover most B2B signal-based marketing scenarios.
Pattern 1: ICP In-Market Audience
Audience condition: Account matches full ICP criteria (industry, headcount, revenue, geography) plus an elevated intent score from a third-party provider (Bombora topic surge above threshold, G2 category research activity, or Demandbase intent score) plus no active opportunity in CRM.
Platform: LinkedIn Matched Audiences (company list) or LinkedIn Predictive Audiences if using native LinkedIn intent data.
Campaign type: Awareness and consideration content. Not direct response. Goal is presence and brand recall during active research. Case studies, analyst content, category positioning.
Refresh cadence: Daily if your CRM-to-LinkedIn sync supports it. HubSpot's native LinkedIn integration syncs company lists on a schedule; Clay can push updated lists via CSV or API depending on your setup.
Pattern 2: Pricing-Page Retargeting
Audience condition: Contact or identified company visited the /pricing page (or your equivalent high-intent page) in the last 21 days, and matches ICP firmographic criteria.
Platform: LinkedIn for identified contacts, Meta for broader retargeting reach, Google Display for retargeting at scale.
Campaign type: Proof content. The account has shown transactional intent; show them evidence they are making the right decision. Customer quotes, ROI data, implementation case studies.
Exit condition: Account creates an active opportunity in CRM, or 60 days pass without a return site visit.
Pattern 3: Competitive Consideration Response
Audience condition: Account visited competitor comparison pages on your site or is identified through G2 Buyer Intent as actively reviewing a named competitor.
Marketing action: Enroll in competitive differentiation campaign with specific messaging addressing your advantage in the dimensions buyers compare. Simultaneously suppress from generic awareness campaigns.
Why the suppression matters: An account in active evaluation does not need brand awareness content. Serving them the same top-of-funnel ads you serve cold accounts wastes budget and misreads their buying stage. Suppression ensures your spend targets the right message for the right stage.
According to the LinkedIn B2B Institute's research on targeting precision, B2B campaigns with tightly defined audience conditions consistently outperform broad-reach campaigns on pipeline influence metrics. Precision costs more per impression and generates fewer impressions. It generates more pipeline per dollar spent.
Building Signal-Level Attribution That Survives a CFO Conversation
Signal-based marketing creates an attribution problem. You replaced a single trackable event (form fill) with a distributed set of signals that influence pipeline without creating a visible conversion moment. The CFO will still ask: "What did marketing generate?" You need an answer that does not rely on last-touch MQL credit.
The answer is signal-level attribution: tracking which signals triggered which marketing actions, which accounts those actions touched, and how many of those accounts later created opportunities.
What Signal-Level Attribution Tracks
For every account that enters a signal-triggered marketing workflow, log four things in your CRM at the account level:
- Which signal fired the trigger (intent threshold, pricing page visit, etc.)
- Which workflow was activated (paid ICP audience, pricing retargeting, nurture trigger, hand-off alert)
- The date the account entered the workflow
- The specific trigger condition value (e.g., intent score: 74)
When an opportunity is created for that account, the signal data is already in the record. The attribution question becomes: was this account in a signal-triggered marketing program in the 90 days before opportunity creation?
This is influence attribution. It does not claim causation. It shows the pattern: accounts that were in signal-triggered marketing programs before an opportunity was created, across a cohort, convert at a different rate than accounts that were not. That pattern is what you present to the CFO.
The Three Metrics That Replace MQL Volume
Signal-touched accounts counts every ICP account that entered any signal-triggered marketing program during the period. This replaces MQL volume as the top-of-funnel demand indicator. It tells leadership how many qualified accounts the marketing system actively engaged.
Signal-to-opportunity rate measures what percentage of signal-touched accounts created an opportunity within 90 days of their first program entry. This replaces the MQL-to-SQL conversion rate and is a stronger quality indicator, because the baseline population (signal-touched accounts) is already filtered for ICP fit and demonstrated intent.
Signal-influenced pipeline totals the pipeline value from opportunities where the company record shows a signal program entry date that preceded the opportunity create date. This replaces marketing-attributed pipeline and is defensible because the time sequence is logged, not inferred.
How to Build This Reporting in HubSpot
Create two custom company properties: "Signal Program Entry Date" (date field, updated when an account enters any signal-triggered workflow) and "Signal Program Name" (text field, records the specific workflow name).
In deal reporting, filter for deals where the associated company has a "Signal Program Entry Date" populated and that date is earlier than the deal's "Create Date." Group those deals by signal program name. The result shows you which signal workflows are generating the most signal-influenced pipeline.
Export that as a cohort view: signal-touched accounts vs. non-signal-touched accounts, pipeline creation rate, average deal size. That is the CFO slide. Forrester's approach to B2B marketing contribution measurement recommends exactly this cohort-based influence model over last-touch or first-touch attribution, because it survives the "correlation vs. causation" question by presenting a pattern across a large enough cohort to be statistically meaningful.
For more on wiring this attribution model into your existing lead scoring infrastructure, the build process is at the lead scoring architecture post.
Signal-touched ICP accounts consistently convert to opportunities at a higher rate than accounts with no signal-triggered marketing contact.
Frequently Asked Questions
What is signal-based marketing?
Signal-based marketing is the practice of triggering marketing program actions from behavioral and contextual signals rather than from form fills or time-based schedules. When an ICP account visits your pricing page, that signal fires a paid retargeting action. When an account's intent score crosses a threshold, that signal fires a nurture sequence. The marketing system responds to evidence of buying behavior rather than waiting for a contact to self-identify.
How does signal-based marketing replace the MQL?
The MQL is replaced by a signal bundle: a defined combination of conditions (intent score threshold, specific page visits, ICP firmographic match, number of engaged contacts) that automatically triggers the same actions the MQL used to trigger. No human scores the lead. When the bundle conditions are all true, the hand-off fires and both a sales alert and a marketing program activation happen simultaneously. The difference from an MQL is that the trigger encodes buying context, not just a contact action.
What is signal-based demand gen?
Signal-based demand gen is a demand generation approach where every program trigger is a signal event rather than a calendar date or batch upload. Instead of sending a nurture email on a fixed 7-day schedule, signal-based demand gen sends it when a prospect returns to a high-intent page. Instead of uploading a static list to LinkedIn every month, it syncs audiences in real time based on which accounts have crossed a signal threshold. The underlying programs are similar; the trigger mechanism is different.
What buying signals should marketing teams actually track?
Marketing teams should focus on signals they can act on with marketing tools: high-intent page visits (pricing, case studies, competitor comparison pages), third-party intent scores from providers like Bombora or G2, lifecycle events (trial starts, feature activations, upgrade page visits), and email engagement patterns. Sales-side signals (job changes, funding rounds, outreach replies) belong in the sales motion. The full signal taxonomy and how to tier signals by urgency is covered in the signal-based GTM pillar post.
How does signal-triggered paid activation work in B2B?
Signal-triggered paid activation syncs CRM or intent data conditions to paid platform audiences in near-real time. An account that meets your ICP criteria and crosses a specific intent threshold automatically enters a LinkedIn Matched Audience running your consideration campaign. An account that visits your pricing page within the last 21 days automatically enters a retargeting audience with proof content. When those conditions no longer apply (opportunity created, signal drops off, time window expires), the account exits the audience. This concentrates your paid spend on accounts actively in a buying cycle rather than spreading it across your full TAM.
How do you report pipeline from signal-based marketing to a CFO who still asks about MQL volume?
Replace MQL volume with three metrics logged at the account level in your CRM: signal-touched accounts (ICP accounts in any signal-triggered program during the period), signal-to-opportunity rate (percentage of those accounts that created an opportunity within 90 days), and signal-influenced pipeline (total pipeline value from those opportunities). These three metrics answer the same questions the MQL metrics answered, but with a data model grounded in buying intent rather than form activity. Present the cohort view: signal-touched vs. non-signal-touched, opportunity creation rate comparison.
Does signal-based marketing require a large technology investment?
No. A functional signal-based marketing program starts with the behavioral tracking you likely already have (HubSpot contact activity, website analytics) and one intent data source (Bombora, G2, or a first-party intent proxy from your content engagement). The first signal workflow most teams build is signal-triggered nurture using HubSpot workflow branches. Paid audience syncing and advanced attribution are next. Full orchestration with Clay and dedicated signal routing infrastructure comes after you have proven that the signal-based approach converts better than the batch approach, which it will.
Start With One Workflow, Not the Whole System
Most teams that try to implement signal-based marketing in a single sprint end up with a half-built system that does not outperform what it was supposed to replace. The better approach is sequential.
Pick the highest-leverage workflow for your current situation. If your paid media spend is not generating pipeline, start with signal-triggered audience sync. If your nurture sequences have low engagement, start with signal-driven lifecycle triggers. If your sales team is ignoring MQL alerts, start with the signal-bundle hand-off threshold that encodes buying context in the alert.
Get one workflow generating measurable results before building the next. Signal-based marketing is not a platform migration. It is a change in how your existing programs fire, and each workflow change is independently valuable.
The four workflows covered here are the marketing-owned half of the system. The other half, covering signal types, tiering, and the technical infrastructure build in Clay, is in the signal-based GTM pillar post. Start with the workflow that fits your biggest current gap. Then build from there.
Not sure which gap to close first? The GTM Maturity Assessment maps your current signal stack against what a functioning signal-based marketing system looks like at your stage. Free, takes five minutes, and gives you a clear starting point.
Sources
- Forrester Research, "It's Time to Bury the MQL" (2023) — data on MQL-to-pipeline conversion rates and sales team MQL response behavior
- Gartner, "The B2B Buying Journey" (2024) — research on how much of the B2B purchase process happens independently of vendor interaction
- HubSpot, "The Best Time to Send Email" (2024) — research on email timing and engagement correlation with prospect activity patterns
- LinkedIn B2B Institute, "B2B Targeting Precision and Pipeline Impact" (2024) — research on how tightly defined audience conditions affect pipeline influence metrics
- Forrester Research, "B2B Marketing Attribution Best Practices" (2024) — methodology for cohort-based influence attribution vs. last-touch models