How many paid subscribers does Spotify have? As of the fourth quarter of 2024, Spotify had 263 million premium subscribers worldwide, up from 236 million in the corresponding quarter of 2023. Spotify’s subscriber base has increased dramatically in the last few years and has more than doubled since early 2019. Spotify and competitors Spotify is a music streaming service originally founded in 2006 in Sweden. The platform can be used from various devices and allows users to browse through a catalogue of music licensed through multiple record labels, as well as creating and sharing playlists with other users. Additionally, listeners are able to enjoy music for free with advertisements or are also given the option to purchase a subscription to allow for unlimited ad-free music streaming. Spotify’s largest competitors are Pandora, a company that offers a similar service and remains popular in the United States, and Apple Music, which was launched in 2015. While Pandora was once among the highest-grossing music apps in the Apple App Store, recent rankings show that global services like QQ Music, NetEase Cloud Music, and YouTube Music now generate higher monthly revenues.Users are also able to register Spotify accounts using Facebook directly through the website using an app. This enables them to connect with other Facebook friends and explore their music tastes and playlists. Spotify is a popular source for keeping up-to-date with music, and the ability to enjoy Spotify anywhere at any time allows consumers to shape their music consumption around their lifestyles and preferences.

In the fourth quarter of 2024, the music streaming service Spotify reached an all-time high with 675 million active users worldwide. This marked an increase of around 12 percent in just one year. What is Spotify? Spotify is a music streaming service that offers digital audio content. Basic audio content can be accessed for free whereas premium user subscriptions enable users to access offline mobile content as well as listen to music without advertising. In the fourth quarter of 2024, the company reported 263 million paying subscribers. Launched in 2008, Spotify originated in Sweden before expanding to European markets and the United States in 2011. Spotify’s U.S. launch was strongly marketed through Facebook, with the music streaming app profiting from the social listening integration via social media. Part of Spotify’s appeal can be attributed to the user- and brand-curated playlists, which can be shared publicly or between friends. Fans may choose what to listen to based on their current mood or preference, and the ability to share such content provides an element of social connectivity ordinarily reserved for networking sites.

This dataset was created using Spotify developer API. It consists of user-created as well as Spotify-curated playlists.
The dataset consists of 1 million playlists, 3 million unique tracks, 3 million unique albums, and 1.3 million artists.
The data is stored in a SQL database, with the primary entities being songs, albums, artists, and playlists.
Each of the aforementioned entities are represented by unique IDs (Spotify URI).
Data is stored into following tables:

• album
• artist
• track
• playlist
• track_artist1
• track_playlist1

album

| id | name | uri |

id: Album ID as provided by Spotify
name: Album Name as provided by Spotify
uri: Album URI as provided by Spotify

artist

| id | name | uri |

id: Artist ID as provided by Spotify
name: Artist Name as provided by Spotify
uri: Artist URI as provided by Spotify

track

| id | name | duration | popularity | explicit | preview_url | uri | album_id |

id: Track ID as provided by Spotify
name: Track Name as provided by Spotify
duration: Track Duration (in milliseconds) as provided by Spotify
popularity: Track Popularity as provided by Spotify
explicit: Whether the track has explicit lyrics or not. (true or false)
preview_url: A link to a 30 second preview (MP3 format) of the track. Can be null
uri: Track Uri as provided by Spotify
album_id: Album Id to which the track belongs

playlist

| id | name | followers | uri | total_tracks |

id: Playlist ID as provided by Spotify
name: Playlist Name as provided by Spotify
followers: Playlist Followers as provided by Spotify
uri: Playlist Uri as provided by Spotify
total_tracks: Total number of tracks in the playlist.

track_artist1

| track_id | artist_id |

Track-Artist association table

track_playlist1

| track_id | playlist_id |

Track-Playlist association table

- - - - - SETUP - - - - -

The data is in the form of a SQL dump. The download size is about 10 GB, and the database populated from it comes out to about 35GB.

spotifydbdumpschemashare.sql contains the schema for the database (for reference):
spotifydbdumpshare.sql is the actual data dump.

Setup steps:
1. Create database

- - - - - PAPER - - - - -

The description of this dataset can be found in the following paper:

Papreja P., Venkateswara H., Panchanathan S. (2020) Representation, Exploration and Recommendation of Playlists. In: Cellier P., Driessens K. (eds) Machine Learning and Knowledge Discovery in Databases. ECML PKDD 2019. Communications in Computer and Information Science, vol 1168. Springer, Cham

As of January 2025, Spotify has over 640 million monthly active users. Here is the full breakdown of Spotify users by year since 2015:

The latest Spotify statistics from the company’s annual report show that 69% of Spotify premium subscribers are located in Europe and North America.

Spotify Million Playlist Dataset Challenge

Summary

The Spotify Million Playlist Dataset Challenge consists of a dataset and evaluation to enable research in music recommendations. It is a continuation of the RecSys Challenge 2018, which ran from January to July 2018. The dataset contains 1,000,000 playlists, including playlist titles and track titles, created by users on the Spotify platform between January 2010 and October 2017. The evaluation task is automatic playlist continuation: given a seed playlist title and/or initial set of tracks in a playlist, to predict the subsequent tracks in that playlist. This is an open-ended challenge intended to encourage research in music recommendations, and no prizes will be awarded (other than bragging rights).

Background

Playlists like Today’s Top Hits and RapCaviar have millions of loyal followers, while Discover Weekly and Daily Mix are just a couple of our personalized playlists made especially to match your unique musical tastes.

Our users love playlists too. In fact, the Digital Music Alliance, in their 2018 Annual Music Report, state that 54% of consumers say that playlists are replacing albums in their listening habits.

But our users don’t love just listening to playlists, they also love creating them. To date, over 4 billion playlists have been created and shared by Spotify users. People create playlists for all sorts of reasons: some playlists group together music categorically (e.g., by genre, artist, year, or city), by mood, theme, or occasion (e.g., romantic, sad, holiday), or for a particular purpose (e.g., focus, workout). Some playlists are even made to land a dream job, or to send a message to someone special.

The other thing we love here at Spotify is playlist research. By learning from the playlists that people create, we can learn all sorts of things about the deep relationship between people and music. Why do certain songs go together? What is the difference between “Beach Vibes” and “Forest Vibes”? And what words do people use to describe which playlists?

By learning more about nature of playlists, we may also be able to suggest other tracks that a listener would enjoy in the context of a given playlist. This can make playlist creation easier, and ultimately help people find more of the music they love.

Dataset

To enable this type of research at scale, in 2018 we sponsored the RecSys Challenge 2018, which introduced the Million Playlist Dataset (MPD) to the research community. Sampled from the over 4 billion public playlists on Spotify, this dataset of 1 million playlists consist of over 2 million unique tracks by nearly 300,000 artists, and represents the largest public dataset of music playlists in the world. The dataset includes public playlists created by US Spotify users between January 2010 and November 2017. The challenge ran from January to July 2018, and received 1,467 submissions from 410 teams. A summary of the challenge and the top scoring submissions was published in the ACM Transactions on Intelligent Systems and Technology.

In September 2020, we re-released the dataset as an open-ended challenge on AIcrowd.com. The dataset can now be downloaded by registered participants from the Resources page.

Each playlist in the MPD contains a playlist title, the track list (including track IDs and metadata), and other metadata fields (last edit time, number of playlist edits, and more). All data is anonymized to protect user privacy. Playlists are sampled with some randomization, are manually filtered for playlist quality and to remove offensive content, and have some dithering and fictitious tracks added to them. As such, the dataset is not representative of the true distribution of playlists on the Spotify platform, and must not be interpreted as such in any research or analysis performed on the dataset.

Dataset Contains

1000 examples of each scenario:

Title only (no tracks) Title and first track Title and first 5 tracks First 5 tracks only Title and first 10 tracks First 10 tracks only Title and first 25 tracks Title and 25 random tracks Title and first 100 tracks Title and 100 random tracks

Download Link

Full Details: https://www.aicrowd.com/challenges/spotify-million-playlist-dataset-challenge Download Link: https://www.aicrowd.com/challenges/spotify-million-playlist-dataset-challenge/dataset_files

Content

This is a dataset of Spotify tracks over a range of 125 different genres. Each track has some audio features associated with it. The data is in CSV format which is tabular and can be loaded quickly.

  Usage

The dataset can be used for:

Building a Recommendation System based on some user input or preference Classification purposes based on audio features and available genres Any other application that you can think of. Feel free to discuss!

  Column… See the full description on the dataset page: https://huggingface.co/datasets/maharshipandya/spotify-tracks-dataset.

1) Data Introduction • The Spotify Playlist-ORIGINS Dataset is a dataset of Spotify playlists called ORIGINS, which individuals have made with their favorite songs since 2014.

2) Data Utilization (1) Spotify Playlist-ORIGINS Dataset has characteristics that: • This dataset contains detailed music information for each playlist, including song name, artist, album, genre, release year, track ID, and structured metadata such as name, description, and song order for each playlist. (2) Spotify Playlist-ORIGINS Dataset can be used to: • Playlist-based music recommendation and user preference analysis: It can be used to develop a machine learning/deep learning-based music recommendation system or to study user preference analysis using playlist and song information. • Music Trend and Genre Popularity Analysis: It analyzes release year, genre, and artist data and can be used to study the music industry and culture, including music trends by period and genre, and changes in popular artists and songs.

34% of Spotify’s monthly active users live in Europe. That means that Spotify has 147.22 million users in the EU regions alone. Here’s the breakdown of regions that contribute the most users to Spotify:

Analysis of ‘K-Pop Hits Through The Years’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://www.kaggle.com/sberj127/kpop-hits-through-the-years on 28 January 2022.

--- Dataset description provided by original source is as follows ---

What is the data?

The datasets contain the top songs from the said era or year accordingly (as presented in the name of each dataset). Note that only the KPopHits90s dataset represents an era (1989-2001). Although there is a lack of easily available and reliable sources to show the actual K-Pop hits per year during the 90s, this era was still included as this time period was when the first generation of K-Pop stars appeared. Each of the other datasets represent a specific year after the 90s.

How was it obtained?

A song is considered to be a K-Pop hit during that era or year if it is included in the annual series of K-Pop Hits playlists, which is created officially by Apple Music. Note that for the dataset that represents the 90s, the playlist 90s K-Pop Essentials was used as the reference.

1. These playlists were transferred into Spotify through the Tune My Music site. After transferring, the site also presented all the missing songs from each Spotify playlist when compared to the original Apple Music playlists.
   • Any data besides the names and artists of the hit songs were not directly obtained from Apple Music since these other details of songs in this music service are only available for those enrolled as members of the Apple Developer Program.
2. The presented missing songs from each playlist was manually searched and, if found, added to the respective Spotify playlist.
   • For the songs that were found, there are three types: (1) the song by the original artist, (2) the instrumental of the original song and (3) a cover of the song. When the first type is not found, the two other types are searched and are compared to each other. The one that sounded the most like the original song (from the Apple Music playlist) is chosen as the substitute in the Spotify playlist.
   • Presented is a link containing all the missing data per playlist (when the initial Spotify playlists were compared to the original Apple Music playlists) and the action done to each one.
3. The necessary identification details and specific audio features of each track were obtained through the use of the Spotipy library and Spotify Web API documentation.

Why did you make this?

As someone who has a particular curiosity to the field of data science and a genuine love for the musicality in the K-Pop scene, this data set was created to make something out of the strong interest I have for these separate subjects.

Acknowledgements

I would like to express my sincere gratitude to Apple Music for creating the annual K-Pop playlists, Spotify for making their API very accessible, Spotipy for making it easier to get the desired data from the Spotify Web API, Tune My Music for automating the process of transferring one's library into another service's library and, of course, all those involved in the making of these songs and artists included in these datasets for creating such high quality music and concepts digestible even for the general public.

--- Original source retains full ownership of the source dataset ---

Did We Solve the Problem? The objective of this analysis was to predict high streaming counts on Spotify and perform a detailed cluster analysis to understand user behavior. Here’s a summary of how we addressed each part of the objective:

Prediction of High Streaming Counts:

Implemented Multiple Models: We utilized several machine learning models including Decision Tree, Random Forest, Gradient Boosting, Support Vector Machine (SVM), and k-Nearest Neighbors (k-NN). Comparison and Evaluation: These models were evaluated based on classification metrics like accuracy, precision, recall, and F1-score. The Gradient Boosting and Random Forest models were found to be the most effective in predicting high streaming counts. Cluster Analysis:

K-means Clustering: We applied K-means clustering to segment users into three clusters based on their listening behavior. Detailed Characterization: Each cluster was analyzed to understand the distinct characteristics, such as average playtime, skip rate, offline usage, and shuffle usage. Visualizations: Histograms and scatter plots were used to visualize the distributions and relationships within each cluster. Results and Insights Effective Models: The Gradient Boosting and Random Forest models provided the highest accuracy and balanced performance for predicting high streaming counts. User Segmentation: The cluster analysis revealed three distinct user segments: Cluster 1: Users with longer playtimes and lower skip rates. Cluster 2: Users with moderate playtimes and skip rates. Cluster 3: Users with shorter playtimes and higher skip rates. These insights can be leveraged for targeted marketing, personalized recommendations, and improving user engagement on Spotify.

Conclusion Yes, we solved the problem. We successfully predicted high streaming counts using effective machine learning models and provided a detailed cluster analysis to understand user behavior. The analysis offers valuable insights for enhancing Spotify’s recommendation system and user experience.

Overview Spotify is one of the largest music streaming service providers, with over 422 million monthly active users, including 182 million paying subscribers, as of March 2022. Some of them don't hesitate to share their experience using this application along with the given rating to denote how satisfied they are with the Application

The way data was collected Scraping Spotify reviews on Google Play Store

Ideas for using this dataset Sentiment analysis What makes the application receive 1-star and 5-star

Original Data Source: Spotify App Reviews

1) Data Introduction • The Spotify Tracks Dataset contains information on tracks from over 125 music genres, including both audio features (e.g., danceability, energy, valence) and metadata (e.g., title, artist, genre).

2) Data Utilization (1) Characteristics of the Spotify Tracks Dataset: • The data is structured in a tabular format at the track level, where each column represents numerical or categorical features based on musical properties. This makes it suitable for recommendation systems, genre classification, and emotion analysis. • It includes multi-dimensional attributes grounded in music theory such as track duration, time signature, energy, loudness, tempo, and speechiness—enabling its use in music classification and clustering tasks.

(2) Applications of the Spotify Tracks Dataset: • Design of Music Recommendation Systems: It can be used to build content-based filtering systems or hybrid recommendation algorithms based on user preferences.

Paying subscribers account for about half of Spotify’s monthly active users. This is the number of paying subscribers by year that Spotify has had since 2015.

Analysis of ‘Spotify Recommendation’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://www.kaggle.com/bricevergnou/spotify-recommendation on 28 January 2022.

--- Dataset description provided by original source is as follows ---

Spotify Recommandation

( You can check how I used this dataset on my github repository )

I am basically a HUGE fan of music ( mostly French rap though with some exceptions but I love music ). And someday , while browsing stuff on Internet , I found the Spotify's API . I knew I had to use it when I found out you could get information like danceability about your favorite songs just with their id's.

https://user-images.githubusercontent.com/86613710/127216769-745ac143-7456-4464-bbe3-adc53872c133.png" alt="image">

Once I saw that , my machine learning instincts forced me to work on this project.

1. Data Collection

1.1 Playlist creation

I collected 100 liked songs and 95 disliked songs

For those I like , I made a playlist of my favorite 100 songs. It is mainly French Rap , sometimes American rap , rock or electro music.

For those I dislike , I collected songs from various kind of music so the model will have a broader view of what I don't like

There is : - 25 metal songs ( Cannibal Corps ) - 20 " I don't like " rap songs ( PNL ) - 25 classical songs - 25 Disco songs

I didn't include any Pop song because I'm kinda neutral about it

1.2 Getting the ID's

1. From the Spotify's API "Get a playlist's Items" , I turned the playlists into json formatted data which cointains the ID and the name of each track ( ids/yes.py and ids/no.py ). NB : on the website , specify "items(track(id,name))" in the fields format , to avoid being overwhelmed by useless data.

2. With a script ( ids/ids_to_data.py ) , I turned the json data into a long string with each ID separated with a comma.

1.3 Getting the statistics

Now I just had to enter the strings into the Spotify API "Get Audio Features from several tracks" and get my data files ( data/good.json and data/dislike.json )

2. Data features

From Spotify's API documentation :

• acousticness : A confidence measure from 0.0 to 1.0 of whether the track is acoustic. 1.0 represents high confidence the track is acoustic.
• danceability : Danceability describes how suitable a track is for dancing based on a combination of musical elements including tempo, rhythm stability, beat strength, and overall regularity. A value of 0.0 is least danceable and 1.0 is most danceable.
• duration_ms : The duration of the track in milliseconds.
• energy : Energy is a measure from 0.0 to 1.0 and represents a perceptual measure of intensity and activity. Typically, energetic tracks feel fast, loud, and noisy. For example, death metal has high energy, while a Bach prelude scores low on the scale. Perceptual features contributing to this attribute include dynamic range, perceived loudness, timbre, onset rate, and general entropy.
• instrumentalness : Predicts whether a track contains no vocals. “Ooh” and “aah” sounds are treated as instrumental in this context. Rap or spoken word tracks are clearly “vocal”. The closer the instrumentalness value is to 1.0, the greater likelihood the track contains no vocal content. Values above 0.5 are intended to represent instrumental tracks, but confidence is higher as the value approaches 1.0.
• key : The key the track is in. Integers map to pitches using standard Pitch Class notation . E.g. 0 = C, 1 = C♯/D♭, 2 = D, and so on.
• liveness : Detects the presence of an audience in the recording. Higher liveness values represent an increased probability that the track was performed live. A value above 0.8 provides strong likelihood that the track is live.
• loudness : The overall loudness of a track in decibels (dB). Loudness values are averaged across the entire track and are useful for comparing relative loudness of tracks. Loudness is the quality of a sound that is the primary psychological correlate of physical strength (amplitude). Values typical range between -60 and 0 db.
• mode : Mode indicates the modality (major or minor) of a track, the type of scale from which its melodic content is derived. Major is represented by 1 and minor is 0.
• speechiness : Speechiness detects the presence of spoken words in a track. The more exclusively speech-like the recording (e.g. talk show, audio book, poetry), the closer to 1.0 the attribute value. Values above 0.66 describe tracks that are probably made entirely of spoken words. Values between 0.33 and 0.66 describe tracks that may contain both music and speech, either in sections or layered, including such cases as rap music. Values below 0.33 most likely represent music and other non-speech-like tracks.
• tempo : The overall estimated tempo of a track in beats per minute (BPM). In musical terminology, tempo is the speed or pace of a given piece and derives directly from the average beat duration.
• time_signature : An estimated overall time signature of a track. The time signature (meter) is a notational convention to specify how many beats are in each bar (or measure).
• valence : A measure from 0.0 to 1.0 describing the musical positiveness conveyed by a track. Tracks with high valence sound more positive (e.g. happy, cheerful, euphoric), while tracks with low valence sound more negative (e.g. sad, depressed, angry).

And the variable that has to be predicted :

• liked : 1 for liked songs , 0 for disliked songs

--- Original source retains full ownership of the source dataset ---

This dataset was extracted from the Spotify platform using the Python library "Spotipy", which allows users to access music data provided via APIs. The dataset collected includes about 1 Million tracks with 19 features between 2000 and 2023. Also, there is a total of 61,445 unique artists and 82 genres in the data.

This clean data has been prepared and utilized for research purposes. Its significance lies in its potential to unravel patterns and predict song popularity prior to its release. This dataset could be used to create various predictive models with machine-learning/deep-learning techniques.

https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F5006553%2F317c91feba2aa097559fd59bf408e944%2Ftable_desc_spot.png?generation=1687699189506270&alt=media" alt="">

Overview

Welcome to the Music Informatics for Radio Across the GlobE (MIRAGE) MetaCorpus. The current (v0.2) development release consists of metadata (e.g., artist name, track title) and musicological features (e.g., instrument list, voice type, tempo) for 1 million events streaming on 10,000 internet radio stations across the globe, with 100 events from each station.

Users who wish to access, interact with, and/or export metadata from the MIRAGE-MetaCorpus may also visit the MIRAGE online dashboard at the following url:

• https://pearl-laboratory.github.io/mirage-mc/

Attribution

The current MIRAGE-MetaCorpus is available under a CC4 license. Users may cite the dataset here:

Sears, David R.W. “Music Informatics for Radio Across the Globe (MIRAGE) Metacorpus -- 2024”. Zenodo, July 19, 2024. https://doi.org/10.5281/zenodo.12786202.

Users accessing the MIRAGE-MetaCorpus using the online dashboard should also cite the following ISMIR paper:

Ngan V.T. Nguyen, Elizabeth A.M. Acosta, Tommy Dang, and David R.W. Sears. "Exploring Internet Radio Across the Globe with the MIRAGE Online Dashboard," in Proceedings of the 25th International Society for Music Information Retrieval Conference (San Francisco, CA, 2024).

Data Sources

This repository of the MIRAGE-MetaCorpus contains 81 metadata variables from the following open-access sources:

• Radio Garden (RG) -- https://radio.garden
• Natural Earth map data set (NE) -- https://www.naturalearthdata.com/
• Internet Radio Station Stream Encoder (SE)
• Annotator Review (AR)
• Monitoring/Matching Algorithm (MA)
• WikiData (WD) -- https://www.wikidata.org
• MusicBrainz (MB) -- https://musicbrainz.org/

Each event also includes attribution metadata from the following commercial sources:

• Spotify (SP) -- https://open.spotify.com/
  • Note that users may examine an additional 19 metadata variables on the MIRAGE online dashboard that were obtained from the Spotify API.
• Musixmatch (MX) -- https://www.musixmatch.com/
• YouTube (YT) -- https://www.youtube.com/
• Genius (GE) -- https://genius.com/
• AZlyrics (AZ) -- https://www.azlyrics.com/

Data Sets

The metadata reflect information about each event's location (e.g., city, country), station (name, format, url), event (id, local time at station, etc.), artist (name, voice type, etc.), and track (e.g., title, year of release, etc.). For that reason, the MIRAGE-MetaCorpus includes the following datasets:

• MIRAGE.csv -- the complete metacorpus (1 million)
• events.csv -- all event-level metadata (1 million)
• tracks.csv -- all track-level metadata (414,886)
• artists.csv -- all artist-level metadata (259,783)
• stations.csv -- all station-level metadata (10,000)
• locations.csv -- all location-level metadata (4,324)

A subset of the MIRAGE-MetaCorpus is also available for events with metadata from online music libraries that reliably matched the event's description in the radio station's stream encoder:

• MIRAGE_reliable.csv (473,850)
• events_reliable.csv (473,850)
• tracks_reliable.csv (204,969)
• artists_reliable.csv (80,005)
• stations_reliable.csv (9,284)
• locations_reliable.csv (4,142)

Contact

If you are a copyright owner for any of the metadata that appears in the MIRAGE-MetaCorpus and would like us to remove your metadata, please contact the developer team at the following email address: miragedashboard@gmail.com

🎵 Spotify Song Preference Dataset

This dataset contains Spotify audio features for 195 songs categorized as liked or disliked by the user. It was created to build and train ML models that can predict user preferences in music based on quantitative audio features.

  📥 Dataset Overview

Total songs: 195 Format: CSV (data.csv) Source: Spotify API Target column: liked (1 = liked, 0 = disliked) Data type: Tabular Licensing: For academic and personal research use (derived from… See the full description on the dataset page: https://huggingface.co/datasets/hardik-0212/My_Dataset.

Context

This dataset consists of 24000 tracks from 30 genres, and is a shrunk version of maharshipandya/spotify-tracks-dataset dataset. All non-heuristic data is cut and cleaned for better usability and performance. All data taken from Spotify API and is open source. This dataset can be used to train prediction models based on user preferences, or categorise tracks by corresponding heuristic.

  Column Description

danceability: Danceability describes how suitable a track is… See the full description on the dataset page: https://huggingface.co/datasets/engels/spotify-tracks-lite.

Spotify Tracks Dataset Description

This dataset contains information on Spotify tracks spanning 125 different genres. Each track is described by various audio features and metadata. The dataset can be utilized for:

• Building recommendation systems based on user preferences or inputs.
• Classification tasks based on audio features and genre categorization.

Columns Description:

• track_id: The unique Spotify ID for each track.
• artists: Names of the artists who performed the track, separated by ';'.
• album_name: The name of the album in which the track appears.
• track_name: The title of the track.
• popularity: A value between 0 and 100, indicating the track's popularity based on recent plays.
• duration_ms: The length of the track in milliseconds.
• explicit: Boolean indicating whether the track contains explicit content.
• danceability: Describes how suitable a track is for dancing (0.0 = least danceable, 1.0 = most danceable).
• energy: Represents the intensity and activity of a track (0.0 = low energy, 1.0 = high energy).
• key: The musical key of the track mapped using standard Pitch Class notation.
• loudness: Overall loudness of the track in decibels (dB).
• mode: Indicates the modality (major or minor) of the track.
• speechiness: Detects the presence of spoken words in the track.
• acousticness: Confidence measure of whether the track is acoustic (0.0 = not acoustic, 1.0 = highly acoustic).
• instrumentalness: Predicts whether a track contains vocals (0.0 = contains vocals, 1.0 = instrumental).
• liveness: Detects the presence of an audience in the recording (0.0 = studio recording, 1.0 = live performance).
• valence: Measures the musical positiveness conveyed by a track (0.0 = negative, 1.0 = positive).
• tempo: Estimated tempo of the track in beats per minute (BPM).
• time_signature: Estimated time signature of the track (3 to 7).

Each track is associated with a specific genre labeled under track_genre.