Why do posts show up under a different profile than expected?

PostSnag attributes every post you capture to the exact Facebook page you were viewing when you scrolled it, so a post that looks like it belongs somewhere else is almost always explained by what was actually on screen at the time, not by PostSnag mixing up two profiles.

Three things commonly cause this: a shared or tagged post appearing on someone's own feed, capturing a person's posts from inside a Facebook Group instead of from their profile directly, and a person or brand running both a personal profile and a separate Page.

Why this happens

Shared and tagged content shows up on a profile's own feed. A profile's feed doesn't only contain posts that person or Page originally wrote. Facebook also displays posts they've shared from someone else, and posts where they've been tagged, right in their own feed. When you scroll that profile, PostSnag captures the feed exactly as Facebook shows it, so a shared or tagged post gets attributed to whichever profile's page you were on, the same as any other post there.

Capturing from inside a Group tags posts to that Group, not to the person. Opening a member's profile from inside a Facebook Group, rather than opening their profile directly, still captures their posts, but PostSnag keeps that capture tagged to the Group. Their personal profile, viewed on its own, shows only their non-group posts. This is intentional, so someone's personal totals don't get combined with their Group activity, but it means the same person can show up as two separate entries in your dashboard: their profile, and their posts inside a specific Group.

A profile and a Page are two different captures, even for the same person or brand. PostSnag treats each Facebook URL you scan as its own profile record. If someone runs both a personal profile and a business Page, or you land on facebook.com/username one time and facebook.com/profile.php?id=... another, those are captured and stored separately. Posts from one never merge into the other automatically.

[Screenshot: A shared post appearing inside a profile's own feed, shown next to how it's labeled once captured]

What to do

1. Check whether the post was originally shared or tagged. A shared post usually still shows its original source in the caption or attached preview. That's the quickest way to tell it apart from a profile's own writing when you're reviewing captures later.

2. Look in the right place for Group captures. If you captured someone's posts while browsing from inside a Group, find them under that Group in your dashboard rather than under their personal profile. Open their profile directly if you want their personal posts tracked on their own.

3. Confirm which URL you're actually on. Before scanning, check whether you're on a personal profile or a Page, especially for a person or brand that runs both. Scan each one separately if you want both captured.

4. Re-scan from the source you actually want. If a post landed somewhere you didn't intend, scanning directly from the profile, Page, or Group you meant to capture gives PostSnag a clean read going forward.

Getting clean attribution next time

Scan a profile, Page, or Group directly from its own page rather than from a shared link, a tag notification, or someone else's feed. If you're specifically after a person's personal posting history, open their profile directly instead of reaching it through a Group they're a member of; the two are kept separate on purpose.

Common questions

Is this a mistake in what PostSnag captured?
No. PostSnag captured exactly what was showing on the page you scrolled, including any shared, tagged, or Group-context content Facebook displayed there.

Can I move a captured post from one profile to another afterward?
Not currently. There's no manual reassign option. If a post landed in the wrong place, the fix is to scan it again from the source you actually want.

Why do a person's Page and personal profile show up as two separate entries?
Because PostSnag treats each Facebook URL as its own profile record. A shared name or brand doesn't merge them; the underlying page does.

Does this happen on Pages too, or only personal profiles?
Either. Any profile or Page feed that shows shared or tagged content will have that content captured along with everything else on that feed.

How is this different from a Group post staying separate from someone's profile?
That's the same underlying idea applied to Groups specifically: PostSnag keeps a Group's captured posts apart from a person's personal profile posts, even when both involve the same person.