Track Social Accounts Across Platforms Using IDs

Track social accounts by recording each platform's permanent numeric or alphanumeric ID alongside the handle, and treat the ID as the authoritative column. Handles change and can be reassigned to other people; IDs cannot. One sheet, one row per account, with an ID column captured at the moment you first add the account, survives every rename and rebrand your list will encounter.

Why handle-based tracking fails quietly

Anyone who has maintained a list of creators, competitors, partners or monitored accounts for more than a year has met the same problem. The list stops matching reality, and it does so without producing a single error.

Three things happen. Accounts rename, so the handle in your sheet no longer finds them and you assume the account is gone. Released handles get claimed by someone else, so your stored link opens a valid profile belonging to a stranger, and nothing flags it. And the same account enters your list twice under two handles at two different times, so you double-count its metrics and contact it twice.

The third failure is the most expensive because it corrupts analysis rather than just inconveniencing you. A quarterly report that joins two periods on handle will silently split one account into two and merge two into one. The numbers look fine. They are wrong. The architectural reason this is unavoidable is set out in why usernames change but user IDs never do, but the practical consequence is enough to act on.

What a persistent identifier is in this context

A persistent identifier is the value a platform assigns to an account at creation and never alters, as distinct from the handle, which the account holder controls. Every major platform issues one, though the formats and names differ: Facebook uses a numeric UID for profiles and a numeric Page ID for Pages, Instagram a numeric user ID sometimes called the pk, TikTok a numeric user ID, YouTube an alphanumeric channel ID beginning with UC, and X a numeric user ID. The guarantee attached to all of them is identical. The value identifies that account for as long as it exists, through every rename, rebrand, avatar change and ownership transfer. What it does not survive is deletion and recreation, since that produces a genuinely new account with a new ID. For tracking purposes that limitation is a feature: if an ID stops resolving, you know the account itself is gone rather than merely renamed.

Identifier formats by platform

The TikTok row carries the trap that catches the most people. A TikTok user ID and a sec_uid are two different values, and someone who records one in a column labelled for the other will produce failures later that look like permission errors rather than data errors. Label the column with the exact identifier name and read TikTok user ID versus sec_uid before you start. The Facebook rows carry the second trap: a Page ID and a profile UID look identical and behave completely differently, as covered in Facebook ID vs Page ID vs Group ID.

Structuring the sheet

You do not need a database for this. A spreadsheet does the job provided it has the right columns, and the right columns are mostly about recording what you knew and when you knew it.

Start with an internal key of your own, a simple incrementing number, so that the same organisation or person appearing on five platforms can be grouped without relying on any platform's values. Then one row per account, carrying the platform name, the persistent ID stored as text, the identifier type spelled out exactly, the handle as of the last check, the display name, the profile URL, and the date you captured the ID.

Two of those choices are worth defending. Store IDs as text, not numbers: spreadsheet software will happily reformat a long numeric ID into scientific notation or truncate its final digits, and you will not notice until the data is unusable. Format the column as plain text before you paste anything into it. And record the capture date, because the handle in your sheet is a snapshot with an age, and knowing that age tells you whether to trust it.

Beyond that, add whatever your work needs: an owner column, a status column, a notes column, a date of last contact. Keep the ID column read-only in practice. It should never be edited after capture, because editing it means you are now describing a different account.

The workflow, step by step

1. Capture the ID at intake. The moment an account enters your list, resolve its ID and record it. Doing this later is harder, because by then the handle may already have changed and you may not be able to find the account at all.
2. Record which identifier you captured. Write the exact type, such as "Instagram user ID" or "TikTok user ID", not a generic word like "ID". This single habit prevents the TikTok and Facebook confusions described above.
3. Store the ID-based URL where one exists. Facebook's profile.php?id= form and YouTube's /channel/UC... form both resolve by ID and keep working through renames. Keep the handle-based URL too, for readability, but know which of the two is reliable.
4. Link the rows that belong together. Group an organisation's accounts under your own internal key so cross-platform reporting does not depend on matching names.
5. Re-verify on a schedule and on triggers. Covered in the next section.
6. Never overwrite history. When a handle changes, move the old one to a previous-handles column rather than deleting it. Old handles explain stale links you will encounter later, and on monitoring work they are evidence.

When to re-verify

Re-verification means loading the account by its ID, confirming it still resolves, and updating the handle and display name if they have moved. How often depends on what the list is for, and there is no universal interval worth quoting as a rule. Set the cadence by consequence: a list that drives payments or published links needs checking more often than a loose watchlist.

More useful than a calendar is a set of triggers. Re-verify when a link in your own published content stops working, when outreach bounces or goes unanswered against an account that used to respond, when a report shows an account's metrics dropping to zero abruptly, when you are about to publish anything containing profile links, and before any contractual or financial step involving the account. Each of those is a signal that the handle you hold may no longer match reality.

One check deserves special mention. Before you publish a page, a media kit or a newsletter that links to external profiles, load every link. A link that now resolves to a stranger's account is a worse outcome than a dead link, and it is the specific failure that handle-based records produce.

Cross-platform grouping and its limits

The appeal of an ID-keyed sheet is that it finally lets you say "these six accounts are the same organisation" with confidence. Worth being clear about what the IDs do and do not give you there.

Platform IDs are platform-specific. There is no shared identifier across platforms, and no technical way to prove that an Instagram account and a TikTok account belong to the same person. The grouping is your editorial judgement, based on evidence such as reciprocal links between the accounts, a link from the organisation's own website, consistent branding and matching contact details. Record the basis for the grouping in a notes column, because a future reader, possibly you, will want to know why those rows were joined. The signal-weighing approach in how to check whether a social media account is real applies directly.

Two further limits. IDs tell you nothing about content, reach or authenticity; they are an addressing mechanism, nothing more. And if your list contains IDs tied to individuals rather than businesses, you are holding personal data, and the data protection rules of your jurisdiction apply to how you store it, how long you keep it and what you use it for. Keep the list no larger and no longer than your purpose requires.

Where to get the IDs

If you have API access to a platform, that is the authoritative route and it scales. Meta's Graph API covers Facebook and Instagram business accounts, and Google documents the YouTube Data API separately.

For ad-hoc lookups from a public profile URL, 2uid.net resolves them without a login or an API key: the Facebook UID Finder for profiles and Pages, plus Instagram, TikTok, YouTube and X. Platform-specific walkthroughs are in finding an Instagram user ID, finding a YouTube channel ID, finding a Facebook Page ID and X user IDs explained. If you want the conceptual grounding before building anything, start with the pillar piece on social media user IDs.

One boundary to respect throughout. All of this works on metadata the platforms publish for public accounts. Nothing here, and no legitimate tool, reads private content, hidden follower lists or anything behind a login, and services advertising those capabilities are either ineffective or breaking platform terms. About 2uid.net and our privacy page set out what the tools do with what you submit.

Frequently asked questions

Do I really need the ID if I already have the profile URL?

Yes, because a handle-based profile URL is only valid while the handle is. If the account renames, your URL fails; if the handle is reassigned, it resolves to someone else. The ID identifies the account regardless, and on Facebook and YouTube you can build an ID-based URL that keeps working.

How often should I re-check a tracking list?

Set the frequency by what the list is used for rather than by a fixed interval. Lists that drive payments, published links or reporting need frequent checks; casual watchlists need few. Pair the schedule with triggers: broken links, bounced outreach, metrics dropping to zero, or any publication or contract involving the account.

Why do long IDs break in my spreadsheet?

Because the software treats them as numbers and reformats them into scientific notation or drops trailing digits. Format the ID column as plain text before pasting anything into it, and verify after import that the values still match the source character for character.

Can one identifier work across several platforms?

No. Each platform runs its own identifier space, and there is no cross-platform ID. Group accounts under an internal key of your own and record the evidence that justified the grouping, such as reciprocal links or a link from the organisation's own website.

What happens when an account is deleted?

The ID stops resolving, which is useful information: it distinguishes deletion from a rename, where the ID would still resolve under a new handle. Keep the row and mark it inactive rather than deleting it, so historic reports that reference the account still make sense.

Is a Page ID the same as a Facebook UID?

No. A Page ID identifies a Page and a UID identifies a personal profile. They are both long numeric strings and look identical, but they belong to different object types in Meta's data model and cannot be substituted for one another. Label which one each row holds.

Should I record the TikTok sec_uid as well as the user ID?

Record whichever your workflow actually needs, in a column named for that exact identifier. The two are different values with different purposes, so keeping them in separate, clearly labelled columns avoids the most common TikTok data mistake. Never put one in a column meant for the other.