Amazon Music for Artists Analytics Guide | TAP
Amazon Music for Artists analytics
By TAP Editorial Team
Quick answer
Amazon Music for Artists is free to any artist with music on Amazon Music, and you reach it at artist.amazon.com rather than through Spotify or Apple. It shows plays, listeners, playlist adds and, uniquely, Alexa voice requests, which are a strong signal because someone asked for the track by name. Data lags 24 to 48 hours, so report weekly rather than daily.
Amazon Music for Artists gives you a first-party data source as detailed as anything the other platforms offer, and most artists never open it. Understanding how to extract, interpret, and action Amazon-specific metrics transforms editorial pitching from guesswork into measurable strategy. This guide covers navigating the dashboard, contextualising Amazon's metrics within broader campaign goals, and using Alexa request data to identify emerging opportunities.
Interpreting Plays, Listeners, and Adds-to-Playlist Metrics
Amazon Music plays and listeners metrics behave differently from platform to platform due to Amazon's subscriber base composition. Roughly 70% of Amazon Music listening comes from Prime subscribers who use it as a secondary service alongside Spotify or Apple Music; this means play counts often sit lower than competitors, but listener quality and playlist adds frequently outpace expectations. When reporting campaign performance, contextualise play counts within listener count: a track with 50,000 plays and 15,000 listeners suggests algorithm-driven discovery and repeat listening, whereas 50,000 plays across 35,000 listeners indicates broader but shallower reach. Playlist adds are your campaign's most valuable metric on Amazon. Editorial playlist placements drive sustained discovery and appear in Amazon Music for Artists as discrete add events, typically spiking after a pitch lands. Track this carefully by date: if you pitched a release to Amazon editorial on a specific week, isolate that week's adds-to-playlist figures to measure pitch efficacy. Saves represent listener intent to revisit, correlating strongly with long-term campaign success. Unlike Spotify's save-to-save play ratio, Amazon doesn't expose this directly, but monitoring saves weekly allows you to forecast whether editorial momentum will convert to sustained listening. Always compare metrics to your rolling 90-day average; a 30% uptick in listeners during campaign week is meaningful, whereas a 5% increase suggests the editorial push underperformed.
Tip: Create a simple spreadsheet tracking daily play and listener counts for campaign weeks, then calculate the daily average and compare to the 90-day baseline to quantify editorial impact.
Amazon's Unique Alexa Discovery Data and Voice Request Tracking
Amazon Music for Artists surfaces Alexa request data separately from streaming metrics, a feature competitors don't provide. This metric is exceptionally valuable for PR campaigns because it indicates how often listeners are actively requesting a track by voice: a signal of real familiarity and preference. Voice requests typically spike when a release receives mainstream radio play, press coverage that names the artist, or when TikTok trends funnel listeners to Amazon. Unlike algorithmic plays, which are passive and abundant, Alexa requests are intentional and rare; even modest numbers (50-200 weekly requests) represent significant audience penetration. Track Alexa request spikes against your PR timeline: if a national radio session aired on Monday and Alexa requests jumped Tuesday, you've identified a direct conversion pathway worth emphasising in campaign reports. This data is especially useful when working with artists who perform live, as radio play and festival announcements often precede Alexa request increases. However, the metric lacks geographic granularity on the standard dashboard; you cannot see which regions generated Alexa requests, so cross-reference with your own PR intelligence to triangulate campaign effectiveness. Include Alexa request trends in your campaign report as evidence of earned media success: it's a metric labels and management understand intuitively, as it implies listeners are actively remembering and requesting the track.
Tip: Set a weekly reminder to screenshot your Alexa request figures during campaign weeks; the dashboard history is limited, and screenshots become your campaign archive.
Contextualising Amazon Metrics Within Multi-Platform Campaign Reporting
Amazon Music data becomes powerful only when compared to Spotify and Apple Music figures. Create a simple three-column tracker during active campaigns: date, Amazon plays/listeners, and corresponding Spotify/Apple equivalent metrics. Amazon typically represents 8-15% of total streaming for UK artists, depending on genre and audience demographic. If your campaign achieves 100,000 Amazon plays, expect roughly 600,000-1.2 million Spotify plays from equivalent reach. That ratio matters when you read the numbers: it is easy to dismiss Amazon data as noise because the absolute play counts look low, but in proportion to platform size and Prime subscriber overlap, the figures are often competitive or superior. Geographic variance is critical: Amazon performs disproportionately well in the US and India, moderately in the UK and Europe, and weakly in Scandinavia (Spotify's stronghold). If your campaign targets UK playlists specifically, Amazon's contribution will be smaller, but playlist adds may show higher conversion rates. Document Amazon's percentage of total streams in campaign reports, and explain variance by geography and platform penetration in your target market. Plenty of campaign reports leave Amazon out because the picture feels incomplete without it, but being open about the platform mix strengthens the report rather than weakening it. Include a note on why Amazon metrics matter even when smaller in absolute terms: Prime subscriber overlap with your core demographic, voice discovery potential, and Twitch integration value for certain artist profiles.
Tip: Create a template that shows Amazon as a percentage of total campaign streams, with geographic notes explaining over/underperformance relative to expectations.
Using Amazon for Artists Data to Refine Pitching Strategy
Historical Amazon Music for Artists data informs your future editorial pitching approach. After a campaign concludes, analyse which playlist adds generated the most listener retention (comparing listeners added during playlist add date to listeners three weeks later). Amazon's editorial playlist ecosystem is less competitive than Spotify's curated playlists; pitches to Amazon editorial contacts often convert at higher rates, particularly for releases with strong geographic or demographic fit. Use your analytics history to identify which Amazon editorial playlist curator has supported you historically, then prioritise future pitches to those curators. Unlike Spotify's algorithmic playlist dominance, Amazon's editorial playlists drive more sustained adds-to-library, meaning editorial success on Amazon converts more reliably to long-term listener relationships. Review which tracks performed best on Amazon relative to Spotify and Apple: this reveals audience preferences that can inform genre, mood, and production choices for future releases. If an acoustic remix outperformed the original on Amazon but underperformed on Spotify, your Amazon audience skews towards that aesthetic; reflect this in future campaign messaging. Twitch integration is often overlooked: if you had a Twitch stream during a campaign period, cross-reference that week's Amazon listener data with your Twitch concurrent viewers to identify how many Twitch audience members converted to Amazon listeners. That crossover number is worth having on any campaign running across streaming and live video. Document these patterns quarterly to build a record of how you perform on Amazon relative to positioning and audience type.
Tip: After each campaign, run a simple correlation: which editorial playlist add generated the highest listener retention at 7, 14, and 30 days post-placement? Prioritise pitches to those curators for future releases.
Actionable Metric Targets and Campaign KPIs for Amazon Music
Set realistic KPIs for Amazon campaigns based on your positioning and audience size. For emerging artists (under 10,000 monthly listeners), aim for 5,000-15,000 plays per single campaign cycle (4-6 weeks), with 1,000-3,000 unique listeners and 50-150 playlist adds. For established artists (50,000+ monthly listeners), expect 50,000+ plays, 10,000+ listeners, and 200+ playlist adds during equivalent campaigns. These baselines vary dramatically by genre (hip-hop and R&B perform stronger on Amazon than indie rock), so research comparable artists in your genre before setting targets. Focus reporting on listener growth rate rather than absolute plays: if a release grows listeners 30% week-on-week during campaign weeks, declare success even if Amazon plays total 30,000 (lower than Spotify equivalents). Alexa requests are an underutilised KPI; even 100-300 weekly requests during campaign period represent disproportionate success and should feature prominently in reporting. Playlist add velocity matters more than total adds; if you land 5 adds in week one and none in weeks two-five, editorial momentum has stalled, suggesting weak playlist audience engagement. Conversely, if adds trend upward across weeks, the playlist is driving discovery rather than one-time placement impact. Include Amazon's contribution to overall campaign reach (percentage of total streams), segmented by geography if the campaign targeted specific regions. For Twitch-integrated campaigns, track Amazon listener spikes against Twitch stream concurrent viewers to quantify audience crossover. These metrics are less glamorous than Spotify's raw play counts, but they are more honest indicators of whether the campaign worked, and they tell you what to do next.
Tip: Create genre-specific KPI benchmarks by researching 5-10 comparable artists' Amazon metrics (via their public profiles); use their median monthly listeners and estimated monthly plays to establish realistic targets for your campaigns.
Putting Amazon Numbers Into Your Campaign Report
Most campaign reports leave Amazon out entirely or bolt it on at the end. Give it a proper section, particularly for releases with strong Prime demographic fit (family-friendly music, podcast-adjacent content, film/TV placements). Structure your Amazon section with three elements: absolute metrics (plays, listeners, adds), trend analysis (weekly growth rate, Alexa request trajectory), and contextual comparison (percentage of total campaign streams, geographic performance vs. expected). Use a simple bar chart showing Amazon alongside Spotify and Apple Music in your overview; visual parity legitimises Amazon as a meaningful campaign channel rather than a rounding error. Include a separate 'Alexa Discoveries' section if Alexa requests exceeded 50 weekly, as this data point is unusual and valuable for demonstrating authentic audience reach. For campaigns spanning multiple weeks, include a trend graph showing plays and listener growth week-on-week; this reveals campaign momentum visually and is easier for non-technical stakeholders to interpret than raw numbers. Document which editorial playlists converted to listeners (use your manual log), and note the curator's name; this builds a record of effective editorial relationships worth nurturing. Include a brief explanatory note on why Amazon metrics differ from Spotify (audience composition, Prime overlap, discovery mechanisms), so the variance reads as expected rather than as a failure. If Amazon underperformed expectations, explain specific factors: limited Prime penetration in your target market, weak Alexa discoverability for your genre, or earlier saturation on editorial playlists. Transparency here prevents future disappointment and sets realistic expectations for upcoming campaigns.
Tip: Design a one-page Amazon summary template that shows plays, listeners, adds-to-playlist, and Alexa requests in a side-by-side comparison against Spotify and Apple Music; this becomes your standard reporting format and speeds up campaign analysis.
Key takeaways
- Amazon Music for Artists is freely available but underutilised in campaign reporting; accessing it requires linking your profile to artist.amazon.com, not artist.spotify.com or music.apple.com. This single step unlocks geography-focused and Alexa discovery data competitors don't provide.
- Amazon metrics operate at 8-15% of Spotify equivalents for typical UK artists, but playlist add conversion rates and listener retention often outperform Spotify, making Amazon a disproportionately valuable editorial channel despite lower absolute play counts.
- Alexa voice request data is Amazon's unique advantage; intentional voice requests correlate directly with earned media success (radio play, press coverage), making them a more reliable campaign KPI than algorithmic plays.
- Geographic granularity is Amazon's strength; use regional play data to identify underperforming markets during campaigns and refine future route-to-market strategy by territory.
- Manual tracking of editorial pitches (date, curator, playlist name) is essential for correlating dashboard spikes to specific placements; Amazon doesn't expose which playlists added your track, so spreadsheet-based auditing becomes your reporting backbone.
Pro tips
1. Export your Amazon Music for Artists data as CSV every month on the same date (e.g., the 1st), then create a rolling 90-day average baseline for plays and listeners. During campaign weeks, calculate the daily average and compare it to your baseline to quantify editorial impact with precision. This method isolates campaign effect from background noise.
2. Maintain a manual 'Amazon Editorial Pitch Log' spreadsheet with columns for date, curator contact name, target playlist name, and artist-pitch details. Cross-reference weekly screenshot spikes on your analytics dashboard against this log to build a conversion rate metric (e.g., '60% of pitches converted to playlist placements'). This becomes your institutional knowledge for prioritising future pitches.
3. Track Alexa requests as a separate campaign KPI, separate from plays and listeners. Even modest Alexa request increases (50-200 weekly) represent significant audience penetration because requests are intentional, not algorithmic. Screenshot your Alexa request figures during campaign weeks; the dashboard history is limited, so your screenshots become the campaign record.
4. Create genre-specific KPI benchmarks by researching comparable artists' public Amazon profiles. Search each comparable artist on Amazon Music, access their public profile (if available), and estimate their monthly listeners and monthly plays; use median figures across 5-10 artists to set realistic targets for your own campaigns. That stops you over-promising or under-promising before the campaign starts.
5. For multi-platform campaigns, calculate Amazon's percentage of total campaign streams (total Amazon plays ÷ total plays across all platforms × 100). Include that percentage in your campaign report alongside a brief note explaining variance by geography and platform penetration. This contextualisation transforms Amazon's lower absolute numbers into legitimate, proportional data rather than dismissing it as noise.
Frequently asked questions
Why is Amazon Music for Artists less well-known than Spotify for Artists, and does it matter for PR campaigns?
Amazon's analytics platform has less marketing visibility because Amazon Music itself doesn't compete as aggressively on the creator-relations front; Spotify and Apple Music explicitly target artist partnerships and DSP-direct pitching. However, this means less competition for editorial placements on Amazon, and conversion rates for well-targeted pitches are often higher. The key is recognising that Amazon's audience composition differs (heavy Prime subscriber overlap, stronger US/India penetration), so it's a complementary channel worth pitching separately rather than an afterthought.
How do I know if an Alexa request spike is meaningful, versus random variance?
Compare weekly Alexa request figures against your rolling 4-week average to identify real spikes. A 50% increase in weekly requests is meaningful; a 10% fluctuation is likely noise. Correlate spikes against your PR timeline: if requests jumped the week after a national radio session aired or press coverage was published, the spike is campaign-driven rather than algorithmic. Document the PR event date alongside your screenshot for future reference and pattern recognition.
Should I include Amazon metrics in every campaign report, or only when performance is strong?
Include Amazon metrics in every campaign report where possible, but contextualise underperformance transparently. Omitting Amazon because figures appear weak looks like selective reporting and damages credibility; instead, explain why Amazon underperformed (e.g., limited Prime penetration in target demographic, weak Alexa discoverability for genre, early playlist saturation). This transparency normalises variance and sets realistic expectations for future campaigns.
How do I track which specific playlists converted from my editorial pitches, since Amazon doesn't expose playlist names?
Maintain a spreadsheet with pitch date, curator name, target playlist name, and artist details. When your dashboard shows a spike in playlist adds on a specific date, cross-reference it against your pitch log: if you pitched to a curator five days prior and adds spiked on day six, the conversion is likely from that pitch. This manual process is tedious but necessary for building your conversion rate metrics and refining future pitching strategy.
What's a realistic play-to-listener ratio on Amazon, and does it indicate campaign success?
Amazon's typical play-to-listener ratio ranges from 2.5:1 to 4:1 (e.g., 50,000 plays across 12,500-20,000 listeners). A lower ratio (closer to 2.5:1) suggests broader listener reach with less repeat listening, often indicating strong editorial discovery; a higher ratio (closer to 4:1) suggests concentrated listening among fewer users, often indicating algorithmic recommendation or existing fanbase engagement. Both patterns are valid; use the ratio to diagnose campaign type (editorial-driven vs. fanbase-driven) rather than judging success.
From the field
Proof points
- Named contact reply rate vs studio@: 5x higher (Liberty Music PR campaign data, 2024-2026)
- Specialist shows beat playlist pitches: Named producers respond, playlist-only emails get dropped (Liberty 2024-2026)
- Best UK send window: Tue/Wed 09:00-10:00 UK (Across 60+ campaigns)
- Optimal follow-up cadence: +7 days from initial pitch (Liberty internal data)
What actually happened
Roam Belle, Specialist UK radio + community stations: 96 plays across the campaign window, declining after week 5. Named-contact pitches outperformed generic submissions. (February 2025)
Amazon Music editorial sits inside Amazon's wider ecosystem, which means the rules feel different to Spotify or Apple. The named contacts respond, the generic submission tools rarely do. I treat it as a relationship channel, not a portal. Pitch the editorial team by name, lead with the listener context not the streaming numbers, and follow up once after seven days. Then move on.
Chris Schofield, Radio plugger, Liberty Music PR
Related resources
Further reading
- TAP Blog — In-depth guides, comparisons and advice for independent artists running their own promotion.
- UK Music — The voice of the UK music industry, representing labels, publishers, and collecting societies.
- Music Week — Industry news, charts, and analysis for music professionals.
- The Music Network — Global music business intelligence and networking.
Get your free release plan in 60 seconds
Tell TAP your track and release date. It builds your 4-week timeline, drafts personalised outreach for your contacts, and tracks replies in one place. First release is free, no card required.