Twitter Posts
A contact's posts and engagement on Twitter/X.
Overview
Contact Twitter Posts capture what individual prospects are saying on Twitter/X—their opinions, industry perspectives, and personal interests.
We match Twitter handles to 4M+ contacts via LinkedIn profile links and email/name matching, then pull recent tweets with engagement data. Each post is tagged with topics from our ~300-category taxonomy. Signals include full tweet text, engagement metrics, and Twitter profile metadata so you can reference both what they said and their public persona.
Subtype
| Signal | Subtype Enum | Description |
|---|---|---|
| Posted on Twitter | postedOnTwitter | Contact's recent posts on Twitter/X |
Schema
{
"signal_id": "d5b12c47-ce39-4da4-b25e-abcdb9981cee",
"signal_type": "twitter-post-contact",
"association": "contact",
"contact": {
"linkedin_url": "http://www.linkedin.com/in/gordon-bowman",
"first_name": "Gordon",
"last_name": "Bowman",
"full_name": "Gordon Bowman",
"email": "[email protected]",
"job_title": "VP of Partnerships & Business Development",
"twitter_url": "https://x.com/gordonbowman",
"twitter_handle": "gordonbowman"
},
"company": {
"name": "Lendflow",
"domain": "lendflow.com"
},
"content": {
"post_text": "The future of embedded finance is partnerships. Here's why...",
"post_url": "https://twitter.com/gordonbowman/status/624402473059422208",
"posted_date": "Fri Jul 24 02:15:25 +0000 2015",
"likes": 12,
"retweets": 3,
"replies": 2,
"views": 1500,
"tags": [
"Corporate Strategy",
"Business Finance",
"Financial Strategy"
]
},
"twitter_user": {
"name": "Gordon Bowman",
"bio": "Momentum/Growth/Angel Investor. Previously @LiftoffMobile, @Twitter, TapCommerce, @PandoraMusic.",
"followers": 1605,
"following": 1891,
"verified": false
}
}Field Reference
Core Fields
| Field | Type | Description |
|---|---|---|
signal_id | string (UUID) | Unique identifier for this signal |
signal_type | string | Always "twitter-post-contact" |
association | string | Always "contact" |
Contact Object
| Field | Type | Description |
|---|---|---|
contact.linkedin_url | string | Contact LinkedIn URL |
contact.first_name | string | Contact first name |
contact.last_name | string | Contact last name |
contact.full_name | string | Contact full name |
contact.email | string | Contact email address |
contact.job_title | string | Contact job title |
contact.twitter_url | string | Contact Twitter/X profile URL |
contact.twitter_handle | string | Twitter handle (without @) |
Company Object
| Field | Type | Description |
|---|---|---|
company.name | string | Company name |
company.domain | string | Company website domain |
Content Object
| Field | Type | Description |
|---|---|---|
content.post_text | string | Full text of the tweet |
content.post_url | string | URL to the tweet |
content.posted_date | string | When the tweet was posted |
content.likes | integer | Number of likes |
content.retweets | integer | Number of retweets |
content.replies | integer | Number of replies |
content.views | integer (nullable) | Number of views |
content.tags | array[string] | LLM-generated topic tags |
Twitter User Object
| Field | Type | Description |
|---|---|---|
twitter_user.name | string | Display name on Twitter |
twitter_user.bio | string | Twitter bio |
twitter_user.followers | integer | Follower count |
twitter_user.following | integer | Following count |
twitter_user.verified | boolean | Verified status |
Example Output
"Gordon - saw your tweet about embedded finance partnerships. With your background at Twitter and Liftoff, you've seen how platform plays scale. We're helping fintech BD teams like yours automate partnership outreach. Would love to share what's working."
Related Insights
For company-level Twitter activity, see Company Twitter Posts.
Identity Resolution
Every contact Twitter/X signal is pre-resolved to a business contact record with a work email. Here's how:
- Twitter handle identified from post activity
- Cross-referenced against LinkedIn profiles that list a Twitter handle
- Full name + job title + current company matched against Twitter profile bio, location, and post content
- LLM-assisted models evaluate linkage probability across all available signals
- Only matches exceeding strict confidence thresholds are accepted — we prefer no match over a false match
- Business email and company resolved from the matched contact record in our database (250M+ contacts, 75M+ companies)
Key Points
- Business emails only. The
contact.emailfield is a professional/work email. Our domain validation excludes generic providers (gmail.com, yahoo.com, etc.). We do not resolve to personal emails. - Match accuracy: 99.8%. Resolution uses full name + title + company, validated against profile bio, location, and content. We never match on name alone.
- Full resolution chain exposed. Each signal includes
contact.email,contact.linkedin_url,contact.twitter_url, andcontact.twitter_handle— so you can see exactly how the identity was resolved. - De-duplication: LinkedIn URLs serve as deterministic secondary keys, eliminating same-name collisions. LLM-assisted verification handles ambiguous cases.
Full matching guide with SQL examples: Resolution
Coverage
- Refresh: Weekly
- Coverage: 10-25% of contacts
- Best for: Social selling, thought leadership outreach, executive engagement
Updated 3 days ago
