Skip to main content
Autobound logo

Social Intelligence

Twitter/X Post Signals

Published Updated

What individual prospects say on Twitter/X, resolved to business contacts and analyzed by AI. Every tweet ships with engagement metrics (likes, reposts, views), account metadata, and extracted pain points, initiatives, technologies, and competitors across 4M+ monitored contacts.

Read the API docs
Contacts Monitored
4M+
Signal Subtypes
1
Tag Taxonomy
~300 categories
Delivery
REST API, GCS Push, Generate Insights API, Flat File
Format
JSONL or Parquet
Bucket
gs://autobound-twitter-contact-posts-v2/

What Are Twitter/X Post Signals?

Monthly refresh

Twitter/X post signals capture what individual prospects say on Twitter/X: opinions, challenges, tool complaints, and industry takes. Autobound collects recent posts from the Twitter/X handles on file for each contact, then analyzes each tweet with AI to extract topic tags from a 300+ category taxonomy, a 10-15 word summary, pain points with intensity scores, initiatives with urgency scores, technologies mentioned with adoption status, and competitors referenced.

Each signal includes full engagement data (likes, reposts, replies, views, bookmarks, quotes) plus account context: bio, follower count, location, and verification status. Twitter/X is less polished than LinkedIn, so candid pain points and tool evaluations often surface here first. Coverage spans 4M+ monitored contacts, refreshed monthly.

Example record

X posttwitter_post

Illustrative example

Loop Returnsloopreturns.com

VP of Engineering says observability costs now exceed compute spend after Kubernetes migration.

Source: loopreturns.com

From a post on X to your next move

What we detect, what you get, and what you do with it. Pick the path that fits your team.

Sales, marketing and RevOps: Slack, CRM fields and plays.

  1. 0103

    Prospects speak their mind on X

    We match X accounts to business contacts and read each post for pain points, tools and competitors.

    1. X (Twitter)
    X (Twitter)Jun 13, 2026

    Six months into our Kubernetes migration and the observability bill is now bigger than the compute bill. Something is deeply wrong with how this industry prices monitoring.

    Extracted
    Loop Returnsloopreturns.comcompanyMarcus WebbcontactX postsignal_subtype

  2. 0203

    You get one clean record

    Each record names the person, their title and company, labels the event, and links back to the source.

    2. Signal record

    Loop Returns

    loopreturns.comSoftware Development

    Marcus WebbVP of Engineering

    X posttwitter_post

    VP of Engineering says observability costs now exceed compute spend after Kubernetes migration.

    “Six months into our Kubernetes migration and the observability bill is now bigger than the compute bill. Something is deeply wrong with how this industry prices monitoring.”
    Views
    48,210
    Likes
    412
    Detected
    Jun 13, 2026

    signal_id dbc467e8…

  3. 0303

    Act on it where you work

    Send it to Slack, write it to your CRM, or give it to an AI agent.

    When
    An exec posts a pain in pain_points that you solve
    Do
    Public reply, then an email the same day
    3. Your team acts
    or your own code
    #account-signals

    Signal alert from your workflow

    Marcus Webb, Loop Returns· X post

    VP of Engineering says observability costs now exceed compute spend after Kubernetes migration.

    Play: Public reply, then an email the same day

    Start the playOpen the source

    Illustration. The record fields are real.

Try it on your own accounts

1,000 free credits. Query social_media in the Signal API or from Claude.

Get a free API keyUse it in Claude via MCP

How we build this signal

How we build each X post signal

Each run reads every new post from each monitored person and turns it into a structured signal.

  1. 01

    Collection

    For each person on our list with a known X handle, we pull their newest posts published inside the run window. The author's contact and company records travel with the post.

  2. 02

    Analysis

    A model reads each post with the person's title, bio and company as context and fills a fixed schema: summary, pain points, initiatives, technologies and competitors. Off-topic posts get empty lists, not guesses.

  3. 03

    Tags

    A second, separate request picks up to 5 topic tags from a fixed list of business categories.

  4. 04

    Batch gate and delivery

    If any model batch in a run fails, the run stops instead of shipping a partial set. Records are keyed on handle and post ID, so a shipped post is never delivered again.

Twitter/X Post Signal Schema

Twitter/X signals include full tweet text, LLM-generated topic tags, engagement metrics with view counts, and verified account metadata.

Full schema docs →
{
  "signal_id": "dbc467e8-84b3-4763-972a-deb88e75112a",
  "signal_type": "social_media",
  "signal_subtype": "twitter_post",
  "signal_name": "Twitter Post",
  "association": "contact",
  "detected_at": "2026-06-13T16:31:43.993Z",
  "contact": {
    "name": "Marcus Webb",
    "job_title": "VP of Engineering"
  },
  "company": {
    "name": "Loop Returns",
    "domain": "loopreturns.com",
    "description": "Returns management platform for ecommerce brands",
    "industries": ["Software Development"]
  },
  "data": {
    "post_url": "https://x.com/marcuswebb_dev/status/2061702360843788335",
    "post_text": "Six months into our Kubernetes migration and the observability bill is now bigger than the compute bill. Something is deeply wrong with how this industry prices monitoring.",
    "posted_date": "Thu Jun 11 15:05:23 +0000 2026",
    "tweet_id": "2061702360843788335",
    "num_likes": 412,
    "num_reposts": 58,
    "num_replies": 63,
    "num_views": 48210,
    "num_bookmarks": 91,
    "num_quotes": 12,
    "is_reply": false,
    "replied_to_username": null,
    "posting_source": "Twitter Web App",
    "language": "en",
    "hashtags": [],
    "urls": [],
    "mentions": [],
    "contact_twitter_url": "https://x.com/marcuswebb_dev",
    "contact_twitter_handle": "marcuswebb_dev",
    "contact_twitter_bio": "VP Eng @ Loop Returns. Infra, on-call, and opinions.",
    "contact_twitter_followers": 8214,
    "contact_twitter_following": 903,
    "contact_twitter_location": "Columbus, OH",
    "contact_twitter_verified": true,
    "contact_twitter_verification_type": "blue",
    "contact_twitter_account_created": "Tue Aug 11 14:52:44 +0000 2015",
    "contact_twitter_total_tweets": 11406,
    "contact_twitter_dm_open": true,
    "tags": ["Infrastructure", "DevOps", "Spending/Investment"],
    "summary": "VP of Engineering says observability costs now exceed compute spend after Kubernetes migration.",
    "pain_points": [
      { "topic": "observability costs exceeding compute spend", "intensity": 0.8 }
    ],
    "initiatives": [
      { "topic": "completing Kubernetes migration", "urgency": 0.7 }
    ],
    "technologies_mentioned": [
      { "name": "Kubernetes", "status": "migrating_to" }
    ],
    "competitors_mentioned": []
  }
}

Bulk data

Need this signal for 10,000+ companies?

Get a free sample file or a bulk feed (API, GCS push, flat file). The sample is real Twitter Contact Posts records, as a CSV.

Talk to sales

Measured coverage

What's inside Twitter/X Post Signals

A dated snapshot counted in our production database, not a live count. Minimums, not ceilings.

Coverage for all 35 signal types →
172,607
Contacts with fresh data per month
Last 30 days, records through Jul 14, 2026
1,343,094
Records created per month
Last 30 days, records through Jul 14, 2026

Top subtypes

1 total
Twitter post2.8M · 100%

Seniority

full breakdown →
Staff99K · 44%
C-Suite47K · 21%
Manager26K · 11%
Director16K · 7.0%
VP13K · 5.7%
Consultant2.1K · 0.9%

Departments

full breakdown →
Business Management50K · 22%
Technology, Software, Information Technology17K · 7.4%
Education12K · 5.3%
Sales10K · 4.5%
Creative, Design8.1K · 3.6%
Marketing7.5K · 3.3%
Operations7.5K · 3.3%

Join keys

fill rate
Contact LinkedIn93%
Contact name100%
Email59%
Records measured 2,770,266+Contacts reached 226,232+

See for yourself

Check out sample data: real Twitter/X Post records with the same fields the API returns.

Read the API docs
“Autobound's API streamlined our data management, accelerated product development, and improved outreach quality.”
AiSDR Team, Engineering Team, AiSDR

Frequently asked questions

What are Twitter/X post signals?
Twitter/X post signals track what individual contacts post on Twitter/X, with AI-extracted topic tags, pain points, initiatives, technologies, competitors, and engagement metrics. Autobound monitors 4M+ contacts and refreshes the data monthly. For posts from company accounts, see Twitter/X company posts.
How does Autobound detect Twitter/X post signals?
Autobound collects recent posts from the Twitter/X handles on file for each contact and analyzes each post with AI. Each signal includes the full post text, a link to the post, engagement counts, account details, and the extracted tags, pain points, initiatives, and technologies.
How should I use Twitter/X data in my outreach?
Use Twitter/X signals to learn what a prospect cares about, then open with that problem. Refer to the topic rather than quoting the post back. Keep the tone short and direct, and focus on posts where the prospect describes a real problem or a tool decision.