Job Change Tracker

Send the contacts in your CRM. Get one row back per person: where they work now, their title, when they started, their role history, and whether they left the company you know them at, landed somewhere new, or moved up inside the same company.

Every row says how the person was matched, which source the answer came from, and how old that source is.

What it does

For each person you send (a name plus the company your records place them at), the actor:

1. Reads any role history you already hold, such as a stored copy from your outreach tool or your own CRM. This costs nothing extra.
2. Finds the person's LinkedIn profile URL with your web search key when you did not send one. A namesake check accepts a profile only when the name matches and the history or the search result shows your company.
3. Reads the search result line for that profile, which usually names the current title and company.
4. Reads the role history with start and end months from Prospeo on your key.
5. Checks the company's own team and about pages, and Google News, for free.
6. Verifies the old work address with BounceBan on your key, only while the person still reads as at the company.

It then works out the status against the company you sent. Career Break and "Open to work" entries never count as a job. A move to a new employer is a new hire. A new role at the same employer, with the earlier role open or ended within 3 months, is a promotion.

The actor never opens linkedin.com and never calls another developer's actor. Paid lookups run on your own provider keys and bill your provider accounts.

What you get

Field	Example
employment_status	current, between_roles, unknown
leaver_status	still_at_company, left, unknown
landing_status	landed, not_landed, not_applicable, unknown
current_company_name, current_title	AccuWeather, VP, AI Partnerships
start_month, start_precision, days_in_role	2026-08, month, 74
move_type, move_type_reason, seniority_change	new_hire, different_company_name, same
previous_company_name, previous_title, left_month	Dataminr, Sr. Director, 2026-07
role_history	array of roles with company, title, start and end month
match_method, match_confidence, match_evidence	name_search, high, ["name","company_domain"]
source, source_detail, source_date, source_age_days	byod, heyreach, 2026-10-07, 7
evidence, sources_tried	why the status was set, and what was tried
read_status, error_reason	ok, or why there is no reading
billable_events_json	the events charged for this row

Rows are flat and snake_case, so they load into Clay, a sheet, or a CRM as they are. Two dataset views come with every run: Overview and Evidence.

Input

One person:

{
  "person_name": "Jane Doe",
  "company_domain": "acme.io",
  "company_name": "Acme",
  "last_known_title": "Head of Growth",
  "profile_url": "https://www.linkedin.com/in/janedoe",
  "email": "jane@acme.io",
  "input_id": "crm-48213",
  "serperApiKey": "...",
  "prospeoApiKey": "...",
  "bouncebanApiKey": "..."
}

Many people go in people, each with the same keys. A person can carry known_history, a role history you already hold:

{ "source": "heyreach", "source_date": "2026-10-07", "experiences": "[{\"companyName\":\"Acme\",\"title\":\"Head of Growth\",\"start\":{\"year\":2021,\"month\":3},\"end\":{\"year\":2026,\"month\":7}}]" }

roles (with company_name, title, start_month, end_month) and a LinkedIn reader row (linkedin_reader) are read too. A history newer than maxSourceAgeDays (default 30) skips the Prospeo call for that person.

Keys and what each one costs you

Key	Used for	Calls per person
Serper or SerpAPI	Profile lookup and the current role line	1 with a profile URL, 1 to 3 without
Prospeo	Role history with months	0 or 1 (0 when your fresh history is used)
BounceBan	Old work address check	0 or 1, only when the person still reads as at the company

With no key at all, the actor still reads your own history, the company team pages, and Google News.

Pricing

Pay per event. You pay for results, plus a small start fee per run.

Event	Fires when	Free	Bronze	Silver	Gold
person_read	A person comes back with read_status ok	0.025 USD	0.02375 USD	0.0225 USD	0.02125 USD
profile_resolved	You sent no profile URL and the run found and accepted one at high or medium match	0.006 USD	0.0057 USD	0.0054 USD	0.0051 USD
apify-actor-start	Once per run, per GB of memory (one at the 256 MB default)	0.001 USD	0.001 USD	0.001 USD	0.001 USD

Not charged: not found, ambiguous, error, and skipped rows; cache hits; and a person repeated in the same run. Set max_charge_usd and the run stops before any row that would pass it. On the free Apify plan the actor reads up to 60 people a month (1.50 USD of evaluation).

Limits

• Your sources decide coverage. In a 60 person test (39 leavers, 21 still employed), keys alone caught 12 of 39 leavers with 0 false flags in 17; adding a fresh history of the buyer's own raised it to 28 of 39, still with 0 false flags. Prospeo lags for people who left, which is why a "still at company" answer from it carries low confidence.
• The search result line is a summary, not a full profile. Start months come from your own history or Prospeo.
• left_month needs a dated history. A leaver found only by the search line or the email check has no month.
• Two profiles that both pass the namesake check return ambiguous and nothing is charged.

Pairs with

• New Hire Finder: from a company, find who started a matching role.
• Career Change Signal Engine: watches a contact list over time and delivers only the changes.

Built by Mamba Labs.