A job-change alert does not rewrite a message already waiting in a campaign. Check three records separately: the current LinkedIn profile or Sales Navigator lead, the CRM contact, and the outreach tool's campaign lead. If the old employer still appears in the final preview, pause that lead. A refreshed CRM field is only useful here if the campaign reads it before the next action.
An alert, a CRM change, and a campaign field are different events
LinkedIn says saved Sales Navigator leads can generate job-change alerts. Its separate Update Leads and Contacts feature lets eligible Advanced Plus users review discrepancies and confirm selected CRM changes; an admin must enable it. Neither description says that an unrelated outreach campaign's imported fields are rewritten when an alert appears. Treat the alert as a reason to inspect the person, not as evidence that every downstream record is current.
Ask which system owns company and title, how the person is matched across systems, and what actually triggers a refresh. Write down the last verified date beside the values. If the tool cannot show the origin of a company field, do not use that field as the sole basis for a personal claim in a scheduled message.
Sources: LinkedIn Sales Navigator saved-lead alerts, LinkedIn Update Leads and Contacts
Find where the old employer persists
HeyReach documents a way to update custom variables on leads in a list through its API and to preview the values used in a campaign message. It also warns that a custom variable named Company can be overridden by its default company variable. Updating one field, therefore, is not proof that the template will use it. The vendor's campaign guide says a launched campaign's selected lead list cannot be changed; check the campaign lead and the final rendered message, not just an upstream CSV or CRM record.
A role change can also alter whether the person belongs in the campaign at all. If the account, territory, or reason for contact changed, stop the pending step while its owner decides whether to continue. Replacing an old company name with a new one in a template does not by itself make the message relevant.
Sources: HeyReach custom-variable import and update, HeyReach campaign lead setup
Test one controlled change before trusting the sync
Use a consented internal test record with a future action and keep sending disabled. Give it an old company in the source list, CRM, and campaign. Change the company in the designated source, then record what each destination shows and when. Preview the next message. Repeat with a changed title and with a person who should leave the audience entirely. This is a proposed acceptance test, not a claim that the products named here passed it.
The test fails if a field updates only in the lead list, a campaign keeps an older value, the template selects a different company field, or a removed lead remains queued. If the product cannot expose a preview or pending-action state, leave the lead paused and ask support which snapshot the next step will use.
- Identity: match the same LinkedIn profile in the alert, CRM, and campaign lead.
- Propagation: record the old and new values, update trigger, and time seen in each system.
- Execution: inspect the exact next message and queued action before enabling a send.
- Ownership: name the person who approves continuing or removing the lead after a role change.
Sources: LinkedIn Update Leads and Contacts, HeyReach custom-variable import and update
Keep the policy decision separate from data freshness
LinkedIn says it does not permit third-party software that scrapes, modifies, or automates activity on its website and warns that prohibited use may lead to account restrictions. A correct company field does not establish that an automated send is approved. The account owner must decide whether the tool's actual operation fits the platform rules; the same freshness check is useful for a manually written native LinkedIn message.
If the three records disagree, do not launch a repair campaign against the whole list. Hold the affected people, reconcile the source and campaign fields, and inspect their next messages. The decision to contact someone after a job change belongs to a reviewer who can see the new role and the reason for reaching out.