INTEL_PROTOCOL_03 // PROTOCOL_SPEC
Suppression + Exclusion Schema
Rules that stop spend leakage (customers, job seekers, vendors, non-ICP) and protect narrative integrity by removing the wrong eyeballs from paid exposure.
Spend Leakage Is Silent
Most organizations only discover leakage when Sales complains—or when Finance asks why media spend grew without revenue lift. This protocol creates an enforceable shield.
CRITICAL FAILURE MODES
- ✕ Customer accounts consume prospect budget
- ✕ Recruiting traffic pollutes intent signals
- ✕ Partners/vendors inflate engagement metrics
Suppression Logic
SUPPRESSION SOURCES
Customer Lists
Open Opportunities
Partner/Vendor Domains
Recruiting/Jobs Traffic
→
FILTERED ACTIVATION
Prospect-Only Cohorts
Logic: [Exclude] customers + vendors + job seekers + out-of-ICP
PLATFORM ON (DSP Suppression)
We enforce suppression at the audience export layer and validate that exclusions persist across refreshes and lookalike expansions.
Rule: If AccountStatus = Customer → Suppress in all prospect audiences
PLATFORM OFF (Operational Suppression)
We maintain suppression lists in CRM and ensure every exported manifest includes enforced exclusions with QA checks.
Checklist: customer suppression applied → verified in platform match report
Artifacts You Receive
- ✓Suppression Field Rules + Source-of-Truth
- ✓Vendor/Partner Exclusion List
- ✓Recruiting/Job Seeker Filtering Logic
- ✓Activation QA Checklist (leak prevention)
Implementation Steps
WK 1
Inventory leakage sources (customers, vendors, recruiting, non-ICP).
WK 2
Implement suppression rules in source systems and export layer.
WK 3
Validate enforcement, automate refresh cadence, and audit leakage monthly.