Twitter (X.com) User Extractor (Rich Metadata) cookieless

"# Twitter (X.com) User Extractor (Rich Metadata) cookieless

Overview

This actor performs a deep extraction of Twitter (X.com) user profile metadata by username, delivering comprehensive account information including verification status, engagement metrics, location data, and security indicators. The extraction operates without cookie dependencies, ensuring reliable data retrieval with high fidelity and structural consistency. All timestamps are returned in ISO 8601 format (UTC), and nested objects maintain strict schema adherence for downstream analytical processing.

Data Dictionary

Field Name	Data Type	Definition
user_id	String	Internal unique identifier assigned to the user profile
username	String	Twitter handle (without @ symbol) used for account identification
external_id	String	Platform-native user identifier from Twitter's internal system
scraped_at	String (ISO 8601)	UTC timestamp indicating when the data extraction occurred
account_created	String (ISO 8601)	UTC timestamp of the original account creation date
is_verified	Boolean	Indicates whether the account has official verification status (blue checkmark)
is_active	Boolean	Indicates whether the account is currently active and not suspended
language_code	String	ISO language code representing the user's primary interface language
reputation_score	Float	Calculated metric (0.0-5.0) representing account trustworthiness and engagement quality
last_seen	String (ISO 8601)	UTC timestamp of the most recent account activity detected
profile_stats.followers	Integer	Total count of accounts following this user
profile_stats.following	Integer	Total count of accounts this user follows
profile_stats.total_posts	Integer	Cumulative number of tweets posted by the user
profile_stats.avg_engagement_rate	Float	Average engagement rate (%) calculated across recent posts
location.city	String	User-declared or inferred city of residence
location.country	String	ISO 3166-1 alpha-2 country code
location.timezone	String	IANA timezone identifier for the user's location
location.coordinates.latitude	Float	Geographic latitude coordinate
location.coordinates.longitude	Float	Geographic longitude coordinate
security.two_factor_enabled	Boolean	Indicates whether two-factor authentication is active on the account
security.last_password_change	String (ISO 8601)	UTC timestamp of the most recent password modification
security.login_attempts	Integer	Number of failed login attempts detected in recent period
security.security_score	Float	Normalized security posture score (0.0-1.0) based on authentication practices
account_type	String	Account tier classification (e.g., ""premium"", ""basic"", ""business"")
email_hash	String	One-way cryptographic hash of the associated email address
sentiment_score	Float	Aggregate sentiment score (-1.0 to 1.0) derived from recent tweet content analysis

Sample Dataset

Below is a sample of the high-fidelity JSON output:

{
  ""user_id"": ""u_789456123"",
  ""username"": ""tech_explorer"",
  ""external_id"": ""usr_7894561230123456789"",
  ""scraped_at"": ""2025-12-21T12:00:00Z"",
  ""account_created"": ""2020-03-15T08:22:31Z"",
  ""is_verified"": true,
  ""is_active"": true,
  ""language_code"": ""en_US"",
  ""reputation_score"": 4.8,
  ""last_seen"": ""2025-12-20T23:15:42Z"",
  ""profile_stats"": {
    ""followers"": 12456,
    ""following"": 891,
    ""total_posts"": 567,
    ""avg_engagement_rate"": 3.2
  },
  ""location"": {
    ""city"": ""San Francisco"",
    ""country"": ""US"",
    ""timezone"": ""America/Los_Angeles"",
    ""coordinates"": {
      ""latitude"": 37.7749,
      ""longitude"": -122.4194
    }
  },
  ""security"": {
    ""two_factor_enabled"": true,
    ""last_password_change"": ""2025-11-30T14:22:10Z"",
    ""login_attempts"": 1,
    ""security_score"": 0.95
  },
  ""account_type"": ""premium"",
  ""email_hash"": ""d4c3b2a1e5f6g7h8i9j0"",
  ""sentiment_score"": 0.75
}

Configuration Parameters

To ensure optimal data depth, configure the following:

Parameter	JSON Field Name	Data Type	Required	Description	Example Value
Username	username	String	Yes	Twitter handle to extract (without @ symbol)	""elonmusk""

Analytical Use Cases

Lead Enrichment & Qualification: Sales intelligence teams can augment CRM records with follower counts, verification status, and engagement metrics to prioritize high-value prospects and tailor outreach messaging based on account tier and activity patterns.

Sentiment Analysis: Data scientists can leverage the sentiment_score field alongside profile_stats to correlate user sentiment with engagement behaviors, identifying brand advocates or detractors for targeted marketing campaigns.

Network Mapping & Influence Analysis: Researchers can construct social graphs using followers and following counts combined with reputation_score to identify key opinion leaders and information diffusion pathways within specific communities.

Temporal Behavior Studies: Longitudinal analysis of last_seen, account_created, and total_posts enables cohort analysis and user lifecycle modeling to understand platform engagement evolution over time.

Geographic Market Segmentation: Location data (city, country, coordinates) facilitates regional market analysis and geo-targeted campaign planning for sales and marketing operations.

Security Posture Assessment: Enterprise security teams can evaluate security_score and two_factor_enabled metrics to assess risk profiles when vetting potential business partners or monitoring brand impersonation threats.

Technical Limitations

Important Considerations:

• Rate Limiting: Extraction throughput is subject to platform-imposed rate limits; batch processing of large username lists may require throttling to maintain data integrity.
• Data Freshness: The scraped_at timestamp reflects extraction time; rapidly changing metrics (e.g., followers, last_seen) may exhibit minor staleness depending on extraction frequency.
• Location Accuracy: Geographic coordinates are derived from user-declared location strings and may not reflect precise physical locations; accuracy varies based on profile completeness.
• Suspended Accounts: Profiles with is_active: false return limited metadata; certain fields (e.g., profile_stats, last_seen) may be null or stale.
• Privacy-Protected Accounts: Private/protected accounts return only publicly visible metadata; follower counts and engagement metrics may be unavailable.
• Sentiment Score Methodology: The sentiment_score is calculated from recent tweet content (typically last 100 tweets) and may not represent long-term account sentiment trends.
• Email Hash Availability: The email_hash field is populated only when email information is publicly exposed or inferrable; null values are common.

---

Keywords & Tags: This specification supports username scraper, get user by username, profile scraper tool, export user profiles, social media username lookup, lead generation scraper, and profile data extraction workflows for sales intelligence and data enrichment operations."