Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tamradar.com/llms.txt

Use this file to discover all available pages before exploring further.

Notifies you when people engage with posts from companies you’re tracking on social channels. This includes reactions (like, celebrate, support, etc.), comments, and reposts on the tracked company’s posts.

​
Content Structure

The content object contains the engagement information:
FieldTypeRequiredDescription
post_urlstringYesURL of the social post that received engagement
post_contentstringYesText content of the original post
post_channelstringYesSocial media channel
post_posted_atstringYesDate when the post was published (YYYY-MM-DD)
engagement_typestringYesType of engagement: "reaction", "comment", or "repost"
engagement_contentstringNoContent of the engagement (comment text or repost text). Null for reactions.
engagement_content_urlstringNoURL of the engagement content (for reposts). Null for reactions and comments.
authorobjectYesDetails of the person who engaged with the post

​
Author Object Structure

The author object contains details about the person who engaged:
FieldTypeNullableDescription
profile_typestringYesType of profile: "contact" or "company"
first_namestringYesFirst name of the person who engaged - null if profile_type is "company"
last_namestringYesLast name of the person - null if profile_type is "company"
profile_urlstringNoSocial profile URL of the person or company who engaged
titlestringYesJob title or position - null if profile_type is "company"
company_namestringYesCompany name where the person works, or the engaging company name if profile_type is "company"
company_domainstringYesCompany domain where the person works, or the engaging company domain if profile_type is "company"
countrystringYesCountry location

​
Examples

These examples include base webhook fields along with company-social-engagement-specific content:

​
Contact Engagement Example

When an individual person engages with a company’s post: 
{
  "update_id": "fe00b8e8-ae51-4e63-b9af-fc45dbf9517b",
  "update_type": "radar_finding",
  "record_id": "ae3929d4-d2c6-4008-a756-d5669c919451",
  "discovered_at": "2025-10-11T23:20:16Z",
  "data": {
    "radar_id": "05c4db36-3d28-4475-a4e8-52e0fcf58477",
    "radar_type": "company_social_engagements",
    "domain": "stripe.com",
    "next_charge_at": "2025-11-10T23:21:41Z",
    "custom_fields": {
      "campaign": "enterprise-accounts",
      "priority": "high"
    }
  },
  "content": {
    "post_url": "https://www.linkedin.com/posts/stripe_activity-123456789",
    "post_content": "Excited to announce our new payment infrastructure for global enterprises! #Payments #Fintech",
    "post_channel": "LinkedIn",
    "post_posted_at": "2025-10-10",
    "engagement_type": "Comment",
    "engagement_content": "This looks great! We've been looking for exactly this kind of solution.",
    "engagement_content_url": null,
    "author": {
      "profile_type": "contact",
      "first_name": "Sarah",
      "last_name": "Johnson",
      "profile_url": "https://www.linkedin.com/in/sarahjohnson",
      "title": "VP of Finance",
      "company_name": "TechCorp Inc",
      "company_domain": "techcorp.com",
      "country": "United States"
    }
  }
}

​
Company Engagement Example

When a company account engages with another company’s post: 
{
  "update_id": "8a1c3f2e-9d4b-4e7f-a5c8-1b3e5f7g9h2j",
  "update_type": "radar_finding",
  "record_id": "c2f8a9d1-4e6b-4a8c-9f7e-3d5a7b9c1e2f",
  "discovered_at": "2025-10-11T15:30:45Z",
  "data": {
    "radar_id": "05c4db36-3d28-4475-a4e8-52e0fcf58477",
    "radar_type": "company_social_engagements",
    "domain": "stripe.com",
    "next_charge_at": "2025-11-10T23:21:41Z",
    "custom_fields": {
      "campaign": "enterprise-accounts",
      "priority": "high"
    }
  },
  "content": {
    "post_url": "https://www.linkedin.com/posts/stripe_activity-987654321",
    "post_content": "Stripe continues to lead in payment innovation with our latest security features!",
    "post_channel": "LinkedIn",
    "post_posted_at": "2025-10-10",
    "engagement_type": "reaction",
    "engagement_content": null,
    "engagement_content_url": null,
    "author": {
      "profile_type": "company",
      "first_name": null,
      "last_name": null,
      "profile_url": "https://www.linkedin.com/company/techcorp",
      "title": null,
      "company_name": "TechCorp Inc",
      "company_domain": "techcorp.com",
      "country": "United States"
    }
  }
}

​
Use Cases

Competitor Intelligence
When executives from target accounts engage with your competitors’ posts about new product launches or company updates, this signals interest in specific solutions. The engagement data reveals which competitors are getting attention from your prospects and what messaging resonates. Market Validation
Track how your target market responds to competitor announcements, funding news, or product updates. High engagement from your ideal customer profile validates market demand for specific solutions and helps inform your product strategy. Lead Scoring & Timing
When someone from a target account actively engages with competitor content through comments and reactions, they’re signaling active buying interest. These engaged prospects become high-priority leads for competitive positioning and timely outreach. Content Strategy Intelligence
Analyze which types of competitor content (product launches, thought leadership, company updates) generate the most engagement from valuable prospects. This intelligence guides your own content strategy and competitive messaging.

​
Technical Notes

  • Engagement Limits: We capture up to 200 engagements per post to ensure timely delivery while covering the most engaged audience
  • Post Monitoring Window: We look back 48 hours for existing posts and monitor each post for 48 hours total
  • Incremental Updates: We continuously check for new engagements during the monitoring window, sending webhooks only for net-new activities (no duplicates)
  • Lookback Period for First Day: If no post is found from the past 48 hours when you created the radar, TAMradar will still try to fetch the company’s last post. Keep in mind that this might return posts from the past, so check the post_posted_at field to ensure smooth processing