Twitter/X Posts (Company)
Company Twitter Posts capture what organizations are publicly communicating on X (formerly Twitter) — product announcements, strategic shifts, integrations, and market positioning in real time.
We monitor company Twitter/X accounts across hundreds of thousands of organizations, matching handles via domain lookup and LinkedIn cross-referencing. The same monitoring infrastructure powers social products at multiple billion-dollar enterprise platforms. Each tweet is analyzed to extract initiatives, pain points, technologies mentioned, and competitors referenced. Twitter’s brevity and real-time nature make it ideal for catching announcements as they happen — often before they reach a company’s blog or press page.
The result: you can reference a company's latest announcement in outreach within hours, identify strategic direction from product tweets, and spot competitive positioning in real time.
See real delivered data → Sample Files
Filter by topic — This signal uses Tags Taxonomy (300+ values) rather than subtypes for topic-based filtering. Use tags alongside pain_points, initiatives, and technologies_mentioned for targeting and routing.
Example Signal
What a single entry looks like in a delivered signal file:
{
"signal_id": "c8e27d14-6b3a-4f92-8d1e-47a9c5f10b83",
"batch_id": "2026-03-15-00-00-00",
"signal_type": "twitter-company-posts",
"signal_subtype": "companyTweet",
"detected_at": "2026-03-14T21:15:09.442Z",
"association": "company",
"company": {
"name": "Notion",
"domain": "notion.so", // match on domain
"linkedin_url": "linkedin.com/company/notionhq", // or match on LinkedIn URL
"industries": ["Software Development"],
"employee_count_low": 501,
"employee_count_high": 1000,
"description": "Connected workspace for notes, docs, and projects..."
},
"contact": [],
"data": {
"summary": "Notion announces native Salesforce integration and enterprise API, signaling push into revenue team workflows...",
"post_text": "Your CRM shouldn't live in a silo. Today we're launching native Salesforce integration + a new Enterprise API for custom workflows. Pipeline reviews, deal rooms, handoff docs - all connected...",
"post_url": "https://x.com/NotionHQ/status/1901234567890123456",
"posted_date": "2026-03-14",
"tweet_id": "1901234567890123456",
"posting_source": "Sprout Social",
"language": "en",
"is_reply": false,
"num_likes": 4892,
"num_reposts": 1247,
"num_replies": 312,
"num_quotes": 89,
"num_bookmarks": 2103,
"num_views": 847000,
"hashtags": ["#NotionEnterprise", "#SalesOps"],
"mentions": ["@salesforce"],
"urls": ["https://notion.so/enterprise-api"],
"tags": ["CRM integration", "enterprise API", "revenue workflows"],
"pain_points": [
{ "topic": "CRM data silos across tools", "intensity": 0.72 },
{ "topic": "disconnected deal documentation", "intensity": 0.65 }
],
"initiatives": [
{ "topic": "native Salesforce integration", "urgency": 0.94 },
{ "topic": "Enterprise API launch", "urgency": 0.91 }
],
"technologies_mentioned": [
{ "name": "Salesforce", "status": "in_use" },
{ "name": "REST API", "status": "in_use" }
],
"competitors_mentioned": [
{ "name": "Confluence" }
],
"company_twitter_handle": "@NotionHQ",
"company_twitter_url": "https://x.com/NotionHQ",
"company_twitter_bio": "Your connected workspace. Notes, docs, projects - all in one place.",
"company_twitter_followers": 892000,
"company_twitter_following": 1247,
"company_twitter_verified": true,
"company_twitter_verification_type": "business",
"company_twitter_total_tweets": 12400,
"company_twitter_dm_open": false,
"company_twitter_location": "San Francisco, CA",
"company_twitter_account_created": "2016-06-15",
"company_twitter_profile_picture": "https://pbs.twimg.com/profile_images/notionhq.jpg"
}
}Field Reference
Standard envelope and entity fields are shared across all signals - see Schema and Resolution. The fields below are specific to this signal:
Signal-Specific Fields
The data object contains everything unique to this signal type - the intelligence extracted from the company's tweet.
| Field | Type | Description |
|---|---|---|
summary | string | One-line headline describing the tweet's strategic significance (e.g., "Notion announces Salesforce integration, targeting revenue teams"). Designed for notifications and list views. Typically 10-20 words |
post_text | string | The full tweet text. Useful for referencing exact wording in outreach and understanding the company's messaging |
post_url | string (URL) | Direct link to the tweet on X. Useful for verification and display |
posted_date | string (date) | Date the tweet was posted. Useful for recency filtering |
tweet_id | string | Unique Twitter/X tweet identifier. Useful for API lookups and deduplication |
posting_source | string | Application used to post (e.g., "Sprout Social", "Twitter Web App"). Useful for identifying managed vs. organic posts |
language | string | ISO 639-1 language code of the tweet. Useful for filtering non-English content |
is_reply | boolean | Whether this tweet is a reply to another tweet. Replies often reveal more candid opinions |
replied_to_username | string | Username of the account being replied to (if is_reply is true) |
num_likes | integer | Like count at time of processing |
num_reposts | integer | Repost/retweet count. High reposts indicate announcements the market is amplifying |
num_replies | integer | Reply count. High replies suggest active discussion or controversy |
num_quotes | integer | Quote tweet count. Quotes often contain commentary from industry voices |
num_bookmarks | integer | Bookmark count. High bookmarks indicate content people want to reference later - a strong intent signal |
num_views | integer | View/impression count. Useful for understanding reach |
hashtags | array[string] | Hashtags used in the tweet. Useful for topic filtering |
mentions | array[string] | @mentions in the tweet. Useful for identifying partnerships and integrations |
urls | array[string] | URLs shared in the tweet. Often point to product pages, blog posts, or landing pages |
tags | array[string] | Topic tags extracted from the tweet content. Useful for signal filtering |
pain_points | array[object] | Challenges referenced in the tweet. Each entry has topic and intensity (0.0-1.0) |
pain_points[].topic | string | Description of the pain point |
pain_points[].intensity | float (0.0-1.0) | How strongly expressed |
initiatives | array[object] | Strategic initiatives announced. Each entry has topic and urgency (0.0-1.0). Useful for identifying companies actively investing in areas you serve |
initiatives[].topic | string | Description of the initiative |
initiatives[].urgency | float (0.0-1.0) | How immediate the initiative appears |
technologies_mentioned | array[object] | Technologies referenced. Each entry has name and status (in_use, evaluating, replacing, mentioned) |
technologies_mentioned[].name | string | Name of the technology |
technologies_mentioned[].status | string | Relationship to the technology |
competitors_mentioned | array[object] | Competitors named in the tweet. Each entry has name |
competitors_mentioned[].name | string | Competitor name |
quoted_tweet.text | string | Text of a quoted tweet, if this tweet quotes another. Provides additional context |
quoted_tweet.author.name | string | Display name of the quoted tweet's author |
quoted_tweet.author.userName | string | Username/handle of the quoted tweet's author |
company_twitter_handle | string | The company's Twitter/X handle (e.g., "@NotionHQ") |
company_twitter_url | string (URL) | Link to the company's Twitter/X profile |
company_twitter_bio | string | The company's Twitter bio. Useful for understanding how they position themselves |
company_twitter_followers | integer | Follower count. Useful for gauging the company's social reach |
company_twitter_following | integer | Following count |
company_twitter_verified | boolean | Whether the account is verified on X |
company_twitter_verification_type | string | Type of verification: business, government, blue |
company_twitter_total_tweets | integer | Total tweet count for the account |
company_twitter_dm_open | boolean | Whether DMs are open. Useful for social selling motions |
company_twitter_location | string | Location listed on the company's profile |
company_twitter_account_created | string (date) | When the account was created |
company_twitter_profile_picture | string (URL) | Profile picture URL |
Timing & Delivery
detected_atis when we processed the tweet. Useposted_datefor the original publication date.- One signal per company per tweet. Multiple tweets in a delivery window generate separate signals.
- Each delivery arrives in a timestamped folder. Treat all signals in a new folder as recent - no need to diff against prior deliveries.
Coverage
- Refresh: Monthly
- Coverage: Hundreds of thousands of company Twitter/X accounts
- Best for: Catching product announcements in real time, identifying strategic direction from public messaging, spotting new integrations and partnerships
Updated 14 days ago
