A LinkedIn Company Page Post Lost Its Page-Identity Link: Freeze Account Attribution

A missing Page identity link is an attribution failure first. Treat it that way. Do not publish a replacement post or move comments to a new record. Do not let a campaign guess which Company Page owns the retained public post.

The retained post is the anchor. LinkedIn documents that a post has an author field, and that author can be an organization URN for a Company Page post. Retrieve the retained post by its post URN, capture the returned author value, and compare it with the intact Company Page record before restoring any local relationship. LinkedIn Post API schema lists the author field and organization author type.

This is slower than making a fresh post. That is the right tradeoff. A fresh post creates a second public object and splits the history you are trying to preserve.

Which Company Page owns the retained public post?

Start from the retained post URN, not the Page name shown in a dashboard. LinkedIn documents retrieval by share or UGC post URN, with URL encoding required for URNs in request parameters. Save the returned post ID, author URN, lifecycle state, published time when available plus commentary and attached content identifiers in a recovery record. LinkedIn Posts API documents post retrieval and the post identifiers it accepts.

An organization URN has the form `urn:li:organization:{organization id}` and represents a LinkedIn Company Page. Resolve the organization ID only after the post response provides the author URN. The Organization Lookup API can retrieve the organization record, including its ID and name, subject to the authenticated member's access.

Use access control as a separate check. LinkedIn documents that organization posting and retrieval permissions are limited to specified Company Page roles. A failed authorization check does not prove that another Page owns the post. It proves that the current authenticated member cannot complete that API operation.

• Record the retained post URN exactly as retrieved.
• Record the post author URN exactly as retrieved.
• Resolve the author organization record and retain its returned ID and name.
• Record the authenticated member's approved role or the authorization failure.
• Hold the recovery for review if the post author conflicts with the Page record or prior attribution evidence.

What should be frozen while the Page link is detached?

Freeze writes that could create a second attribution path. The goal is to stop new records from attaching to an unverified Page, not to delete the retained post or its existing history.

Keep read-only evidence available. LinkedIn Page content analytics can expose engagement details by individual post, including post details and engagement metrics, including impressions, clicks, reactions, comments, and reposts. LinkedIn notes that some metrics can take up to 48 hours to appear, while reactions and comments reflect in real time. Treat that timing difference as a reporting caveat during recovery. LinkedIn Help describes the Page content analytics fields and timing.

• Pause automatic comment routing for the detached post.
• Pause account attribution writes tied to the old Page edge.
• Pause campaign actions that select this post through Page ownership.
• Mark affected reporting rows as pending attribution rather than moving them.
• Preserve existing comment, campaign, and reporting record IDs for reconciliation.

What belongs in the Company Page-post recovery ledger?

Make the ledger the one place where a reviewer can trace the retained post to the restored Page edge. It must separate evidence from assumptions. If prior-link proof is missing, label it missing. Do not fill the gap with a Page name match.

Use a stable content hash only as a duplicate test. It can show that two records carry the same stored post content, but it cannot establish Company Page ownership on its own. The returned author URN is the ownership evidence in this recovery.

How do you restore the relationship without duplicating history?

Restore the internal post-to-Page relationship, not the public post. The write should point the already-retained local post record to the verified organization record. Do not create a new LinkedIn post to make a dashboard look complete.

LinkedIn's documented post creation flow returns a new post ID in the response header. That is exactly why post creation is the wrong recovery action when a public post already exists: it creates another object instead of repairing the attribution record around the retained object. LinkedIn Posts API documents post creation and the returned post ID.

After the single edge write, reconcile dependents by their existing IDs. Re-enable a comment-routing record only when it still points to the retained post ID. Re-enable campaign and reporting records only when their post and Page IDs plus the restored edge all match the ledger.

• Create one recovery record and lock it to the retained post ID.
• Write one verified post-to-Page relationship in the internal attribution system.
• Do not create, reshare, or substitute a LinkedIn post during the repair.
• Reattach dependent records to the retained post only when their stored IDs match.
• Keep conflicting rows in review status until a reviewer resolves the conflict.

Which duplicate tests must pass before attribution resumes?

Run duplicate tests against identifiers, not display text. The post URN must map to one active internal Page relationship. The verified organization URN must map to the intended Page record. A title or other display text is supporting context, not a unique key.

Check touch history separately. The retained post's comments plus routing, attribution, campaign, and reporting records should remain attached to the same retained post ID. A new row is acceptable only when it is an explicit recovery audit event, not a replacement engagement record.

If a duplicate public post exists, leave both public objects unchanged while a reviewer decides the customer-facing response. Do not merge or delete records based on matching text alone.

• One active internal Page edge for the retained post URN.
• One verified organization URN for the restored Page record.
• No second post created during the recovery window.
• No duplicate comment-routing job for the retained post.
• No duplicate campaign attribution or reporting row for the same retained post and measurement period.