Kworb Music Charts Scraper: Workflows and Practical Use Cases

Direct answer

Kworb Music Charts Scraper extracts public music streaming charts and catalog stats from Kworb.net without requiring logins or proxies. It supports nine modes covering Spotify daily and weekly charts across 76 country markets plus global aggregates, Apple Music worldwide song rankings, YouTube most-viewed music videos, Shazam and Deezer charts by market, US radio airplay, all-time top Spotify artists, global cross-platform rankings, and per-artist song streaming totals. Music teams use this Actor to track streaming performance across platforms, identify breakout tracks through chart rank deltas, and curate regional playlist recommendations. Workflows begin by selecting a specific chart mode, setting narrow market filters, and standardizing returned records into structured music intelligence reports.

Practical use cases

These use cases come from Kworb Music Charts Scraper's published documentation. Each is expanded into an operating pattern so the Kworb Music Charts Scraper output has a purpose beyond collection.

Use case 1: Music industry analytics

Outcome: track streaming performance across platforms and markets.

Question to answer: Compared with the last run, what is genuinely new or different, and does it cross the threshold for action?

Configure: Start with youtubeCategory (Kworb's regional split of today's most-viewed music videos on YouTube.), spotifyArtistIds (One or more 22-character Spotify artist IDs, one per entry, e.g. 06HL4z0CvFAxyc27GXpf02 (Taylor Swift). Looked up directly (no directory search needed) and processed before artistNames.), period (Daily chart (updated daily) or weekly chart (Fri-Thu aggregate).). Use the narrowest Kworb Music Charts Scraper values that represent the real task, keep the first result set small, and record why each selected input matters to the Kworb Music Charts Scraper outcome.

Working method: Anchor every record to a durable identifier before comparing runs, then classify each delta as new, gone, or altered. Hold any delta that cannot be tied to a stable key out of the action queue until it can be.

Deliverable: Create a dated change digest that highlights actionable differences and links each one to the underlying record. Include the Kworb Music Charts Scraper source identifier and the collected fields behind every Kworb Music Charts Scraper decision.

Stop condition: Pause when a change is flagged from a single run with no second confirmation, or the matching key itself proves unstable. Fix the Kworb Music Charts Scraper question, comparison rule, or configuration before expanding the Kworb Music Charts Scraper run.

Use case 2: Playlist curation

Outcome: surface daily/weekly top movers by country.

Question to answer: Which records satisfy the decision rule clearly enough to act on, and which need a second look?

Configure: Start with period (Daily chart (updated daily) or weekly chart (Fri-Thu aggregate).), country (Spotify chart market. global is the worldwide aggregate chart.), chartCountry (Country market for the Shazam or Deezer chart. ww is Shazam's worldwide chart. Note: Deezer does not publish charts for every country Shazam does (unsupported combinations return no data).). Use the narrowest Kworb Music Charts Scraper values that represent the real task, keep the first result set small, and record why each selected input matters to the Kworb Music Charts Scraper outcome.

Working method: Write the rule down before reviewing anything, change only one input or condition between batches, and record which field drove each record's classification so any shift in outcome has a traceable cause.

Deliverable: Create a decision-ready review queue that preserves each raw record and its inclusion or exclusion reason. Include the Kworb Music Charts Scraper source identifier and the collected fields behind every Kworb Music Charts Scraper decision.

Stop condition: Pause when the acceptance rule had to be reinterpreted mid-batch, or reviewers disagree on how to apply it to the same record. Fix the Kworb Music Charts Scraper question, comparison rule, or configuration before expanding the Kworb Music Charts Scraper run.

Use case 3: Competitive benchmarking

Outcome: compare an artist's cross-platform reach (Spotify vs Apple Music vs YouTube).

Question to answer: Where do these groups genuinely differ, and is the difference large enough to change a decision?

Configure: Start with youtubeCategory (Kworb's regional split of today's most-viewed music videos on YouTube.), artistNames (One or more artist names to look up in Kworb's all-time Spotify artist directory (case-insensitive, exact match preferred), one per entry. A batch of names emits one artistSummary + song records per artist, up to the shared maxItems cap. Alternatively supply spotifyArtistIds directly.), spotifyArtistIds (One or more 22-character Spotify artist IDs, one per entry, e.g. 06HL4z0CvFAxyc27GXpf02 (Taylor Swift). Looked up directly (no directory search needed) and processed before artistNames.). Use the narrowest Kworb Music Charts Scraper values that represent the real task, keep the first result set small, and record why each selected input matters to the Kworb Music Charts Scraper outcome.

Working method: Build the cohorts on a documented rule first, then compare only records inside the same cohort to each other, keeping any record that spans cohorts flagged for separate review.

Deliverable: Create a comparison matrix with cohort definitions, comparable fields, notable gaps, and decision implications. Include the Kworb Music Charts Scraper source identifier and the collected fields behind every Kworb Music Charts Scraper decision.

Stop condition: Pause when cohorts overlap on the defining field, or the gap being reported depends on a field with heavy missing data. Fix the Kworb Music Charts Scraper question, comparison rule, or configuration before expanding the Kworb Music Charts Scraper run.

Step-by-step implementation workflow

1. Select the required Kworb dataset mode in the Actor configuration, such as spotifyChart for streaming charts or artistStats for catalog deep dives.
2. Define geographical scope using country (for Spotify 76 markets), chartCountry (for Shazam 87 markets / Deezer), or youtubeCategory for regional video splits.
3. Configure target scope limits by populating maxItems (up to 1000) and specifying exact artist identifiers in spotifyArtistIds or artistNames.
4. Run the scraper via Apify and fetch returned records in JSON format, ensuring proper handling of omitted empty fields.
5. Ingest chartEntry, artistSummary, or song records into analytical storage, transforming raw stream counts and rank change strings into numerical metrics for tracking.

Input schema and parameter guide

The Actor's published input controls enable precise filtering across platforms and markets:

• mode (string): Selects dataset extraction mode. Options include spotifyChart, appleMusicChart, youtubeChart, topArtists, artistStats, shazamChart, deezerChart, radioChart, and globalArtistRanking. Default is spotifyChart.
• country (string): Specifies Spotify chart market across 76 countries or global. Default is global.
• period (string): Sets Spotify temporal window to daily (updated daily) or weekly (Friday through Thursday aggregate). Default is daily.
• youtubeCategory (string): Splits YouTube music video charts into regional groupings including global, anglo, hispano, asian, and other. Default is global.
• chartCountry (string): Defines market for Shazam (87 countries plus ww worldwide) and Deezer charts. Default is us.
• artistNames (array): List of artist names to look up in Kworb's Spotify directory (e.g. ["Taylor Swift"]). Emits artistSummary and song records up to maxItems.
• spotifyArtistIds (array): List of 22-character Spotify artist IDs (e.g., 06HL4z0CvFAxyc27GXpf02). Looked up directly and processed prior to artistNames.
• maxItems (integer): Hard cap limiting total emitted records (range 1 to 1000). Default is 25.

Data validation and operational quality controls

• Empty fields are omitted by Kworb when data is unpublished; pipelines must handle missing properties gracefully without setting false zeros.
• Spotify chart daily updates cap at 200 rows on Kworb's site, and globalArtistRanking caps at 300 rows regardless of higher maxItems settings.
• Deduplicate tracks using permanent identifiers like artistSpotifyId, videoId, or exact sourceUrl rather than relying solely on track title strings.
• Separate cumulative streaming figures from daily stream changes to maintain clear historical record baselines.

Frequently asked questions

How does Kworb Music Charts Scraper handle proxy requirements?

Kworb serves public chart data directly via standard HTTP requests, so no proxies, cookies, or account logins are required to run this Actor.

What happens if a Shazam or Deezer country chart combination has no data?

If Kworb does not publish a chart for the chosen market, the Actor returns zero records with an informative status message instead of throwing an error.

How are artist names resolved when using artistStats mode?

The Actor checks provided artistNames against Kworb's internal Spotify directory. Direct 22-character strings in spotifyArtistIds are processed first to skip directory lookups.

Why do daily Spotify chart results stop at 200 records?

Kworb's underlying source pages only publish up to 200 positions per country chart. Setting maxItems higher than 200 will not pull additional rows beyond what Kworb displays.

How are cross-platform points calculated in globalArtistRanking?

Kworb computes composite artist scores by combining real-time points from Apple Music, Spotify, iTunes, YouTube, Shazam, and Deezer, updating rankings approximately every 15 minutes.

Resources

• Kworb Music Charts Scraper on Apify