This article explains how product-level and track-level genres function within the FUGA Interface. You will learn how to configure fixed primary genres, custom subgenres, and alternate genres, as well as how store-specific metadata rules apply to platforms such as Apple Music and Beatport during delivery.
Overview of Genre Fields
Genres can be set at both the product level and the asset (track) level. Providing accurate genre metadata ensures proper distribution and correct mapping across Digital Service Providers (DSPs).
The FUGA Interface includes four main genre fields:
Genre: A fixed, non-editable drop-down field containing broad main genres accepted across all delivery feeds.
Subgenre: An editable text field where custom or specific genre descriptions can be entered.
Alternate Genre: A fixed drop-down field used to specify a secondary broad genre if applicable.
Alternate Subgenre: An editable text field used to specify a secondary custom genre.
Setting Product and Asset Genres
To set genres at the product level:
Navigate to Catalog > Products.
Select the product you want to update.
Scroll down to the Genre section of the product.
Select your primary genre from the drop-down list in the Genre field.
(Optional) Enter a specific genre in the Subgenre field.
To set genres at the asset level:
Navigate to Catalog > Products.
Select the product containing the asset you want to update.
Select the specific track.
Scroll down to the Genre section of the asset.
Select your primary genre from the drop-down list in the Genre field.
(Optional) Enter a specific genre in the Subgenre field.
Available Main Genres
The Genre field contains a fixed list of options to ensure every product is delivered with an accepted primary classification. You cannot add new main genres to this drop-down list.
The available fixed main genres are:
Alternative
Audiobooks
Blues
Children's Music
Classical
Comedy
Country
Dance
Electronic
Folk
Hip Hop/Rap
Holiday
Inspirational
Jazz
Latin
New Age
Opera
Pop
R&B/Soul
Reggae
Rock
Spoken Word
Soundtrack
Vocal
World
Custom Subgenre Guidelines
While the Subgenre and Alternate Subgenre fields are free-text with no strict character limits or forbidden characters, it is strongly recommended to enter terms that match established genre categories on your target DSPs. Matching standard DSP genre terminology helps prevent mapping errors or automatic reclassification during ingestion.
DSP-Specific Genre Rules
Certain DSPs enforce specific automated logic or curation policies regarding genres:
Apple Music: FUGA delivers track-level genres for current Apple deliveries. If the majority of tracks on a release are tagged with the "Classical" genre, Apple Music may automatically apply the "Classical" genre to the entire product. This occurs regardless of the original product-level genre setting and will trigger stricter Classical metadata validation rules across the release. For a complete list of recognized genres, refer to the article Music Genres and Categories on Apple Music.
Beatport: Beatport takes delivered genres into consideration during ingestion. However, final genre allocation rests with the Beatport curation team. Beatport remains open to adjusting genres upon request if their curation team agrees with the change request. For a complete list of recognized categories, refer to the article Beatport Genres.
If you encounter unexpected genre classification issues after delivery, contact your FUGA representative or reach out via our support channel.