Profile & Identity Data forms the foundation of each client record in Catchlight. These fields help you identify individuals, contact them, and assess the reliability of the match between your CRM record and Catchlight's enriched data.
Core Identity Fields
Full Name
What it is: The client's complete legal name
Format: First Name, Middle Name/Initial, Last Name, Suffix
Source: Your CRM data, supplemented by public records and social media
Use cases:
Personalizing communications
Verifying correct person match
Formal correspondence
Limitations: May not reflect preferred names, nicknames, or recent name changes (marriage, legal changes)
Preferred Name / Nickname
What it is: Name the person commonly uses
Format: Text field
Source: Social media profiles, professional bios
Use cases:
Personal communications
Building rapport
Avoiding formality mismatch
Example: Legal name "Robert" may prefer "Rob" or "Bob"
Contact Type
What it is: Classification of the relationship
Possible values:
Client (active relationship)
Prospect (potential client)
Lead (early-stage opportunity)
Former Client
Referral Source
Center of Influence
Source: Your CRM categorization
Use cases:
Filtering and segmentation
Tailoring communication approach
Prioritizing outreach
Email Address
What it is: Primary email contact
Format: Standard email format ([email protected])
Source: Your CRM or public professional profiles
Use cases:
Direct communication
Marketing campaigns
Digital engagement tracking
Limitations: May be outdated if person changed jobs; personal vs. professional email distinction matters
Best practice: Verify before large campaigns; respect opt-out preferences
Phone Number
What it is: Primary contact number
Format: (XXX) XXX-XXXX
Source: Your CRM, public directories
Use cases:
Direct outreach
Appointment scheduling
Emergency contact
Limitations: Mobile vs. landline not always distinguished; may be outdated
Compliance note: Be aware of TCPA regulations for automated calls/texts
Mailing Address
What it is: Primary residence or mailing location
Format: Street Address, City, State, ZIP
Source: Your CRM, public records, property databases
Use cases:
Direct mail campaigns
Geographic segmentation
Service area verification
Considerations:
Address may be PO Box rather than physical residence
Seasonal residents may have multiple addresses
Recent movers may have outdated data
Catchlight System Identifiers
Catchlight ID
What it is: Unique internal identifier assigned by Catchlight
Format: Alphanumeric string (e.g., CTL-4829103-A)
Source: Generated by Catchlight system
Use cases:
Technical support inquiries
Data synchronization
Deduplication
API integrations
Note: This ID is permanent and doesn't change even if other data is updated
CRM ID / External ID
What it is: The unique identifier from your CRM or source system
Format: Varies by your system
Source: Your CRM upload
Use cases:
Cross-referencing between systems
Data synchronization
Import/export tracking
Maintaining linkage to your system of record
Best practice: Ensure these IDs are consistent across all data uploads to prevent duplicate records
Catchlight Date Added
What it is: When this record was first added to Catchlight
Format: MM/DD/YYYY
Source: System-generated timestamp
Use cases:
Tracking when enrichment began
Measuring time-to-contact
Campaign cohort analysis
Understanding data vintage
Last Updated Date
What it is: Most recent date any field in this record was updated
Format: MM/DD/YYYY HH:MM
Source: System-generated timestamp
Use cases:
Data freshness assessment
Triggering reviews when data changes
Identifying stale records
Data Quality Indicators
Match Confidence
What it is: Catchlight's confidence that enrichment data matches the correct individual
Possible values:
Excellent (95-100%): Very high confidence; multiple strong identifiers match
Good (85-94%): High confidence; most key identifiers match
Fair (70-84%): Moderate confidence; some identifiers match, may need verification
Needs Review (<70%): Low confidence; human verification recommended
How it's determined:
Exact matches on name + address + age
Professional profile alignment
Social media correlation
Public records consistency
Use cases:
Prioritizing data verification
Determining which fields to trust
Filtering for high-quality records only
Flagging records for manual review
Best practice:
For high-stakes outreach, verify Fair or lower matches
Use Excellent/Good matches confidently
Don't reference specific enrichment details for Needs Review records without verification
Example scenario:
Excellent Match: "John Smith" at 123 Main St, age 52, LinkedIn profile matches, same employer
Needs Review: "John Smith" (very common name), limited unique identifiers, multiple possible matches
Enrichment Status
What it is: Overall completion state of data enrichment for this record
Possible values:
Complete: Full enrichment process finished
Partial: Some data enriched, some pending
In Progress: Actively being enriched
Pending: Queued for enrichment
Failed: Unable to enrich (insufficient identifiers)
Not Started: Not yet processed
Source: Catchlight enrichment engine
Use cases:
Understanding data completeness
Managing expectations for data availability
Prioritizing re-enrichment
Troubleshooting missing data
See also: 5.10: Enrichment Status Values for detailed explanation
Data Coverage Score
What it is: Percentage of Catchlight fields that are populated for this record
Format: 0-100%
Source: Calculated from field completion
Use cases:
Assessing overall data richness
Comparing records for prioritization
Identifying candidates for manual research
Typical ranges:
80-100%: Very comprehensive profile
60-79%: Good coverage
40-59%: Moderate coverage
<40%: Limited coverage
Note: Some clients naturally have less public data available (private individuals, certain professions)
Using Identity Data Effectively
Verification Before Outreach
For important communications, verify:
Match Confidence is Good or Excellent
Contact information is recent (Last Updated Date)
Name and professional details align
Email/phone seem current (not outdated employer domain)
Managing Duplicates
Use Catchlight ID and CRM ID together to:
Prevent duplicate record creation
Merge records when necessary
Maintain clean data across systems
Privacy Considerations
Identity data requires careful handling:
Only use contact information for appropriate business purposes
Respect opt-out requests
Comply with CAN-SPAM, TCPA, and other regulations
Don't share or sell contact information
Data Accuracy Monitoring
Regularly review:
Records with low Match Confidence
Outdated Last Updated Dates (>12 months)
Contact info with bounce backs or disconnects
Name mismatches between systems
Common Scenarios
Scenario 1: Low Match Confidence You see a client record with 68% Match Confidence.
Action:
Review which fields are populated
Cross-check with LinkedIn or other known sources
Update your CRM with additional identifiers (address, email, employer)
Request re-enrichment with better data
Scenario 2: Multiple Records for Same Person You notice two Catchlight IDs that seem to be the same individual.
Action:
Compare CRM IDs to see if they're duplicates in your system first
Check Match Confidence and Data Coverage to determine which is more complete
Contact support to merge records if confirmed duplicate
Scenario 3: Outdated Contact Information Email bounces back from a high-value client.
Action:
Check Last Updated Date for email field
Look at Current Employer to see if they changed jobs
Check LinkedIn URL if available for updated contact info
Update your CRM and sync to Catchlight
Related Articles
5.10: Enrichment Status Values
8.2: Understanding Empty Data Fields
7.1: Data Accuracy and Limitations
3.2: Exploring Client Profiles
7.4: Combining Catchlight with CRM