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

ItemValue
DeliveryFlat file (Google Cloud Storage)
Bucketgs://autobound-linkedin-reaction
Folder<YYYY-MM-DD-HH-MM-SS>/ (UTC run time)
Filesoutput.jsonl (nested), output.parquet (same rows, flat columns), distribution.json (rows by reaction age)
CadenceFirst delivery Nov 5, 2026. Weekly deliveries are planned.
HistoryEvery delivery ships all reaction ages. Most rows are recent: about half of the first delivery is from the last 30 days.
REST APINot 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

SignalSubtype EnumDescription
LinkedIn ReactionlinkedinPostReactionContact 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

FieldTypeDescription
signal_idstring (UUID v5)Stable ID. The same reaction gets the same ID in every delivery, so you can dedupe across deliveries.
signal_typestringAlways "linkedin-reaction"
signal_subtypestringAlways "linkedinPostReaction"
associationstringAlways "contact"
detected_atstring (ISO 8601)When we fetched the person's profile

Contact Object

FieldTypeDescription
contact.namestringFull name
contact.first_namestringFirst name
contact.last_namestringLast name
contact.linkedin_urlstringLinkedIn profile URL, as linkedin.com/in/<slug> (lowercase)
contact.job_titlestringCurrent job title
contact.emailstringBusiness email. Never a personal email. Null when the only email we have is probably from a past employer.
contact.headlinestringLinkedIn headline
contact.locationstringLocation text from the profile
contact.country_codestringTwo-letter country code
contact.followersintegerLinkedIn followers

Company Object

The person's current employer.

FieldTypeDescription
company.namestringCompany name
company.linkedin_urlstringCompany LinkedIn page
company.domainstringCompany website domain
company.industriesarray of stringIndustries
company.employee_count_lowintegerHeadcount range, low end
company.employee_count_highintegerHeadcount range, high end. Null for the top range (10,001+).
company.descriptionstringCompany description

Reaction Data

FieldTypeDescription
data.reaction_typestringLIKE 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_textstringThe activity text: "liked this" or "reacted on this"
data.reacted_atstring (ISO 8601)When the person reacted (exact, read from the reaction ID)
data.reaction_urlstringLink to the reaction activity

Reacted Post Object

FieldTypeDescription
data.reacted_post.post_idstringPost ID
data.reacted_post.post_urlstringPost URL
data.reacted_post.post_textstringPost text
data.reacted_post.posted_datestring (ISO 8601)When the post was published
data.reacted_post.num_reactionsintegerReactions on the post
data.reacted_post.num_commentsintegerComments on the post
data.reacted_post.top_reaction_typesarray of stringMost common reaction types on the post
data.reacted_post.media_typestringimage, video, article, document, none and similar
data.reacted_post.hashtagsarray of stringHashtags in the post, or null
data.reacted_post.mentionsarray of stringNames mentioned in the post, or null
data.reacted_post.is_resharebooleanTrue when the post shares another post
data.reacted_post.author_namestringPost author name
data.reacted_post.author_urlstringPost author LinkedIn URL (person or company page)
data.reacted_post.author_typestringperson or company

Coverage (first delivery, Nov 5, 2026)

MeasureValue
Reactions7.8M
People who reacted1.36M
Reactions from the last 30 days4.0M
contact.job_title filled99%
contact.email filled73%
company.domain filled95%
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.


Did this page help you?