February 2, 2024 by InsightLeap
Glance views are the number of times shoppers viewed your product detail page while your retail (1P) offer was the featured offer, the spot most people still call the Buy Box. Amazon doesn't deduplicate the count, so 15 glance views could be 15 shoppers or one shopper reloading the page. The metric lives in Vendor Central under Reports, then Retail Analytics, then Traffic, and in 2025 Amazon began renaming it featured offer page views (FOPVs); the definition and the data behind it are unchanged.
The rest of this page covers what exactly gets counted and what never makes it in, where the report lives, how glance views line up against the traffic metrics sellers see, and how to turn the number into a conversion read you can act on every week.
Three counting rules explain most of this metric's behavior, and all three trip up vendors reading their first Traffic report.
A glance view is recorded only while your retail offer is the featured offer. When a third-party seller wins the featured offer on one of your ASINs, shoppers keep opening the detail page, but none of those visits land in your glance views. That traffic is invisible to you. So when views suddenly drop on an otherwise healthy ASIN, check who held the featured offer over that stretch before you conclude that demand fell.
Glance views are not deduplicated. Every page load counts: a shopper who checks your product five times before buying generates five glance views, and Amazon gives vendors no way to collapse those loads into one visitor. The deduplicated version of this idea, sessions, exists on the seller side and never made it to Vendor Central.
Glance views are a vendor metric. Sellers working in Seller Central see page views and sessions instead. If you sell hybrid, or you compare notes with a seller-side colleague, the numbers follow different counting rules; the table further down covers how they differ.
In 2025, Amazon began renaming glance views to featured offer page views (FOPVs) in Vendor Central. The rollout has been gradual, so depending on your account and the screen in front of you, you may see the old name, the new one, or both. Nothing behind the label changed: the counting rules and the historical data are the same.
The new name earns its keep by stating the counting condition out loud. The metric counts page views that happened while your offer was the featured offer, which is the detail the old name hid. If a report lands in your inbox with a FOPV column, read it as the glance views column and move on.
The report lives at Reports, then Retail Analytics, then Traffic, in the manufacturing view. If you feed a warehouse or a BI tool, the same traffic data is available through SP-API.
A few practical details about the dashboard:
Vendor-facing traffic data is younger than most people assume: Amazon first exposed glance view and conversion data to all vendors in November 2020, through Sales Diagnostic reporting. For the wider tour of what else the console offers, our guide to Amazon Vendor Central reports and analytics walks through the rest.
The Amazon ecosystem has several numbers that all sound like "people looked at my product," and they measure different things.
| Metric | Who sees it | What it counts |
|---|---|---|
| Glance views (FOPVs) | Vendors, in Vendor Central | Detail-page views while your retail offer held the featured offer; not deduplicated |
| Page views | Sellers, in Seller Central Business Reports | Detail-page views regardless of who held the featured offer |
| Sessions | Sellers only | Unique shopper visits within a 24-hour window; one session can span several page views |
| Ad impressions, search impressions, brand-store visits | Advertising and brand tools | Appearances upstream of the detail page, before any click happens |
Two comparisons cause most of the confusion. First, glance views against page views: page views don't exclude the periods when a third-party offer was featured, so a hybrid brand lining the two up across accounts is comparing two different counts. Our post on Amazon ASIN page views covers the seller-side metric in more depth.
Second, impressions against glance views. An impression means your product appeared in search results or on a category page; a glance view means a shopper opened the detail page. Impressions measure exposure and glance views measure interest, so high impressions with flat glance views mean shoppers saw the product and declined to click. That points the work at what they saw in the search results: the title, the lead image, the price, the review line.
The most useful thing to do with glance views is turn them into a conversion rate:
Conversion rate = ordered units ÷ glance views
Use ordered units, not shipped units. Orders land close in time to the page views that produced them, while shipments lag by days, so a shipped-based rate smears one week's demand across the next. What counts as a good rate varies by category and price point, so treat your own history as the benchmark: the trend over time and the spread between comparable ASINs in your catalog tell you more than any industry figure.
Before you read any conversion move as real, check it against stock. Amazon's out-of-stock rate is itself computed from glance views:
% Rep OOS = (glance views while out of stock ÷ total glance views) × 100
An out-of-stock week looks exactly like a conversion collapse until you check it, because shoppers kept viewing while there was nothing to buy. Vendor Central also reports Procurable Product OOS, which shows how often your offer was out of stock when shoppers visited the detail page, and reading your conversion rate next to it tells you whether the page stopped converting or simply had nothing to sell.
There is also a reason to care beyond your own dashboard: Amazon uses glance views to gauge demand, and for a vendor that demand shows up as purchase orders. Glance views also feed Amazon's Buy Box Fast Track metric.
Three limits are worth knowing before you build a weekly report on this number.
A glance view is one view of your product detail page during a period when your retail (1P) offer held the featured offer. Amazon reports it to vendors in the Retail Analytics Traffic report, and it is the closest thing vendors have to a page-view count.
No. Glance views count page loads, and Amazon doesn't deduplicate them, so fifteen glance views could be fifteen shoppers or one shopper returning fifteen times. The deduplicated metric, sessions, exists only on the seller side.
No. When a 3P seller holds the featured offer, detail-page visits during that period never appear in your glance views. On ASINs where the featured offer moves between your retail offer and third parties, swings in glance views can reflect featured-offer changes as much as demand, so check who held the offer before drawing conclusions.
The new name for glance views. Amazon began renaming the metric in Vendor Central in 2025; the definition and the data are unchanged, and screens may show either name while the rollout continues.
Glance views sit at the top of the only funnel Vendor Central shows you: views, then ordered units, then purchase orders. The weekly routine is short: pull the Traffic report, compute ordered units ÷ glance views, check Rep OOS before believing any conversion move, and treat a lost featured offer as the first suspect whenever views fall off a cliff on a single ASIN. If you would rather have that read waiting for you than rebuild it every Monday, InsightLeap's Traffic Insights has put glance views, page views, sessions, and conversion rate alongside your sales metrics since July 2023, and pairing traffic with Shipped COGS separates a visibility problem from a conversion problem.