What naming convention survives a network of fifty accounts?

Use stable internal identifiers and readable labels with the dimensions the team actually needs, such as client, market and content role. Avoid making a mutable public handle the only key that connects assets, schedules and reports.

Keep the visible naming simple enough for humans to check. A long code nobody understands can be as error-prone as “account two.” Document the convention and the mapping to real platform identities, then use the same mapping across production and analytics.