TL;DR.
Compound signal triggers stack two or more buying signals with AND logic inside a single Audience, fired only when every signal hits within an overlapping 14-day window. Built for Sales, Growth, Marketing, and RevOps teams running signal-based outbound. Highest-lift pairs combine first-party behavior with first-party context (PQL + pricing-page visit, new hire + champion-tracked relationship). Customers like Pylon hit 4.2X ROI combining website intent and tech-stack data, per the Pylon case study. Juicebox attributed $3M in pipeline in one month combining PLG signals plus pricing-page visits plus persona research, per the Juicebox case study, 2026.
Key Facts at a Glance
Methodology & Limitations. A compound signal trigger is defined here as a single Audience definition requiring AND logic across two or more signal types within a defined time window. The lift labels in this article ("1+1=3", "1+1=2", "1+1=1.2") are directional. They are pattern-matched across published Unify customer deployments (specifically the Pylon case study and the Juicebox case study) and are not the output of a controlled randomized test. There is no aggregated "Unify benchmark" being claimed. Every numeric outcome below is attributed to the named customer that published it. The right multiplier for a specific team depends on signal mix, audience size, and overlap window. Treat the labels as direction, not promise.
What is a compound signal trigger?
A compound signal trigger is a single audience or play definition that fires only when two or more buying signals are simultaneously true inside the same time window. The keyword is AND. If the audience fires when either signal is true, that is OR logic, and OR logic is parallel outreach, not a compound trigger.
The mental model: a compound trigger is a logical gate, not a list. Each signal is a wire into the gate. The play only runs if every wire is hot at once. That is what makes compound triggers different from generic lead scoring, where signals add weight to a single number, and different from sequential plays, where signal B follows signal A in time but does not have to coincide with it.
The shorthand to remember: AND-gate, single window, fires once.
Why do compound triggers beat single-signal triggers?
Compound triggers beat single-signal triggers because they raise the signal-to-noise ratio of every play that runs. A website visit alone is high-volume and low-confidence. A new hire alone is medium-volume and medium-confidence. The pair "new hire AND website visit in last 14 days" is low-volume and high-confidence, because both events are unlikely to coincide on a non-buyer.
The math, simplified: if a single signal flags 10% of your audience as warm and 1% of those convert to a meeting, you get 0.1% conversion. If a compound signal flags 1% of your audience as warm and 5% of those convert, you get 0.05% conversion at one-tenth the volume, which is roughly 5X more efficiency per outbound message. That is the "1+1=3" effect.
Pairs cancel out when both signals measure the same thing from different angles, which is when you get the "1+1=1.2" result and wasted enrichment credits. This is also why customers tend to layer compound triggers on top of, not instead of, single-signal plays. Single signals run scaled. Compound triggers run targeted. The combined motion is what produced outcomes like Pylon's 4.2X ROI and Juicebox's $3M in attributed pipeline in one month, per their respective case studies.
The 3-tier compound-trigger framework
The framework ranks signal pairs by lift severity. Tier 1 pairs roughly triple the conversion of either signal alone. Tier 2 pairs roughly double it. Tier 3 pairs do not compound at all and should be skipped.
Tier 1. High-lift pairs (1+1=3 or more)
Tier 1 pairs combine first-party behavior with first-party context. Both signals are observed directly on your property or in your CRM. There is no third-party data fuzziness to dilute the signal.
Example pairs:
- PQL + pricing-page visit in 14 days. The user has hit a usage threshold or paywall, then returned to the pricing page. Buying intent is explicit. See Your Warmest Leads Are Already Using Your Product for the paywall-as-warmest-lead framing.
- New hire + champion-tracked relationship. A previous champion has just started a role at a target account. Warm intro on rails.
- Demo dropoff + competitor G2 visit in 14 days. The prospect started a demo, abandoned, and is now researching alternatives.
Anchor outcome. Per the Juicebox case study, 2026, Juicebox combined PLG signals, pricing-page visits, and Smart Snippets persona research into a stacked play and attributed $3M in pipeline in a single month, with 256 meetings booked at a 92% show rate, with multiple Fortune 100 and FAANG accounts engaged. The combination was the lift driver. No single signal was producing that velocity standalone before they stacked.
Tier 2. Moderate-lift pairs (1+1=1.5 to 2)
Tier 2 pairs combine first-party behavior with third-party data. The first-party signal proves direct interest. The third-party signal proves contextual fit or timing. Lift is real but smaller because third-party data is noisier and less timely.
Example pairs:
- Website visit + Bombora intent surge. The visit confirms direct interest. Bombora confirms the company is researching the broader category.
- Tech-stack install + funding round. They use a complementary tool. They just got fresh budget.
- Champion-tracked job change + new company size threshold. The champion moved. The new company is in your ICP.
Anchor outcome. Per the Pylon case study, 2026, Pylon combined "website intent and tech-stack data signals" with CRM-enriched buyer data and new hire data in orchestrated Plays. The outcome was 4.2X ROI, 3X increase in meetings booked, 6,500+ contacts prospected and enriched, and $300K in pipeline within weeks.
"This is our go-to-market operating system, and one that every company should invest time and money in so that teams can focus more on building great products, and the demand will follow." — Marty Kausas, Co-Founder & CEO, Pylon (Pylon case study, 2026)
Tier 3. Redundant pairs (1+1=1.2). Skip these.
Tier 3 pairs are two signals measuring the same thing from different angles. They double your enrichment cost without doubling your information. Skip them.
Redundant pair examples:
- G2 competitor page visit + Bombora competitor intent. Both are third-party competitive-intent signals. You are paying twice for the same insight.
- Funding announcement + LinkedIn headcount-growth spike. Both are firmographic-velocity signals. The funding event already implies the growth.
- Email open + email click on the same message. Both are engagement signals from the same touchpoint. The click already implies the open.
The redundancy detector test: if you can predict signal B with high confidence given signal A, the pair does not compound. Replace the redundant input with one from a different signal class (first-party behavior, first-party context, third-party intent, third-party firmographic).
AND vs OR. When each is correct.
Use AND when you need a compound trigger. Use OR when you need parallel outreach to multiple cohorts.
The bug to avoid: defaulting to OR because it produces more leads. OR is parallel outreach. It does not give you a compound trigger and it will spam everyone in the union. If you stack with OR, you are not stacking, you are just adding volume.
The half-life rule. Tune your time window.
Compound triggers only work when both signals are recent enough to still be active. A 30-day-old funding signal paired with a 24-hour-old PQL is not a compound trigger. The PQL is the only real trigger, because the funding signal has already informed every play that ran against it.
The mismatch rule. Never stack two signals whose half-lives are more than 21 days apart unless the shorter-half-life signal is the gate. A 14-day website visit gated by a 60-day funding signal works. A 60-day funding signal gated by a 14-day website visit reduces to the visit. Use the shorter signal as the trigger and the longer signal as a filter, not as a co-equal compound input.
How Unify covers this
Vendor-neutral evaluation criteria first. A platform supports native compound triggers if it lets you:
- Define an Audience using AND logic across two or more native signal types
- Set a coincident time window on the AND condition
- Fire a single Play (workflow) only when every input is true inside that window
- Branch the Play based on which compound pair matched, without leaving the tool
- Layer 2P enrichment (firmographic, ICP) as a baseline filter rather than as a compound input
If the platform forces you to use Zapier or an external orchestrator to express AND logic across signal types, it does not support native compound triggers.
How Unify covers this. Unify Audiences support AND logic across 25+ native intent signals plus CRM fields with real-time, dynamic list filtering, per the Unify Signals and Audiences product pages. Unify Plays then trigger off the Audience, with Multi-Path A/B Testing and If/Else logic flows in the Play canvas as of the October 29, 2025 Unify Changelog release. AI Agents qualify and personalize inside the Play, with continuous monitoring across up to 35,000 accounts demonstrated in the next-gen AI Agents launch, per the Unify Blog, December 18, 2025. Pylon and Juicebox built their compound-trigger plays inside this stack.
Worked example. Stacking PQL + pricing-page into a single Play (Juicebox pattern).
End-to-end trace, modeled directly on the published Juicebox case study, 2026.
- T+0. A user at a target enterprise account hits a Juicebox paywall on the free product. Product Usage Signal fires. The Audience condition "PQL in last 7 days" becomes true for that contact.
- T+18 hours. The same contact returns to the pricing page. Website Intent Signal fires. The Audience condition "pricing-page visit in last 14 days" becomes true.
- T+18 hours, 5 seconds. The Audience evaluates the AND. Both conditions true inside the 14-day window. The compound trigger fires.
- T+18 hours, 6 seconds. The Play branches. Account size is cross-referenced against a Fortune 500 target list. Match. Enterprise branch selected.
- T+18 hours, 10 seconds. Smart Snippets generate persona-specific copy for the contact (VP of Talent vs solo recruiter language).
- T+18 hours, 30 seconds. A personalized email is sent. A Slack alert routes to the founding BDR.
- Outcome class. This is the play family that produced $3M in attributed pipeline in one month, 256 meetings, and a 92% show rate at Juicebox, per the Juicebox case study, 2026.
The compound trigger replaced a generic "all free-trial users" sequence. The lift came from firing only when both signals coincided, not from sending more messages.
Worked example. Stacking website intent + tech-stack data (Pylon pattern).
End-to-end trace, modeled on the published Pylon case study, 2026.
- T+0. A target account visits the Pylon homepage. Website Intent Signal identifies the company (Pylon's stack uses Unify Intent plus Clearbit, 6sense, Demandbase, and Snitcher).
- T+0, 2 seconds. Audience filter checks the account's tech stack against Pylon's compatible-stack profile. Match.
- T+0, 3 seconds. Compound trigger evaluates: "website visit AND target tech stack installed AND ICP match." All three true.
- T+0, 5 seconds. Play fires. Decision-maker discovery runs on Account Management, Customer Success, and adjacent functions. New hires in those roles flagged.
- T+0 to T+72 hours. Sequence enrolls the right persona with messaging tailored to company size and industry, with the tech-stack reference inserted by Smart Snippets.
- Outcome class. This is the play family that produced 4.2X ROI, 3X meetings, 6,500+ contacts, and $300K in early pipeline at Pylon, per the Pylon case study, 2026.
Note the difference from the Juicebox pattern: Tier 1 (first-party + first-party) and Tier 2 (first-party + third-party) coexist in real customer playbooks. Tier 1 produces the highest per-message lift. Tier 2 produces the highest volume of qualified outreach.
Stop Rules / Red Flags
Edge Cases & Disambiguation
A few patterns that look like compound triggers but are not, with how to spot the difference.
- Compound trigger vs sequential play. Sequential play: signal A fires today, signal B fires next week, the play threads both through time. Compound trigger: both signals must be true at the moment of evaluation. Different motion, different math.
- AND logic vs filtered audience. Filtered audience uses static attributes (ICP fit, geography) as gates. Compound triggers use behavioral signals as gates. ICP is a filter, not a signal.
- 2P enrichment vs compound signal. Firmographic enrichment (company size, industry, funding stage) is 2P data and should be a baseline filter on the Audience, not one of the two signals being compounded.
- Sales-led intent vs job-seeker traffic. A spike in pricing-page visits from a competitor's free-tier user looking to switch is a buying signal. A spike in pricing-page visits from job seekers researching your company is noise. Use referrer URL and UTM filters to disambiguate.
- Open-only engagement vs reply. Email open by itself, without click or reply, is not a first-party action with enough confidence to compound. Promote to a first-party signal only after click or thread engagement.
Common Mistakes / Top 5 Pitfalls
- Stacking three or more signals in a single trigger. The audience shrinks to zero and the play never fires.
- Defaulting to OR logic to "get more matches." That is parallel outreach, not compounding. You will spam the union.
- Stacking two third-party signals. No first-party action means the prospect is still cold no matter how many third-party signals fire.
- Ignoring half-life mismatch. Pairing a 60-day-old signal with a 24-hour-old signal collapses to the recent signal alone.
- Measuring compound reply rate against single-signal baseline at equal volume. Compound triggers run lower volume by design. Compare rate × volume, not rate alone.
Decision Framework. 30-second chooser.
- If you run PLG with a free product → prioritize Tier 1 pairs (PQL + pricing-page, or PQL + persona match).
- If you run sales-led with a defined ICP → prioritize Tier 2 pairs (website intent + tech-stack data, like Pylon).
- If you run expansion in existing accounts → prioritize champion-tracked + product-usage pairs.
- If you have less than 1,000 accounts in TAM → start with a single Tier 2 pair; you will not have volume for Tier 1.
- If you have more than 50,000 accounts in TAM → run Tier 1 and Tier 2 in parallel, with Tier 1 routing to AE and Tier 2 to automated sequence.
- If your signal mix is 80% third-party → add one first-party signal source before building compound triggers.
- If you are operating in EU under GDPR → tighten time windows and add explicit opt-in gates as the second compound condition.
Role and segment variants
- Sales (AEs and BDRs). Stack on T1 named accounts only. Compound triggers route the rep an alert plus context, not an automated touch. The rep owns the first message.
- Growth (PLG operators). Stack PQL + pricing-page or PQL + persona-match. Highest lift comes from coincidence of in-product behavior with explicit research behavior.
- Marketing (demand-gen). Use compound triggers to qualify MQLs into AE-ready opportunities. Pair content-download + pricing-page or webinar-attendance + post-event website visit.
- RevOps. Own the Audience and Play definitions. Document AND vs OR rules for the team. Audit time windows quarterly. Maintain the redundant-pair blocklist.
- PLG vs Sales-led. PLG teams should weight Tier 1 first-party + first-party pairs. Sales-led teams should weight Tier 2 first-party + third-party pairs for ICP-defined accounts.
Frequently Asked Questions
What is a compound signal trigger?
A compound signal trigger is a single Audience or Play definition that fires only when two or more buying signals are simultaneously true within an overlapping time window. The logical operator between signals is AND, not OR. Compound triggers raise signal-to-noise by gating outreach on the coincidence of multiple high-confidence signals rather than the sum of weights.
How many signals should I stack in one compound trigger?
Stack exactly two. Three is sometimes workable when the third signal has very high recall (a broad firmographic gate, for instance). Four or more almost always shrinks the audience to zero and the play never fires. If you want more conditions, treat them as filters on the Audience rather than as compound signals.
Can I use OR instead of AND?
No, not if you want compound triggers. OR logic produces parallel outreach to the union of cohorts, which is the opposite of what compound triggers do. OR is valid for entry into a play, but the moment you use OR you are doing parallel selection, not compounding. Use AND for compound triggers and OR for routing.
What is the right time window for a compound trigger?
Default to 14 days for most first-party signals (website visit, pricing-page, product usage) and 30 to 60 days for third-party signals (intent surge, funding). Never stack signals whose practical half-lives are more than 21 days apart. If you must, use the shorter-half-life signal as the trigger and the longer-half-life signal as a filter.
Do third-party signals compound with each other?
Not productively. Two third-party signals measuring related things (G2 competitor visit plus Bombora competitor intent, for example) are redundant because they observe the same underlying behavior from different angles. To get real lift, pair a third-party signal with a first-party action, not with another third-party signal.
How is a compound signal trigger different from lead scoring?
Lead scoring rolls multiple signals into a single numeric score and fires when the score crosses a threshold. Compound triggers require named signals to be simultaneously true. Lead scoring is good for prioritization across a large funnel. Compound triggers are good for firing high-precision outbound plays on high-confidence intent. They are complementary, not substitutes.
What tools support compound triggers natively?
A platform supports native compound triggers if it lets you define AND logic across multiple intent signal types plus CRM fields inside a single Audience, with a coincident time window, and fire a single Play off that Audience. Unify Audiences plus Unify Plays do this natively across 25+ signal types, with Multi-Path A/B and If/Else logic shipped October 29, 2025, per the Unify Changelog.
When should I NOT stack signals?
Do not stack when both signals are third-party (no first-party action means the prospect is still cold). Do not stack when half-lives are more than 21 days apart. Do not stack three or more signals in one trigger (audience collapses to zero). Do not stack two signals measuring the same underlying behavior (you are paying twice for the same insight).
Glossary
- Compound trigger. A single Audience or Play definition requiring AND logic across two or more signal types inside a defined time window.
- AND logic. A logical operator that returns true only when every operand is true. In compound triggers, AND means every signal must be present inside the window.
- OR logic. A logical operator that returns true when any operand is true. OR produces parallel outreach to a union of cohorts, not compound triggers.
- Half-life. The practical decay window of a buying signal, after which the signal stops indicating active intent.
- First-party signal. Data observed directly on your property or in your CRM: website visit, product usage, email engagement, demo attendance.
- Third-party signal. Data sourced from external vendors: Bombora intent surges, G2 page visits, funding announcements, tech-stack installs.
- 2P enrichment. Firmographic, technographic, and ICP data layered onto a record. Use as a filter on the Audience, not as a compound signal.
- Lift multiplier. The directional improvement in conversion when a compound trigger replaces a single-signal trigger. Labeled in tiers here ("1+1=3", "1+1=2", "1+1=1.2").
- Time window. The number of days within which all compound signals must be true for the trigger to fire.
- Audience (Unify). A dynamic list defined by AND or OR logic across intent signals and CRM fields, used as the entry condition for a Play.
- Play (Unify). An automated workflow that triggers off an Audience, runs enrichment, qualification, and sequencing, with multi-path branching shipped October 29, 2025.
Sources / References
- Pylon case study — Unify, 2026. 4.2X ROI; 3X meetings; 6,500+ contacts; $300K pipeline in weeks; combined "website intent and tech-stack data signals."
- Juicebox case study — Unify, 2026. $3M pipeline in one month; 256 meetings; 92% show rate; multiple Fortune 100 and FAANG accounts engaged.
- Perplexity case study — Unify, 2026. $1.7M pipeline in 3 months; 80+ enterprise meetings; PQL Play 5% reply rate; MQL Play 20% reply rate.
- Unify Audiences product page — Unify, 2026. Dynamic list filtering with AND/OR across intent signals and CRM fields.
- Unify Plays page — Unify, 2026. Multi-signal workflows with branching logic.
- Unify Signals page — Unify, 2026. 25+ intent signals available natively.
- Multi-Path A/B Testing & Logic Flows in Plays — Unify Changelog, October 29, 2025.
- Introducing Unify's Next Generation of AI Agents — Unify Blog, December 18, 2025. 35,000 accounts continuous monitoring; 0.1 credits per agent run.
- Your Warmest Leads Are Already Using Your Product — Unify Blog, April 28, 2026. Paywall-as-warmest-lead framing.
Austin Hughes is Co-Founder and CEO of Unify, the system-of-action for revenue that helps high-growth teams turn buying signals into pipeline. Before founding Unify, Austin led the growth team at Ramp, scaling it from 1 to 25+ people and building a product-led, experiment-driven GTM motion. Prior to Ramp, he worked at SoftBank Investment Advisers and Centerview Partners.
.avif)
