> ## 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.

# Contact Social Engagements

> Contact Social Engagements documentation for TAMradar API.

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

### Content Structure

The `content` object contains the engagement information:

| Field                    | Type   | Required | Description                                                                   |
| ------------------------ | ------ | -------- | ----------------------------------------------------------------------------- |
| post\_url                | string | Yes      | URL of the social post that received engagement                               |
| post\_content            | string | Yes      | Text content of the original post                                             |
| post\_channel            | string | Yes      | Social media channel (always "linkedin")                                      |
| post\_posted\_at         | string | Yes      | Date when the post was published (YYYY-MM-DD)                                 |
| engagement\_type         | string | Yes      | Type of engagement: "reaction", "comment", or "repost"                        |
| engagement\_content      | string | No       | Content of the engagement (comment text or repost text). Null for reactions.  |
| engagement\_content\_url | string | No       | URL of the engagement content (for reposts). Null for reactions and comments. |
| author                   | object | Yes      | Details of the person who engaged with the post                               |

#### Author Object Structure

The `author` object contains details about the person who engaged:

| Field           | Type   | Nullable | Description                                                     |
| --------------- | ------ | -------- | --------------------------------------------------------------- |
| profile\_type   | string | Yes      | Type of profile: "contact" or "company"                         |
| first\_name     | string | No       | First name of the person who engaged, or company name           |
| last\_name      | string | Yes      | Last name of the person - `null` if `profile_type` is `company` |
| profile\_url    | string | No       | Social profile URL of the person who engaged                    |
| title           | string | Yes      | Job title or position                                           |
| company\_name   | string | Yes      | Company name where they work                                    |
| company\_domain | string | Yes      | Company domain where they work                                  |
| country         | string | Yes      | Country location                                                |

### Example

This example includes [base webhook fields](/webhooks/overview) along with contact-social-engagement-specific content:

```json theme={null}
{
  "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": "contact_social_engagements",
    "domain": null,
    "next_charge_at": "2025-11-10T23:21:41Z",
    "custom_fields": {
      "account_manager": "sarah.smith",
      "priority": "high"
    }
  },
  "content": {
    "post_url": "https://www.linkedin.com/posts/someone_activity-123456789",
    "post_content": "Just launched our new AI product! #AI #ProductLaunch",
    "post_channel": "LinkedIn",
    "post_posted_at": "2025-10-10",
    "engagement_type": "Reaction",
    "engagement_content": null,
    "engagement_content_url": null,
    "author": {
      "profile_type": "contact",
      "first_name": "John",
      "last_name": "Smith",
      "profile_url": "https://www.linkedin.com/in/johnsmith",
      "title": "VP of Engineering",
      "company_name": "Tech Corp",
      "company_domain": "techcorp.com",
      "country": "United States"
    }
  }
}
```

### Use Cases

**Sales Intelligence**\
When a VP or C-level executive from a target account engages with your tracked contact's post about industry trends, this signals interest and creates a warm introduction opportunity. The engagement data provides context for outreach - you know what content resonated with them.

**Relationship Mapping**\
By tracking who engages with your key contacts' posts, you can identify hidden connections and influencers within target organizations. If multiple people from the same company engage with content, it reveals the internal network and decision-making structure.

**Engagement Pattern Analysis**\
Track which types of content (product launches, thought leadership, company updates) generate the most engagement from valuable contacts. This helps understand what messaging resonates with your target audience and when they're most active.

**Warm Lead Identification**\
When someone consistently engages with your tracked contact's content through comments and reactions, they're demonstrating active interest. These engaged individuals become warm leads for outreach, as they're already familiar with your contact's expertise and perspectives.

### 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 person'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