A Visible LinkedIn Repost Lost Its Reposter-Profile Link: Freeze Amplifier Attribution

Treat this as an internal-record recovery scenario. The retained repost may still be visible to your team, while the internal relationship that previously connected it to a reposter profile is absent or detached; a retained link may instead be stale.

Do not infer an actor from a name fragment, a campaign label, or a later comment. Freeze every downstream record that relies on the detached edge until a reviewer can trace a candidate profile back to retained evidence.

• Preserve the repost ID exactly as stored.
• Preserve the source-post ID and any recorded parent or root relationship.
• Stop dependent attribution changes and reporting rollups, including automated follow-up.

Which intact profile created the retained visible repost?

Start with the repost record, not the profile directory. LinkedIn's Posts API documents an author field on a post and documents reshareContext.parent, with reshareContext.root derived from that parent.

Use the original stored author or profile identifier only when it is present in an immutable export, approved audit record, or prior verified capture tied to the same repost ID. Content text and an author-display-name hash can support a match alongside the timestamp, but they do not replace direct prior-link proof.

If two profiles remain plausible, keep the edge unresolved. A correct unknown is safer than assigning amplification credit to the wrong person.

Which records should stay frozen while identity is checked?

Freeze every record that says or implies that a specific profile amplified the source post. That includes qualification fields built from the repost, comments queued because of the repost, campaign notes, attribution dashboards, and reports that count the event toward a person or account.

Keep raw observations separate from conclusions. A stored repost ID and source-post relationship can remain in the ledger. A claim that a named profile created it stays on hold until the actor edge has proof.

LinkedIn's Network Update Social Actions documentation describes social actions attached to shares or posts and also to comments, with examples that include an actor. Use any retained social-action record as evidence only when its target and actor identifiers can be traced to the same recovery case.

• Hold automated audience changes based on the proposed reposter.
• Hold manual credit or performance reporting tied to the proposed reposter.
• Retain the raw event and its source-post lineage for audit.

How do you restore the actor edge without changing the repost relationship?

Create a new internal actor-edge record rather than overwriting the original repost record. Link the candidate profile ID to the exact repost ID, attach the prior-link proof, record the reviewer, and mark the restoration time.

Do not edit the source-post relationship to make an actor match appear cleaner. LinkedIn documents a reshare parent and a derived root in the post response, so preserve those values as the repost's lineage anchor. Posts API

Release held records only after the reviewer confirms that the repost ID, source-post lineage, candidate profile ID, and prior-link proof all point to the same event.

• Record the restoration as a new auditable edge.
• Attach the exact prior-link evidence.
• Require reviewer release before dependent records resume.

What counts as enough proof to release the recovery?

Direct prior-link proof is the release standard. Examples include an immutable export that contains the repost ID and profile ID together. A prior approved audit snapshot or a retained system event that binds both identifiers also qualifies.

A content hash, display-name match, or shared campaign context can narrow the review. It cannot independently establish the actor edge. If direct proof is unavailable, leave the attribution unresolved and report the limitation.

Keep personal data to the minimum needed for the audit. LinkedIn's Privacy Policy states that it collects data when members communicate through its services, including messages and connection requests. Do not copy unnecessary private message content into a recovery ledger.