Back to Blog
GuidesOctober 19, 2026· 13 min read

KDP Ads Impression Share: How to Read Your Search-Term Report Before Touching a Bid

I

InteliAds Team

KDP Ads

KDP Ads Impression Share: How to Read Your Search-Term Report Before Touching a Bid

You open the Amazon Ads console, see a search term with a tiny share of the impressions available, and the urge is to raise the bid. That reflex is how KDP authors burn budget on terms that were never going to sell the book. KDP ads impression share is a diagnostic signal, not a command, and it only helps when you read it next to the rest of the search-term report.

Short answer: Amazon's Sponsored Products search-term impression share report lists impression share and impression rank by search term. Impression share is your account's share of all Sponsored Products ad impressions for that search term over the selected period. A low figure tells you the exposure was limited, but not why, and not whether more exposure would have been profitable. Read a consistent period first, sort the terms by what happened, and only then decide whether a bid, a targeting change, or no change at all is the right response. Check the field definitions in Amazon's documentation, because the console is the source of truth.

Why a bid change is the wrong first move when impressions look low

A bid is only one of several things that decide whether your ad is shown on a search. Eligibility of the book, the match between the term and the book, competing bids, and campaign settings all sit in front of it. If you change the bid before you know which one is limiting you, you cannot tell afterward what the change actually did.

There is also a cost problem. Raising a bid on a term with low impression share raises your cost on every click you do get, including clicks that never turn into orders. Low share is not evidence of lost profit, and it is not evidence of a budget shortage either. A term can have a low share simply because it is a poor fit for the book, in which case low exposure is the system working correctly.

Three traps show up most often when authors react to a low figure:

  • Treating every low share as lost sales: Some of that unseen exposure would have been clicks from shoppers who never wanted the book.
  • Borrowing Google Ads language: Amazon's report does not break the gap into lost-to-budget and lost-to-rank columns, so do not assume you can split the cause from the percentage alone.
  • Comparing mismatched windows: A week of data set against a month of data produces differences that look like performance changes but are only calendar differences.

Bid-desk tip: write down the question before you open the report, for example "which terms is this book not appearing for that it should?" A defined question stops the report from becoming a list of numbers to chase.

What the search-term report can and can't tell you about KDP ads impression share

The share and rank figures are account-wide for the shopper's search term, not a separate impression-share measurement for one keyword, book or campaign. That distinction matters. A single broad, phrase, or auto target can show up across many different search terms, each with its own impression share and impression rank. A term appearing in more than one campaign retains account-wide share and rank. Use campaign or target reports separately when attributing performance to one book.

What it cannot do is explain itself. It does not tell you whether a gap came from bid level, relevance, book eligibility, or competition. It also does not tell you what the missing impressions would have earned. For that you need clicks, orders and spend from the relevant performance reports. KDP royalties are a separate book-level context; do not attribute a particular royalty payment to one search term.

Use the Amazon Ads reporting console to pull the report, and keep the date range identical every time you compare. InteliAds does not display this report or an impression-share dashboard. What it can do is let you track KDP ads and royalties for the same period, so the exposure story from Amazon can be set against spend and profit. Profit in InteliAds is royalties minus ad spend, and the royalty side needs KDP Sync to be linked.

Sorting the report: separating terms that never got a chance from terms that got a chance and failed

The most useful split in this report is between terms with thin exposure and terms with real exposure that did not convert. They look similar in a spreadsheet and need opposite responses. One group needs a diagnosis of why the ad barely appeared. The other needs a decision about whether the term deserves any more money.

Hypothetical example: a cozy mystery author sees the term "village mystery series" with low impression share, few impressions, and no orders. Separately, "cozy mystery books" has many impressions, a healthy click count, and spend with no orders. The first term never got a fair test, so no conclusion about it is safe. The second got its chance and failed, so it is a candidate for a lower bid, a negative, or a pause, regardless of its impression share.

Work through the report in this order:

  1. Set one consistent date range and keep it for every comparison.
  2. Sort by impressions, then group terms into thin exposure and real exposure without using a fixed cutoff, since the right line depends on your category and volume.
  3. For the thin group, note impression share and impression rank, and mark which terms are relevant to the book.
  4. For terms with sufficient data, compare clicks, spend and attributed sales in the corresponding performance reports. Use the book royalty margin as an assumption for break-even estimates, not as search-term royalty attribution.
  5. Leave any term with too little data unchanged and revisit it in the next comparable period.

Bid-desk tip: a low share on an irrelevant term is a result, not a problem. Mark it as such so it does not reappear on your fix list every review.

Diagnosing low impressions: bid too low, targeting too narrow, or book not eligible

Once a relevant term has thin exposure, test the causes one at a time. Bid level is only one possibility. Targeting that is too narrow, a match type that rarely triggers, a campaign that is not running as expected, or a book that is not eligible to be advertised on that search can each produce the same low figure.

The table below pairs report patterns with the console check to run before touching a bid. Each check can be done in the Amazon Ads console, and none requires a number from this article.

Pattern in the reportCause to test firstConsole check before any bid change
Relevant term, low impression share, few impressionsBid below what the auction needs, or targeting too narrowReview the target's bid and match type, then check whether a broader match would reach the term
Low share on terms that appear under only one targetThe term reaches you through a narrow routeCompare which targets and campaigns produced the term, and add it as its own target if it is relevant
Low share across nearly every term in one campaignCampaign-level limit or book eligibilityCheck campaign status, daily budget, and whether the advertised book is active and eligible
High impressions, weak clicks, mixed shareRelevance, not exposureRead the search terms for intent mismatch and consider negatives instead of more bids
Terms with strong royalties and low sharePossible room to grow profitablyConfirm royalty per order against spend, then make one small, logged bid change and re-read the same period length
Low share but no relevance to the bookNothing to fixLeave it alone, or add it as a negative if it is drawing clicks

If you want these checks to run on a schedule rather than by memory, InteliAds lets you write your own IF/THEN rules for Sponsored Products, which run hourly, and Rules Dry Run previews the changes before they apply. BidBot is a separate feature that offers bid recommendations. Neither one reads Amazon's impression-share report, so use them for spend and performance conditions, and keep the exposure diagnosis in the Amazon console. The KDP ads guide covers the wider account setup that sits behind these checks.

Use the account-level share report alongside campaign performance data to decide which hypotheses need a test.

Worked example: a 12-keyword campaign with three different problems

Hypothetical scenario, not a benchmark: a manual Sponsored Products campaign for a cozy mystery paperback has 12 keywords. The figures below cover one consistent reporting period in the Amazon Ads reporting console, using campaign performance data alongside account-wide search-term impression share and rank. The groups below are illustrative; share is not calculated separately for this campaign.

Group A is the tempting one, because converting terms with low share look like a bid problem. Low share alone does not prove lost profit or a budget shortage, though, so check the margin first. Group B is not automatically a bid problem either, and group C will never be fixed by spending more.

What each group needs before any change

  • Group A: estimate the margin using attributed sales and an explicit royalty assumption, then compare the same period before and after any later change.
  • Group B: check whether the search terms are realistic for the book, and whether stronger terms in the same theme already get exposure elsewhere.
  • Group C: read the actual search terms. If shoppers are looking for something your book is not, consider negatives. If the terms fit, look at the listing instead.
  • Group D: record it as the baseline for comparison and leave it alone.

Deciding what to change, what to leave alone, and how long to wait before judging

Change one thing per group, and write down the date and the reason. If you change bids, negatives, and the listing all at once, the next report cannot tell you which one mattered.

Report patternEvidence still missingReasonable first actionLeave alone
Low share, converting, profitableWhether rank or budget is the constraintSmall, logged bid test on one termTerms in the same group that have not converted
Almost no impressionsSearch demand and relevanceReview the term list. Retire it or move it to a better campaign.Bids on healthy neighbors
Many impressions, no clicksWhether the term matches shopper intentInspect search terms. Add negatives if they are clearly off-topic.Bids, until intent is understood
Steady and profitableNone neededKeep as the baselineEverything

On timing, I avoid a fixed day count. Wait until the period you judge holds enough impressions, clicks, and orders to be more than noise, and compare it against a period of equal length. Bid-desk tip: if the clicks in a group are only a handful, a lower share is a reason to keep watching, not a reason to act.

Console actions in order

  1. Open the search-term impression share report in the Amazon Ads reporting console and set one consistent date range.
  2. Sort by search term and note share and rank beside clicks and orders.
  3. Group terms by pattern, as in the table above.
  4. Make one logged change per group.
  5. Re-run the same report over a period of equal length and compare.

InteliAds does not display the impression share report or an impression-share dashboard, so that diagnosis stays in the Amazon Ads console. What InteliAds adds is the profit side. As a KDP Sponsored Products manager connected through Amazon Ads OAuth, it can track KDP ads and royalties. When KDP Sync is linked, it imports royalties, orders, KENP, and pricing, and profit is royalties minus ad spend. You can write IF/THEN rules that run hourly, and Dry Run previews the changes before anything is applied. BidBot is separate and offers bid recommendations. None of these tools predicts results.

FAQ

Q: Does Amazon show an actual impression share percentage for KDP ads, or do I have to infer it? A: Amazon's Sponsored Products search-term impression share report shows impression share and impression rank by search term, so you do not have to infer it for terms it covers. Open it in the Amazon Ads reporting console, and see Amazon's announcement for its definition. InteliAds does not display this report.

Q: If a keyword has zero impressions, does that always mean my bid is too low? A: No. Zero impressions can also come from low search demand, weak relevance, or targeting that rarely matches real queries. Check those before raising a bid.

Q: How many days of search-term data do I need before a bid change is justified? A: I do not use a universal number. Use a period long enough to contain meaningful clicks and orders, and compare it to a period of the same length. Thin data supports watching, not changing.

Q: What should I do when a search term has plenty of impressions but no clicks? A: Read the term against what your book actually offers. If it is off-intent, consider a negative. If it fits, review the listing before touching the bid, since a higher bid buys more of the same non-response.

Q: How do I tell if my book's price, cover, or reviews are suppressing impressions rather than my bid? A: The report alone cannot separate them. Compare your listing with competitors on the terms where you do appear, and look at whether clicks and orders lag even when share is healthy. That pattern points to the listing, not the bid.

Q: Should I raise bids on terms that already convert, or fix the terms that get no exposure first? A: Start with converting terms only if they are profitable after ad spend, and test small, logged changes. Terms with no exposure need diagnosis, not money, so handle them in parallel without raising bids on them blindly.

Q: When does adding negative keywords make sense before adjusting bids? A: When the search-term report shows clearly irrelevant queries consuming impressions or clicks. Removing them cleans the data, so any later bid decision rests on cleaner evidence.

Q: Can auto campaign search terms help me diagnose low impressions on my manual campaigns? A: Yes, as a discovery source. Terms that auto campaigns surface and convert on can show which queries your manual campaign lacks. Confirm each term against its own report data before adding it.

Reading kdp ads impression share well means treating low share as a question, not a verdict, and checking profit before spending more. If you want royalty-aware profit beside your campaigns, review InteliAds pricing, then See InteliAds plans or Create an account. Essential has no trial. Review your settings before enabling automated changes. For more, see the KDP ads guide and more KDP ads guides.

See InteliAds plans: compare Essential, Pro, and Publisher (Essential has no trial; Pro and Publisher include a 7-day trial). InteliAds is a Sponsored Products manager for KDP authors: royalty-aware profit when KDP Sync is linked, user-written IF/THEN rules with dry run, and targeting filters for keywords, product targets, and search terms. Create an account.

Put these rules to work

Set IF/THEN conditions, run them every hour, and revert any batch when you need to.