GV (Glance Views)
GV (Glance Views) is the reporting shorthand for what shoppers did before they didn’t — the count of times a product’s detail page was visited. In Amazon’s analytics vocabulary the same concept appears as DPV (detail page views) for sellers generally, and as FOPV (featured offer page views) when the views occurred while your offer held the Featured Offer.
What is GV?
GV (Glance Views) is the reporting shorthand for what shoppers did before they didn’t — the count of times a product’s detail page was visited. In Amazon’s analytics vocabulary the same concept appears as DPV (detail page views) for sellers generally, and as FOPV (featured offer page views) when the views occurred while your offer held the Featured Offer.
So GV is less a metric than a vocabulary entry: the number that answers “how many people looked?” You’ll see it in Vendor Central dashboards, category reviews, and performance conversations — and the discipline of using it well is knowing which flavour of the metric you’re looking at, because raw views, session-based views, and owned-offer views tell genuinely different stories.
Sorting the GV family (and why the differences matter)
The same visit can count differently depending on the report. Raw views count every page load (refreshes included) — fine for scale, noisy for decisions. Session-based counting (mostly what sellers see) treats a shopping visit more carefully — better matched to conversion math. FOPV filters to views where you held the Featured Offer — meaning on shared listings, it excludes the attention some other seller monetised. The practical sorting: use session/DPV numbers for seller conversion analysis (orders ÷ sessions), FOPV-style views for offer-share analysis on competitive pages, and treat raw view counts as directionally useful for vendor-side trend conversations. Mixing the flavours silently is the most common analytical error in this corner of the metrics world.
Using glance views to make decisions
The pairings that turn GV into action: with conversion (the orders ÷ views ratio — is arriving traffic converting?), with ad spend (views per dollar — is paid reach arriving at the page?), and with time (views before and after a change — what did the deal, ranking shift, or listing edit do?). The behavioural habits: annotate the trend chart with every action taken (campaigns, coupons, listing edits), watch the divergence between views and owned views on any listing with multiple sellers, and never let a views number leave the room without its conversion partner. The number measures arrivals; every decision lives in what happened next.
In practice
A vendor’s weekly review shows GVs down 12% and the room starts diagnosing a visibility crisis — until someone puts conversion beside the number and it’s UP 19% on the pair. The views dip was a coupon ending (fewer bargain hunters arriving); the shoppers who still came converted better. The review’s conclusion flips from “traffic problem” to “healthy mix change” in one paired glance — the exact discipline the metric rewards.
How Harpy Media helps
We report view metrics with their conversion partners and the changelog that explains them — arrivals without outcomes are half an answer.
GV FAQ
What is GV?
Glance Views — the reporting shorthand for detail-page views (visits to a product page). Related: DPV (detail page views), FOPV (views while you owned the Featured Offer).
Is GV the same as DPV?
Largely yes — they describe the same visit-counting concept; DPV is the more current term, and FOPV is the refined version filtered to your Featured Offer period.
How should I use glance views?
As a denominator: pair them with conversion, ad spend, and a changelog of actions — and check which counting flavour (raw, session, or owned-offer) a report is using.
Want these numbers watched for you, every week?
Book Free Consultation