LinkedIn Reaction
Posts that a contact reacted to on LinkedIn (like, celebrate, support and more), with the post and its author.
Signal type: linkedin-reactions-contact in the API, linkedin-reaction in flat files.
Overview
A reaction is the lightest form of engagement on LinkedIn, and the most common. In a typical month, about 27 in 100 LinkedIn profiles react to at least one post, while about 4 in 100 write or repost one. Reactions show who a person pays attention to and what topics they care about, long before they post or comment themselves.
Each record is one person reacting to one post. It carries the person (resolved to a business contact with a work email when we can), their current company, the reaction, and the post with its author.
Delivery
| Item | Value |
|---|---|
| Delivery | Flat file (Google Cloud Storage) |
| Bucket | gs://autobound-linkedin-reaction |
| Folder | <YYYY-MM-DD-HH-MM-SS>/ (UTC run time) |
| Files | output.jsonl (nested), output.parquet (same rows, flat columns), distribution.json (rows by reaction age) |
| Cadence | First delivery Nov 5, 2026. Weekly deliveries are planned. |
| History | Every delivery ships all reaction ages. Most rows are recent: about half of the first delivery is from the last 30 days. |
| REST API | Not available yet |
Parquet note: Parquet column names are the dotted JSON paths (for example
contact.email). Some tools, such as BigQuery external tables, do not accept dots in column names. Use the JSONL file in those tools.
Subtype
| Signal | Subtype Enum | Description |
|---|---|---|
| LinkedIn Reaction | linkedinPostReaction | Contact reacted to a LinkedIn post |
Schema
{
"signal_id": "51d4c02a-bfa5-529f-828a-c91458bd098f",
"signal_type": "linkedin-reaction",
"signal_subtype": "linkedinPostReaction",
"association": "contact",
"detected_at": "2026-11-02T18:45:39.816Z",
"contact": {
"name": "Jordan Lee",
"first_name": "Jordan",
"last_name": "Lee",
"linkedin_url": "linkedin.com/in/jordan-lee-example",
"job_title": "Director of Revenue Operations",
"email": "[email protected]",
"headline": "RevOps leader | Building GTM systems",
"location": "Austin, Texas, United States",
"country_code": "US",
"followers": 2140
},
"company": {
"name": "Example Analytics",
"linkedin_url": "linkedin.com/company/example-analytics",
"domain": "example.com",
"industries": ["Software Development"],
"employee_count_low": 201,
"employee_count_high": 500,
"description": "Example Analytics provides revenue analytics software for B2B sales teams."
},
"data": {
"reaction_type": "LIKE",
"reaction_text": "liked this",
"reacted_at": "2026-11-01T14:22:10.512Z",
"reaction_url": "https://www.linkedin.com/feed/update/urn:li:activity:7522000000000000000",
"reacted_post": {
"post_id": "7521900000000000000",
"post_url": "https://www.linkedin.com/posts/example-post",
"post_text": "We just rolled out a new forecasting process across our sales org...",
"posted_date": "2026-10-31T16:05:44.000Z",
"num_reactions": 184,
"num_comments": 12,
"top_reaction_types": ["LIKE", "PRAISE", "INTEREST"],
"media_type": "image",
"hashtags": ["RevOps", "Forecasting"],
"mentions": null,
"is_reshare": false,
"author_name": "Sam Rivera",
"author_url": "https://www.linkedin.com/in/sam-rivera-example",
"author_type": "person"
}
}
}Field Reference
Core Fields
| Field | Type | Description |
|---|---|---|
signal_id | string (UUID v5) | Stable ID. The same reaction gets the same ID in every delivery, so you can dedupe across deliveries. |
signal_type | string | Always "linkedin-reaction" |
signal_subtype | string | Always "linkedinPostReaction" |
association | string | Always "contact" |
detected_at | string (ISO 8601) | When we fetched the person's profile |
Contact Object
| Field | Type | Description |
|---|---|---|
contact.name | string | Full name |
contact.first_name | string | First name |
contact.last_name | string | Last name |
contact.linkedin_url | string | LinkedIn profile URL, as linkedin.com/in/<slug> (lowercase) |
contact.job_title | string | Current job title |
contact.email | string | Business email. Never a personal email. Null when the only email we have is probably from a past employer. |
contact.headline | string | LinkedIn headline |
contact.location | string | Location text from the profile |
contact.country_code | string | Two-letter country code |
contact.followers | integer | LinkedIn followers |
Company Object
The person's current employer.
| Field | Type | Description |
|---|---|---|
company.name | string | Company name |
company.linkedin_url | string | Company LinkedIn page |
company.domain | string | Company website domain |
company.industries | array of string | Industries |
company.employee_count_low | integer | Headcount range, low end |
company.employee_count_high | integer | Headcount range, high end. Null for the top range (10,001+). |
company.description | string | Company description |
Reaction Data
| Field | Type | Description |
|---|---|---|
data.reaction_type | string | LIKE for a like. UNKNOWN for any other reaction (celebrate, support, love, insightful, funny): the public page shows these only as "reacted on this". |
data.reaction_text | string | The activity text: "liked this" or "reacted on this" |
data.reacted_at | string (ISO 8601) | When the person reacted (exact, read from the reaction ID) |
data.reaction_url | string | Link to the reaction activity |
Reacted Post Object
| Field | Type | Description |
|---|---|---|
data.reacted_post.post_id | string | Post ID |
data.reacted_post.post_url | string | Post URL |
data.reacted_post.post_text | string | Post text |
data.reacted_post.posted_date | string (ISO 8601) | When the post was published |
data.reacted_post.num_reactions | integer | Reactions on the post |
data.reacted_post.num_comments | integer | Comments on the post |
data.reacted_post.top_reaction_types | array of string | Most common reaction types on the post |
data.reacted_post.media_type | string | image, video, article, document, none and similar |
data.reacted_post.hashtags | array of string | Hashtags in the post, or null |
data.reacted_post.mentions | array of string | Names mentioned in the post, or null |
data.reacted_post.is_reshare | boolean | True when the post shares another post |
data.reacted_post.author_name | string | Post author name |
data.reacted_post.author_url | string | Post author LinkedIn URL (person or company page) |
data.reacted_post.author_type | string | person or company |
Coverage (first delivery, Nov 5, 2026)
| Measure | Value |
|---|---|
| Reactions | 7.8M |
| People who reacted | 1.36M |
| Reactions from the last 30 days | 4.0M |
contact.job_title filled | 99% |
contact.email filled | 73% |
company.domain filled | 95% |
Reactions that are likes (LIKE) | 82% |
Identity Resolution
Each reaction starts from a LinkedIn profile URL, which is a unique identifier. We match that URL to our contact and company database to add the job title, the business email and the company details. See Resolution for how matching works.
Not in this version
These fields are planned and are not in the file today:
- AI fields on the post (summary, pain points, initiatives, technologies, competitors)
- The post author's company
- Reactions on comments (only reactions on posts today)
- Contact seniority and department
Need a sample? Contact [email protected] for sample reactions on your target accounts.
Updated about 4 hours ago

