A surgical technologist needs to confirm which proximal humerus plate the surgeon ordered for Tuesday's surgery. She goes to the catalog, selects humerus in the anatomical region filter, opens the first product page, and sees it's the steel version. She goes back to the listing, opens the titanium one, scrolls down to the codes, and goes back again to check the screws that go with it. In five minutes, she's been through the same page four times.
In Analytics, that visit shows up as one person with several views of the catalog. Multiplied by hundreds of people, it produces a figure worth knowing how to read.
What the metric counts
Views per user is a ratio: the number of times a page was loaded over the number of people who viewed it. On a company page, such as an “About” page or a contact page, the number stays close to one, because people read it and move on. In a medical device catalog, usage is different. People come in with a region or a procedure in mind, compare one product with another, confirm a code, and go back to the listing to open the associated instruments. Each return adds a view.
That's why, in a catalog, a high views-per-user figure is a sign of use. It indicates that people found a listing that works for going back and forth, and that they browse it instead of abandoning it at the first product page.
SAI's catalog, 39 days after launch
At SAI, the catalog page, /productos/, recorded 9,617 views in the 39 days after the launch on August 10, 2026, with 5.07 views per user and an average time of 1 minute 56 seconds. In the equivalent window before the launch, the same page had 2.46 views per user.
The figure includes all traffic sources for the period: organic search, direct visits, and every other channel. That's enough for this analysis, because the question is what people did once they were on the site.
Read that way, it says something concrete: the catalog gets used. People come in, filter, go back, and open another product. In the same window, 1,396 people downloaded technical documentation from the site, which is the step after finding the product.
What to know before comparing
Views per user doesn't measure the same thing in every catalog, and comparing two periods or two sites requires knowing how each one is built.
If the filters change the results without reloading the page, a person can go through ten combinations and add only one view. If each filter loads a new URL, every click counts. The same goes for going back from the product page: using the browser's back button or a link to the listing changes what gets recorded. A redesign that alters any of those things changes the figure even if people do exactly the same thing.
Average time helps tell the two readings apart. Five views in twenty seconds look more like someone who can't find what they're looking for and tries again. Five views in almost two minutes look more like someone who is comparing.
What to look at alongside the number
The catalog page metric shows the listing. Someone who comes from Google straight to a product page doesn't go through it, and in an implant catalog, many visits start that way. To see the full path, the product pages need to be analyzed together with the listing.
Other signals complete the picture. Site searches that return nothing reveal what name people use for a product the catalog calls something else. Filter combinations that come up empty indicate where the structure doesn't match the way people search. And documentation downloads, cross-referenced with the product page they come from, show which products are being looked at seriously.
Those signals don't appear on a dashboard by themselves. They're set up when the site is built, using the same categories as the catalog: anatomical region, procedure, code, and brand.
Services covered in this article
