How to Use KDP Analytics: A Practitioner's Step-by-Step Tutorial

You need an active KDP account with at least one published title (eBook, paperback, or hardcover) before any analytics data populates. Draft titles and titles in review show zero data.

You'll also want a spreadsheet ready — Google Sheets or Excel — to log weekly snapshots. KDP does not store historical data beyond 90 days in some views, and the export function gives you raw CSVs that are easier to analyze outside the dashboard.

If you're running Amazon Ads, note that ad analytics live in a completely separate interface at advertising.amazon.com — not inside KDP. This tutorial covers the KDP dashboard only. Ad performance data requires a separate workflow.

Time investment: Initial setup and orientation takes about 45-60 minutes. Ongoing weekly review runs 15-20 minutes once you know where to look.

Log into kdp.amazon.com and click 'Reports' in the top navigation bar. This is the primary analytics hub. You'll see four tabs: Orders, Royalties, Prior Months' Royalties, and Payments.

The default landing view is the Orders tab, which shows real-time unit sales data (with a 24-48 hour lag). This is where most authors spend 80% of their analytics time.

The Royalties tab shows estimated earnings for the current month. Treat these as estimates — final royalties are calculated after the month closes and returns are processed. The number you see mid-month will shift.

Avoid this mistake: Don't confuse the 'Payments' tab with current earnings. Payments reflect what was actually deposited into your bank account, which is always 60+ days behind your actual sales month. New publishers frequently panic thinking they're not earning when they're just waiting on the payment cycle.

The Orders tab shows a date-range selector at the top. Default is the last 30 days. You can pull up to 90 days here without exporting. Set your date range first before reading any numbers — the default range resets every session.

The table shows: Title, Author, ASIN/ISBN, Marketplace, Units Ordered, Units Refunded, and Net Units. Focus on Net Units — that's your real number after returns.

Marketplace column is where most authors leave money on the table analytically. Click the dropdown and switch from 'All Marketplaces' to individual markets (US, UK, DE, CA, AU, etc.) to see geographic breakdown. According to Amazon's own marketplace documentation, KDP titles are available in 11+ international stores, but most authors never check non-US performance.

Avoid this mistake: Don't sum 'Units Ordered' across marketplaces and call it your total. Always use Net Units, and always check if you're filtering by a single marketplace or all of them — the filter state isn't obvious at a glance.

If any of your eBooks are enrolled in KDP Select (Kindle Unlimited), the Orders tab will show a separate column: KENP Read (Kindle Edition Normalized Pages). This is not the same as units sold — it's the number of pages read by KU subscribers.

KENP royalty rates fluctuate monthly based on the global KDP Select fund. Amazon publishes the per-page rate after each month closes. As of early 2026, the rate has historically hovered around $0.004-$0.005 per page, but this changes monthly and you should verify the current rate in your Prior Months' Royalties tab after each month closes — we don't have real-time fund data to cite here.

To estimate KU revenue: multiply your KENP pages read by the published per-page rate for that month. A 200-page book fully read by 100 KU subscribers = 20,000 KENP × current rate.

Avoid this mistake: Don't compare KENP reads to unit sales as if they're equivalent. A 'read' in KU means the subscriber read at least one page. Completion rate is invisible in KDP's native dashboard — you can't see how far readers actually got.

On the Orders tab, set your desired date range, then click the 'Download' button in the upper right of the table. KDP exports a CSV file with all the columns visible in the table plus a few additional fields not shown in the UI, including transaction-level detail.

Do this monthly, on the 1st or 2nd of each month for the prior month. Create a folder structure like `/KDP-Reports/2026/` and name files consistently: `kdp-orders-2026-01.csv`, `kdp-orders-2026-02.csv`. Sounds obvious, but disorganized exports are the number-one reason authors can't answer basic questions about their catalog six months later.

The CSV includes columns for: Order Date, Title, Author Name, ASIN, Marketplace, Units Ordered, Units Refunded, Net Units Sold, Royalty Type, and Royalty.

Avoid this mistake: Don't rely solely on the in-dashboard view for record-keeping. KDP's interface has historically changed layouts without notice, and some authors have reported losing access to older date ranges after interface updates. Your CSV exports are your permanent record.

Switch to the Royalties tab. This view shows estimated royalties for the current month-to-date, broken down by title and marketplace. The royalty figure here accounts for your royalty rate (35% or 70% for eBooks, 60% minus printing costs for print) but is still an estimate until the month closes.

For print books, the royalty calculation is: (List Price × Royalty Rate) − Printing Cost. KDP shows the printing cost deduction in the Royalties tab if you expand the row for a paperback or hardcover title. This is where you catch pricing errors — if your royalty per unit is under $2.00 on a paperback, you likely have a pricing or trim-size issue worth investigating.

For a practical benchmark: a 6×9 paperback with 200 pages priced at $14.99 on amazon.com typically generates around $5.34 in royalties at 60% after printing costs — but printing costs vary by page count, ink type, and trim size. Use KDP's own pricing calculator (available on the pricing page during book setup) to verify your specific numbers.

Avoid this mistake: Don't use the current-month Royalties tab number for income reporting or tax planning. Use Prior Months' Royalties for finalized figures only.

Click the 'Prior Months' Royalties' tab. This is the only place in KDP where finalized, closed-month revenue data lives. Each row represents one closed month, one marketplace, one title. These numbers are final — returns have been processed, rates have been applied, and this is what drove your actual payment.

This tab is your ground truth for year-over-year comparisons. If you're trying to answer 'did January 2026 outperform January 2025,' this is where you get the answer — not the Orders tab.

You can also download this data as a CSV. Do it. The interface only shows a limited number of months before older rows become harder to access, and the layout has changed in past updates.

Avoid this mistake: Don't skip this tab because the current-month Royalties tab looks similar. The prior months data is finalized; the current-month data is an estimate. They serve completely different analytical purposes, and conflating them leads to inaccurate revenue tracking.

BSR (Best Sellers Rank) does not appear anywhere inside the KDP analytics dashboard. This surprises a lot of publishers who expect it to be there. To find BSR, you go directly to your book's Amazon product listing and scroll to the 'Product Details' section — it's listed under 'Best Sellers Rank' with category breakdowns.

BSR updates roughly hourly on the live Amazon listing. A BSR under 100,000 in the main Kindle Store or Books category generally indicates consistent daily sales, but the exact sales volume per BSR position varies significantly by category and time of year. We don't have category-specific BSR-to-sales conversion data to cite for 2026 — treat any published conversion charts as rough estimates, not precise figures.

For ongoing BSR tracking, manual spot-checking works for small catalogs (under 10 titles). For larger catalogs, a tool like PageBeacon can track BSR trends across your titles over time, which is useful for spotting organic ranking drops before they hit your royalty numbers.

Avoid this mistake: Don't check BSR once and draw conclusions. A single BSR snapshot is nearly meaningless — a book could be at 5,000 BSR from one sale spike or consistently at 50,000 from steady daily sales. Trend over time is the signal.

Consistent review beats deep-dive analysis done once a quarter. A 15-minute weekly check catches problems — a title going out of stock, a pricing error on a new marketplace, a sudden royalty drop — before they compound.

Here's the weekly sequence that works: (1) Orders tab → check net units for the last 7 days across all marketplaces. (2) Spot-check BSR on your top 3-5 titles on live Amazon listings. (3) If it's the 1st-5th of the month, download last month's CSV and log it. (4) If any title shows a >30% drop in weekly units versus the prior week, investigate the listing directly — check if the price changed, if a competitor launched, or if a category ranking shifted.

The 30% week-over-week drop threshold is a practical trigger, not a published KDP metric. It's the point where normal sales variance becomes a signal worth investigating rather than ignoring.

Avoid this mistake: Don't check analytics daily if it's causing reactive decision-making. Changing prices, keywords, or categories based on 24-hour data swings is a common trap. Weekly cadence gives you enough signal to act on without reacting to noise.

Raw numbers without context are just noise. Here's how to read the signals your KDP data is actually sending.

Steady units, declining royalties: Usually means a marketplace currency shift (GBP or EUR weakening against USD) or an accidental price change. Check the Royalties tab by marketplace and compare royalty-per-unit across months.

Zero units for 14+ days on a previously selling title: Don't assume the book stopped selling. Check the live listing first — is it still showing as 'In Stock'? Is the price still correct? Has the category ranking changed? Print titles can go out of stock without triggering a KDP notification.

KENP reads spiking while unit sales are flat: A KU promotion, a BookTok mention, or an Amazon algorithm push is sending KU subscribers to your book. This is a signal to consider whether your book is better monetized inside or outside KDP Select — a decision that depends on your full catalog strategy, not just one data point.

Avoid this mistake: Don't optimize for a single metric in isolation. Authors who chase BSR often drop prices to spike rankings, which can permanently anchor reader price expectations and reduce long-term royalties per unit. Analytics should inform decisions, not replace judgment.

Problem 1: My Orders tab shows zero sales but I know people bought the book.
Check your date range filter first — it resets to a default range each session and may be set to a period before your book went live. Also confirm the marketplace filter isn't set to a single market where you had no sales. If both look correct, the 24-48 hour reporting lag may be the cause — wait a full 48 hours before escalating to KDP support.

Problem 2: My royalties this month look much lower than last month but units are similar.
Compare royalty-per-unit between the two months in the Royalties tab. If per-unit royalties dropped, you likely have a marketplace mix shift (more sales in lower-royalty markets like IN or BR), a currency conversion change, or an unintended price change on one marketplace. Export both months' CSVs and compare line by line.

Problem 3: I can't find KENP data for my eBook.
KENP data only appears if the title is enrolled in KDP Select. Go to your Bookshelf, click the three-dot menu next to the eBook title, and check enrollment status. If it's not enrolled in KDP Select, it won't appear in KU and won't generate KENP data — which is expected, not a bug.

Problem 4: My Prior Months' Royalties tab shows a different number than what was deposited.
This is normal. The Prior Months' tab shows royalties earned in that month. The Payments tab shows what was deposited, which includes royalties from approximately two months prior. A March deposit reflects January's finalized royalties. If the math still doesn't reconcile after accounting for the delay, check whether you have multiple KDP accounts or a pending tax withholding issue in your tax interview settings.