Create Contact Radar
Create a contact radar for person-level tracking.
updates_since to include recent activity. Choose a date a few weeks or
months back for eligible activity from that period plus ongoing updates. If
omitted, social-activity radars start at their exact creation time, not the start of today:
even a post published one minute earlier is excluded. Your first check may return
no results, and updates may take time to arrive.contact_job_changes monitors detected changes, not a historical list of job moves.updates_since from your chosen lookback.Body
The type of contact activity to track. Choose based on your tracking needs:
• contact_job_changes: Track when someone leaves, gets promoted, or changes roles at a company. Requires domain and at least one identifier (email, profile_url, or full_name).
• contact_social_engagements: Track when people engage (react, comment, repost) with a specific person's social media posts. Requires profile_url.
• contact_social_posts: Track social media posts FROM a specific person. Monitors when the contact themselves posts content on social platforms. Requires profile_url.
contact_job_changes, contact_social_engagements, contact_social_posts Optional RFC 3339 timestamp with a UTC offset. Recommended for recent activity: choose a date weeks or months back. If omitted, most radars start at their exact creation time, not the start of today; even a post published one minute earlier is excluded. Initial checks may return no results; immediate updates are not guaranteed. New hires and promotions compare UTC calendar months, starting with the cutoff month (creation month if omitted). Contact job changes monitor detected changes, not historical job moves. TAMradar stores the timestamp in UTC. It must be now or in the past, at most five calendar years old. The five-second clock-skew tolerance does not allow future scheduling.
LinkedIn profile URL of the person to track.
• For contact_job_changes: Optional LinkedIn person profile using the /in/ path (used alongside other identifiers). Company, school, and legacy /pub/ URLs are rejected. • For contact_social_engagements: Required LinkedIn, X, or Twitter profile (this is whose engagement activity we'll track) • For contact_social_posts: Required LinkedIn, X, or Twitter profile (this is whose posts we'll track)
Protocol (https://) is automatically added if missing.
"https://www.linkedin.com/in/johndoe"
Company domain where the contact works.
• Required for contact_job_changes (the company you're tracking them at) • Optional for contact_social_engagements (not needed for social tracking) • Optional for contact_social_posts (can be used to associate the contact with a company)
Automatically normalized - strips protocol, www, paths.
"stripe.com"
Contact's individual email address. Used for contact_job_changes only. Role-based, shared, and placeholder addresses such as info@, sales@, and noreply@ are rejected. At least one identifier (email, profile_url, or full_name) is required for job change tracking.
"john.doe@stripe.com"
Contact's full name. Only letters, spaces, hyphens (-), and apostrophes (') are allowed — abbreviations with periods (e.g. J.) will be rejected. Clean the name before submitting. Used for contact_job_changes only. At least one identifier (email, profile_url, or full_name) is required for job change tracking. full_name is not used as a duplicate key; duplicate matching uses email or the normalized LinkedIn profile URL within the same domain and radar type.
"John Doe"