Adobe Analytics Scroll Depth Buckets Showing "Unspecified" Despite Configuring 0%–100% Buckets

I’d wager that the unspecified values are from the first hits of the visits where there is not yet any scroll depth measured.

This is expected behavior, and based on what you have here it looks like your component is working correctly.

When you put an evar against it’s own instances metric, you will never see unspecified because it will only show you instances where that evar was actually set. If you compare the number of instances against page views (which is where I’m assuming this is being set), the numbers should be pretty close – that can give you an idea if this is firing reliably.

The metric visits, on the other hand, will count all of the visits in your time period against the evar. Now, it is possible for an evar to have more than one value in the same visit, so if you were to add up the rows of the values (for now ignore the unspecified row, and just look at the others) it would be greater than the total. So your five bucket values together total 398, which is a lot more than your total of 291 visits. Now lets consider the unspecified. If there is even just one hit in the visit that doesn’t have scroll depth (very likely the first hit of the visit or even other types of hits like clicks/custom links), then it gets counted as unspecified. So this doesn’t mean that 262 visits didn’t have scroll depth bucketed at all, it just means that in addition to having hits with scroll depth, 262 visits had at least one hit without scroll depth.

If you go into the filter icon beside the dimension name, there is a box where you can deselect unspecified. That is what you want to do in this case, since those unspecifieds don’t add anything to your report.

I agree with the others. It sounds like you are tracking “scroll depth” on your page views; but this wouldn’t apply to your actions. Also, I am assuming that you are using the Adobe Scroll Depth Plugin code, this won’t fire on the first hit, but will track the maximum depth reached on the previous page.

Between your first page views and your actions, you will have unspecified values.

Unless you are doing your own thing, on the initial PV tracking “0”, then having triggers as the user scrolls down the page and tracking the depth? But again, if you only added this to your PVs and custom scroll triggers, you probably don’t have it applied to all your other actions (form completions, orders, link clicks, etc).

I agree with Mandy, not including “unspecified” in your table is probably your best option, particularly if you want to use a metric like Visits that is part of ALL hits (even ones that don’t make sense for Scroll Depth context, and those “first” hits where there is not yet any scroll depth.)

I agree with ​@MandyGeorge and ​@Jennifer_Dungan. A couple of points to add that fully explain it, using the numbers from your own screenshots only:

1. Why Instances = 0% Unspecified but Visits doesn't:
   Instances only counts occurrences where the eVar was actually set — so by definition every instance falls into a defined bucket. Visits evaluates the eVar across the entire visit, including hits where scroll depth was never set (entry hit, clicks, form submits, etc.). Any visit with even one such hit gets tagged under Unspecified, alongside whatever scroll buckets it also touched.

2. Your own numbers prove the eVar changes value within a visit:
   Total Visits = 291, but your 5 bucket rows sum to 398 (146+47+60+43+102) — already more than the total, before Unspecified is even added. This confirms scroll depth is a Most Recent allocation eVar, and a single visit naturally passes through multiple buckets as the user scrolls further (0% → 26-50% → 76-100% in one visit = counted in all three rows).

3. What the 262 Unspecified actually means:
   Not "262 visits with zero scroll data" — it means 262 of your 291 visits (90%) contained at least one hit with no scroll value set, most likely the entry/page-load hit itself (scroll can only be measured after the page renders) plus any non-scroll actions (clicks, form submits) in that visit.

My Recommendation:
Use Instances, not Visits, as your primary scroll-depth metric — scroll depth is a page-level concept, and Instances avoids the ambiguity, Visits introduces for any per-page eVar.