Excluded internal domain list for clean customer views
Block your own company domain and other throwaway domains from auto-creating customer records so request views stay about buyers instead of your team.
Why this can grow a startup
Customer evidence gets noisy fast when internal testing and staff requests masquerade as real accounts. An exclusion list keeps the request graph honest. That matters for roadmap calls, reporting, and anything public-facing because the company can trust that counts and account views reflect actual customers rather than internal traffic.
Company example
Linear excludes its own domain from Customer Requests so internal issue creation does not generate fake customer records, and also supports broader excluded-domain rules.
Source and metric
Source: Linear Docs · Browse Linear Docs tactics
Excluded domains prevent internal requests from creating customer records
Source discovered: May 27, 2026
When to use it
Use this when Product, Support, Analytics is relevant to data hygiene, customer evidence, b2b and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Linear Docs and identify what is directly supported.
- Choose one channel context: Product, Support, Analytics.
- Define the test around Excluded domains prevent internal requests from creating customer records.
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.