Sales and strategy teams know which accounts to target, but outreach often fails because contacts are generic, duplicated, or unverifiable. Standard lead gen lists flood CRMs with noise, creating compliance risk and wasted effort.
This segment takes your company list, country scope, and target roles, resolves each firm via official registries, retrieves websites, and delivers one role-matched decision-maker contact per company with verified email, phone, appointment date, and compliance basis — defensible and ready for activation.
Ingest company list, countries, and target roles per function.
Resolve companies in registries and map decision-makers.
Enrich with websites, verify contacts, and package for CRM.
This segment is activated with a blend of trusted sources and your own inputs
AI reasoning
User Input
Curated APIs
Open Datasets
Web intelligence
One verified decision-maker per requested role and company
Registry ID, standardized company name, and official website included
Verified professional email and phone, with status and confidence scores
Appointment date and role tenure metadata
Legal basis tags for GDPR/CCPA-compliant outreach
Your questions on this segment, answered
Your questions on this segment, answered
What’s in the confidence score, and which thresholds do teams use?
It blends source QA (e.g., PDL’s testing/QA), validation statuses, registry match strength, and tenure recency. Most teams gate outreach at ≥ 80–85, send cautiously to accept-all/risky, and suppress invalid.
What does “one verified decision-maker per role” mean in practice?
For each company+role, we select the highest-confidence profile (email/phone status, registry consistency, recent appointment, seniority). You can cap max_contacts_per_role (default = 1) and we expose the rationale so Sales trusts the pick.
How fresh are contacts—do you track appointment dates and turnover?
Each contact includes an appointment/tenure field (when available). We refresh on a rolling cadence; if tenure is stale or confidence falls, the contact is flagged for re-verification or substitution before CRM sync.
Can you map titles to our internal role taxonomy (e.g., group CRO & VP Sales)?
Yes. Our LinkUp-powered role normalizer standardizes function and seniority (e.g., Sales • VP) and then maps to your taxonomy labels—so downstream routing (territories, sequences, SFDC roles) stays clean and explainable.
How do you resolve company inputs to the right entity and avoid duplicates?
We resolve your company_name/domain/country to an official registry identifier, then standardize canonical name and country. This registry-first approach prevents duplicates and gives legal-grade precision before contact selection. (Our enrichment providers document source vetting and false-linkage prevention.)
How do you verify emails and phones—and handle “accept-all/risky” addresses?
We combine provider-side QA (PDL’s testing framework rejects ~3 sources for every 1 used) with our own checks. Emails are classified (valid/accept-all/risky/invalid) and we apply send-rules for risky segments; phones are normalized/validated in E.164 format. Industry guidance is clear: accept-all domains can hurt deliverability, so we segment and throttle them.
How do you keep contact data compliant with GDPR/CCPA?
We work on an explicit legal basis (typically legitimate interest for B2B) and enrich only from vetted providers. Our pipeline audits source permissions and collection methods before ingestion, and we avoid sensitive categories. People Data Labs publicly documents compliance screening of sources and the categories it does not disclose (e.g., health, biometrics, minors), which we honor end-to-end.
{ "_meta": { "dictionaryColumns": ["Variable", "Data_Type", "Sample_Value", "Description"] }, "data": [ { "Variable": "company_name_input", "Description": "Client-provided target company name", "Business_Rules": "Raw input; used for matching", "Source_System": "Client Data", "Data_Type": "VARCHAR", "Sample_Value": "Acme Robotics" }, { "Variable": "company_domain_input", "Description": "Client-provided company website/domain", "Business_Rules": "Optional; improves match precision", "Source_System": "Client Data", "Data_Type": "VARCHAR", "Sample_Value": "acmerobotics.com" }, { "Variable": "iso_country_input", "Description": "Client-provided target country (ISO 3166-1 alpha-2)", "Business_Rules": "Must be valid ISO code", "Source_System": "Client Data", "Data_Type": "VARCHAR", "Sample_Value": "DE" }, { "Variable": "target_role_input", "Description": "Target decision-maker role", "Business_Rules": "Free text; standardized later", "Source_System": "Client Data", "Data_Type": "VARCHAR", "Sample_Value": "VP Marketing" }, { "Variable": "max_contacts_per_role_input", "Description": "Max contacts per role per company", "Business_Rules": "Integer >=1; default 1", "Source_System": "Client Data", "Data_Type": "INTEGER", "Sample_Value": "1" }, { "Variable": "registry_id", "Description": "Official company registry identifier", "Business_Rules": "Deterministic ID from registry", "Source_System": "Open Data", "Data_Type": "VARCHAR", "Sample_Value": "HRB123456" }, { "Variable": "company_name_canonical", "Description": "Standardized company name", "Business_Rules": "Registry-resolved", "Source_System": "Open Data", "Data_Type": "VARCHAR", "Sample_Value": "Acme Robotics GmbH" }, { "Variable": "company_country", "Description": "Standardized company country", "Business_Rules": "ISO alpha-2 code", "Source_System": "Open Data", "Data_Type": "VARCHAR", "Sample_Value": "DE" }, { "Variable": "company_website", "Description": "Official resolved company website", "Business_Rules": "Valid HTTPS URL; registry/domain matched", "Source_System": "Web Intelligence", "Data_Type": "VARCHAR", "Sample_Value": "https://www.acmerobotics.com" }, { "Variable": "contact_full_name", "Description": "Decision-maker full name", "Business_Rules": "Title case; UTF-8", "Source_System": "Curated APIs", "Data_Type": "VARCHAR", "Sample_Value": "Julia Neumann" }, { "Variable": "role_title", "Description": "Official job title", "Business_Rules": "Raw from source", "Source_System": "Curated APIs", "Data_Type": "VARCHAR", "Sample_Value": "VP Marketing" }, { "Variable": "role_function", "Description": "Standardized function category", "Business_Rules": "ENUM: Marketing, Sales, Operations, Finance, HR, Product, Engineering, IT, Supply Chain, Legal, Executive, Other", "Source_System": "Web+AI Reasoning", "Data_Type": "ENUM", "Sample_Value": "Marketing" }, { "Variable": "role_seniority", "Description": "Standardized seniority level", "Business_Rules": "ENUM: C-Level, VP, Director, Manager, Lead, IC, Other", "Source_System": "Web+AI Reasoning", "Data_Type": "ENUM", "Sample_Value": "VP" }, { "Variable": "person_linkedin_url", "Description": "LinkedIn profile URL", "Business_Rules": "Valid HTTPS URL", "Source_System": "Curated APIs", "Data_Type": "VARCHAR", "Sample_Value": "https://www.linkedin.com/in/julianeumann" }, { "Variable": "email", "Description": "Professional email address", "Business_Rules": "RFC 5322; business domains preferred", "Source_System": "Curated APIs", "Data_Type": "VARCHAR", "Sample_Value": "j.neumann@acmerobotics.com" }, { "Variable": "email_status", "Description": "Email verification result", "Business_Rules": "ENUM: valid, accept_all, risky, invalid, unknown", "Source_System": "Curated APIs", "Data_Type": "ENUM", "Sample_Value": "valid" }, { "Variable": "phone_e164", "Description": "Phone number in E.164 format", "Business_Rules": "Starts with +; digits only", "Source_System": "Curated APIs", "Data_Type": "VARCHAR", "Sample_Value": "+49301234567" }, { "Variable": "phone_status", "Description": "Phone verification result", "Business_Rules": "ENUM: verified, unverified, unknown", "Source_System": "Curated APIs", "Data_Type": "ENUM", "Sample_Value": "verified" }, { "Variable": "appointment_date", "Description": "Date decision-maker assumed current role", "Business_Rules": "YYYY-MM-DD; may be null", "Source_System": "Web Intelligence", "Data_Type": "DATE", "Sample_Value": "2023-04-15" }, { "Variable": "legal_basis", "Description": "Legal basis for outreach under GDPR/CCPA", "Business_Rules": "ENUM: legitimate_interest, consent, contractual_necessity, other", "Source_System": "Client Data", "Data_Type": "ENUM", "Sample_Value": "legitimate_interest" }, { "Variable": "confidence_contact", "Description": "Overall confidence score for contact", "Business_Rules": "0-100", "Source_System": "Web+AI Reasoning", "Data_Type": "INTEGER", "Sample_Value": "92" } ] }
