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

SignalSubtype EnumDescription
Posted on TwitterpostedOnTwitterContact'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

FieldTypeDescription
signal_idstring (UUID)Unique identifier for this signal
signal_typestringAlways "twitter-post-contact"
associationstringAlways "contact"

Contact Object

FieldTypeDescription
contact.linkedin_urlstringContact LinkedIn URL
contact.first_namestringContact first name
contact.last_namestringContact last name
contact.full_namestringContact full name
contact.emailstringContact email address
contact.job_titlestringContact job title
contact.twitter_urlstringContact Twitter/X profile URL
contact.twitter_handlestringTwitter handle (without @)

Company Object

FieldTypeDescription
company.namestringCompany name
company.domainstringCompany website domain

Content Object

FieldTypeDescription
content.post_textstringFull text of the tweet
content.post_urlstringURL to the tweet
content.posted_datestringWhen the tweet was posted
content.likesintegerNumber of likes
content.retweetsintegerNumber of retweets
content.repliesintegerNumber of replies
content.viewsinteger (nullable)Number of views
content.tagsarray[string]LLM-generated topic tags

Twitter User Object

FieldTypeDescription
twitter_user.namestringDisplay name on Twitter
twitter_user.biostringTwitter bio
twitter_user.followersintegerFollower count
twitter_user.followingintegerFollowing count
twitter_user.verifiedbooleanVerified 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:

  1. Twitter handle identified from post activity
  2. Cross-referenced against LinkedIn profiles that list a Twitter handle
  3. Full name + job title + current company matched against Twitter profile bio, location, and post content
  4. LLM-assisted models evaluate linkage probability across all available signals
  5. Only matches exceeding strict confidence thresholds are accepted — we prefer no match over a false match
  6. Business email and company resolved from the matched contact record in our database (250M+ contacts, 75M+ companies)

Key Points

  • Business emails only. The contact.email field 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, and contact.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