Company LinkedIn Posts
Surface and analyze a prospect company's LinkedIn posts to identify initiatives, pain points, and engagement patterns.
Overview
Company LinkedIn Posts surface what your prospects are publicly saying about their priorities, challenges, and initiatives.
We track 4M+ company LinkedIn pages. To maximize coverage where it matters, we optimize the scan pool by geography, industry, and company importance—prioritizing high-value accounts while maintaining broad distribution. Each post is analyzed to extract structured pain points, initiatives, technologies mentioned, and competitors referenced.
The result: you can reference a company's own words in outreach, time messages around announcements, and infer priorities they've made public—without manually scrolling through feeds.
How we build and maintain coverage: Our scan pool is designed to maximize buyer coverage across your highest-value accounts while maintaining a well-distributed sample across geographies, industries, and company sizes.
We continuously ingest new LinkedIn company page URLs and evaluate whether we can successfully gather posts from them. We plan to roughly double the total number of companies in our monitoring pool in the near term - expanding coverage for mid-market, SMB, and international segments.
Subtype
| Signal | Subtype Enum | Description |
|---|---|---|
| Company LinkedIn posts | linkedinPost | Recent posts from company LinkedIn page |
Schema
{
"signal_id": "7f09831f-e135-49da-8db9-c3f48fd2deff",
"signal_type": "linkedin-post-company",
"signal_subtype": "linkedinPost",
"signal_name": "Company posted on LinkedIn",
"association": "company",
"detected_at": "2026-01-06T19:12:42.111Z",
"company": {
"name": "First Command Financial Services, Inc.",
"domain": "firstcommand.com",
"linkedin_url": "linkedin.com/company/first-command-financial-services",
"employee_count_low": 1001,
"employee_count_high": 5000,
"industries": [
"Financial Services"
]
},
"data": {
"post_url": "https://www.linkedin.com/feed/update/urn:li:activity:7274105232534462465/",
"post_text": "Advisor Spotlight! How have Advisors changed their business practices over the past five years? See the variety of ways...",
"posted_date": "2024-12-09T18:40:42.000Z",
"num_likes": 47,
"num_comments": 4,
"tags": [
"Leadership",
"Business Strategy",
"Financial Planning"
],
"summary": "First Command highlights innovative business practices from successful financial advisors.",
"pain_points": [],
"initiatives": [
{
"topic": "showcasing advisor success stories",
"urgency": 0.7
}
],
"technologies_mentioned": [],
"competitors_mentioned": []
}
}Field Reference
Core Fields
| Field | Type | Description |
|---|---|---|
signal_id | string (UUID) | Unique identifier for this signal |
signal_type | string | Always "linkedin-post-company" |
signal_subtype | string | Always "linkedinPost" |
signal_name | string | Always "Company posted on LinkedIn" |
association | string | Always "company" |
detected_at | string (ISO 8601) | When we detected this signal |
Company Object
| Field | Type | Description |
|---|---|---|
company.name | string | Company name |
company.domain | string | Company website domain |
company.linkedin_url | string | LinkedIn company URL |
company.industries | array[string] | Industry classifications |
company.employee_count_low | integer | Lower bound of employee count |
company.employee_count_high | integer | Upper bound of employee count |
company.description | string | Company description |
Data Object
| Field | Type | Description |
|---|---|---|
data.post_url | string (URL) | Link to the LinkedIn post |
data.post_text | string | Full post content |
data.posted_date | string (ISO 8601) | When the post was published |
data.num_likes | integer | Number of likes on the post |
data.num_comments | integer | Number of comments on the post |
data.tags | array[string] | Gemini-generated topic tags (~300 possible values) |
data.summary | string | LLM-generated 10-15 word summary of the post |
data.pain_points | array[object] | Challenges or problems mentioned in the post |
data.initiatives | array[object] | Projects or strategic moves mentioned in the post |
data.technologies_mentioned | array[object] | Tech products or platforms referenced |
data.competitors_mentioned | array[object] | Other companies referenced in the post |
Pain Points Object
| Field | Type | Description |
|---|---|---|
topic | string | Description of the pain point |
intensity | float (0-1) | How acute the pain is expressed (higher = more acute) |
Initiatives Object
| Field | Type | Description |
|---|---|---|
topic | string | Description of the initiative |
urgency | float (0-1) | How immediate/active the initiative is (higher = more urgent) |
Technologies Mentioned Object
| Field | Type | Description |
|---|---|---|
name | string | Name of the technology, product, or platform |
status | enum | Relationship: evaluating, using, implemented, migrating_from, migrating_to, churned, considering, integrated, building_on, hiring_for |
Competitors Mentioned Object
| Field | Type | Description |
|---|---|---|
name | string | Name of the competitor company |
Example Output
"Saw your recent LinkedIn post about the AI adoption event—sounds like a great initiative. When organizations are rolling out AI tools, having the right data infrastructure is critical. Would love to share how we're helping similar public sector teams scale their AI implementations."
Identity Resolution
Company LinkedIn post signals are resolved to a company record using a direct, deterministic path:
- LinkedIn company page URL captured from the post activity
- Matched against our company database (75M+ companies) using the LinkedIn company URL
- Company firmographic data attached: domain, industries, employee count range, description
Key Points
- Direct match. LinkedIn company page URLs are unique identifiers — there is no ambiguity.
- Coverage:
company.domainis populated on 99%+ of signals.company.linkedin_urlis populated on 95%+. - Join on
company.domainorcompany.linkedin_urlto match signals to your CRM or data warehouse.
Full matching guide with SQL examples: Resolution
Coverage
- Refresh: Every 2 weeks
- Coverage: 25-50% of companies
- Best for: Trigger-based outreach, understanding company priorities, timing outreach around announcements
How Coverage Works
Our scan pool balances two objectives: deep buyer coverage on your most important accounts, and broad distribution across the market.
Prioritizing hot accounts. Companies identified as high-value—based on account importance, industry fit, and size—are prioritized for monitoring. This ensures the accounts most likely to appear in your pipeline have the highest likelihood of coverage.
Sampling across segments. Beyond priority accounts, we maintain a well-distributed sample across geographies, industries, and company sizes. This prevents blind spots in underrepresented segments and ensures signal coverage scales with your market, not just your target account list.
Continuous URL ingestion. We are constantly adding new LinkedIn company page URLs to the scan pool and evaluating whether we can successfully gather posts from them. Pages that are publicly accessible and active are retained; inactive or restricted pages are cycled out.
Pool expansion. We plan to roughly double the total number of companies in our monitoring pool in the near term. This expansion specifically targets improved coverage for mid-market and SMB companies, international markets (EMEA, APAC), and emerging industries and verticals.
Updated about 16 hours ago
