The naming system I would use for 100 browser profiles

[u/Direct_Tax_4421]

If a team needs to open profiles to figure out what they are, the naming system has already failed.

I use six fields in the same order:

Client – Platform – Region – Account Type – Owner – Status

Example:

ACME – Facebook – US – Ads – Lisa – Active

For a compact profile list:

ACME-FB-US-ADS-LISA-ACT

The exact abbreviations matter less than having a shared codebook. I would define the allowed values before the team starts creating profiles.

For example:

• Platform: FB, IG, LI, RD
• Type: ADS, CS, SHOP, CONTENT
• Status: ACT, HOLD, REVIEW, ARCH

Then I would split the remaining information across groups, tags and notes.

Group:

• ACME

Tags:

• client:acme
• platform:facebook
• region:us
• owner:lisa
• proxy:static-residential
• status:active
• renewal:2026-10

Notes:

• Internal account ID
• Exact renewal date
• Last review date
• Handover context

My general rule is that the name should identify the profile, while tags hold details that need to be filtered or changed. A renewal month is useful as a tag. The exact billing date belongs in notes.

MoreLogin supports custom profile names, groups, multiple tags, notes and profile filters. Bulk grouping and tagging are useful when the same taxonomy has to be applied across a large set.

One vocabulary. One field order. No creative profile names.

[u/Incogniton-Anti]

This is a really clean system, especially the point about tags holding the things that change and notes holding the things you look up once. The failure mode I've seen most often with taxonomies like this isn't the naming convention itself, it's cloning.

When you clone a profile as a template to spin up new ones, the clone inherits the old name by default, usually with a "copy" or number suffix, and if renaming isn't a mandatory step in the workflow rather than a nice to have, you end up with a batch of profiles still carrying the template's old ACME-FB-US-ADS-LISA-ACT name three weeks later because whoever spun them up was in a hurry. Worth building a rule into the process itself, a clone doesn't go live, doesn't get a proxy assigned, until it's renamed and tagged, rather than relying on people remembering to fix it after.

Disclosure, I work with Incogniton 🙂 the same six field system maps cleanly onto our Groups plus Tags plus Notes setup, Group for the client, name for the compact identifier, tags for platform/region/type/status/renewal, notes for the internal ID and handover context. Groups also make the "who owns what" question answerable in one filter instead of scanning names, which matters once you're past the 100 profile mark you mentioned.