Skip to main content

Creating and Delivering Ringtone Products

  • Updated

This article explains how to properly deliver ringtones within the FUGA Interface. You will learn the technical requirements for ringtone assets, how to configure them as mobile products, and the specific metadata guidelines required by Digital Service Providers (DSPs) to ensure successful ingestion and delivery. Following these standards prevents technical errors and ensures your content is accepted by all supported partners.

Technical Specifications

Ringtones (or mobile products) have specific technical constraints that differ from standard audio tracks. Before starting the ingestion process, ensure your assets meet the following criteria:

  • File Format: Assets must be provided as .wav files.

  • Duration: The audio must be a minimum of 5 seconds and a maximum of 29 seconds.

  • Unique Identifiers: Each ringtone requires a unique Universal Product Code (UPC) or European Article Number (EAN), a unique International Standard Recording Code (ISRC), and a unique Catalog number. These identifiers are mandatory for all products and must not be reused from the original full-length track or any other release.

     

Creating a Ringtone Product

Ringtones must be delivered as standalone products rather than regular music products. To create a ringtone in the FUGA Interface, follow these steps:

  1. Navigate to Catalog > Products and select Add Product.

  2. In the Create new product window, locate and enable the toggle for Mobile product for ringtones.

  3. Set the product type to Single. Note: Ringtones must be delivered as one-track singles; you cannot deliver multiple ringtones within a single product.

  4. When adding the asset, the system will automatically set the asset type to Ringtone. This setting is locked once the audio is uploaded.

  5. Upload your .wav file and enter the required unique metadata identifiers.

     

Metadata Restrictions

DSPs have strict rules regarding the use of descriptive language in ringtone metadata to prevent poor user experiences in mobile stores. To avoid delivery rejections, ensure that album titles, artist names, or track titles do not include generic terms such as:

  • Tone

  • Alert Tone

  • Text Tone

  • Ringtone

  • Ringtone Version

For example, a track should be titled "Song Title," not "Song Title (Ringtone Version)."

If you require further assistance with ringtone configuration, please contact your FUGA representative or reach out via our support channel.

Related articles