Loco tags help you organise your translatable assets
Tags are applied at asset level. This means a tag applies to all language versions of the same item. Note how this differs from flags, which are applied to individual translations.
Filtering dashboard views
If you were localizing a website, you might create a tag called "Buttons" or a tag called "Home page". You could then filter your dashboard view to show only button assets or only assets that live on the home page. This is especially useful if your project contains thousands of assets.
Filtering exports
Filtering language packs by tag can be done to export subsets of your project into separate files.
For example: if you tagged your assets as either "PHP" or "JavaScript" you could export separate PHP and JSON files from the same project containing only the assets they need.
Via the export API you can negate tags by prefixing "!" to the name. e.g. filtering on "!PHP" would produce all assets without this tag.
Allowed tag names
You can use any name up to 50 characters, with the exception of being all digits or beginning with the "!" character (exclamation mark).
You could tag assets with a version number like "v1" or "1.0", but "1" would be disallowed.
Loco avoids duplicate tag confusion by treating them as case insensitive. If you create "foo", you cannot also create "Foo". Spaces and punctuation are treated similarly. If you create "foo bar", you cannot also create "foo, bar" because it is too similar.
When querying the API, you may use these small differences interchangeably, but as a general rule we recommend you always present your original tag name to the API.