← Back to all updatesQ3 2026Released 11 August 2026
⭐ New featureCreate and manage your own tags
Three custom tag types are now available in FXPLATFORM. Create them, manage them and apply them to content directly — no request to Funxtion, no development work, no waiting on a release cycle.
What's included
•Three custom tag types: Personal Trainer, Brand (shown as Vendor in FXPLATFORM) and Category
•Create, edit and manage custom tags directly in FXPLATFORM
•Apply custom tags to your content as part of the normal editing flow
•Up to 10 custom tags per label type
•Custom categories sit inline in the existing Category list, alongside the standard ones
How to access: Available to content admin users in FXPLATFORM
⭐ New featureFilters that follow your content
Custom tags become filters in the member app. Filters are dynamic — one only appears when there is content behind it, so members never open a filter that returns nothing.
What's included
•Workouts — Brand and Instructor filters added, and the Types filter is now Category
•Training Plans — Brand and Instructor filters added
•Virtual Classes — no change needed; Brand and Instructor are already present and are reused for custom tags
•Dynamic by default — a filter appears only when there is data behind it, and is hidden entirely when there isn’t
•The Brand filter covers every vendor in your library, including integration partners, in a single list
•The Types to Category rename is applied across all whitelabel apps, with no configuration required
How to access: Live across whitelabel apps once custom tags are applied to content
For developersTag metadata endpoints
Custom tags are exposed through the REST API so you can build tag metadata into your own interface — populating a filter list with your own trainers or brands, or showing the vendor and instructor on a content card.
Personal Trainers—POST | GET /v3/content/fitness/instructors
Vendors / Brands—POST | GET /v3/content/fitness/content-providers
Categories—POST | GET /v3/content/categories
Choosing what comes back
•filter[where][custom] is optional and tri-state — omit the key for everything, =true for entries you created, =false for seeded and global entries
•Integration brands are seeded globally, so their custom value is false
•For highlighted integration brands specifically, use featured rather than custom — it returns only integration brands that have published content, and tenant-created brands are never featured
•The collections array on a provider tells you which content types that brand currently has published content in — drive your entry points from it rather than hardcoding, so new content types appear automatically
ScopeCustom Tagging delivers filtering and discoverability. Tags do not automatically appear on content cards in the app — surfacing a trainer name, brand or category on a card is front-end work in your own application, using the endpoints above.