Calculated Metrics at a Visit Level (Approx Count Distinct)

Great news Jen, thanks so much for the update! 

Good news - this will be fixed Oct 30 (next week). Distinct Count will no longer count "unspecified" as 1.

Bump and a +1 for this - is there a fix planned for this yetjen.lasser​​?

tbh i think a huuuuuge number of people will just be making this mistake and not realising it counts unspecified - which will be very skewing, given it's usually by far the largest single value in any dimension.......not sure i would have been comfortable letting this one run in the wild with this bug for so long if i were you guys!

(P.S. When this feature works properly it's going to be AWESOME!!!  just keen to see it count properly.  )

I will try to remember to update this thread. For sure though, we will put the update in our release notes. We don't have a scheduled release date for the "unspecified" improvement yet though.

Hi Jen,

When this change is implemented, do you mind updating this thread so I can modify my segments?

thanks!

dbachota​ - while we look into the best way to remove "unspecified", here is how you can build you segment to workaround the issue. This example is looking for 3 items to exist

It looks like it is counting unspecified for eVars - we will get this fixed. Props, marketing channels, etc are fine though. Thanks for raising this!

Can you please verify this?  I looked at a visit of my own and it was in the "Visit contains 3 distinct count of Evar" segment.  I then broke it down by the Evar and saw Value 1, Value 2, and Unspecified.  It seems that "unspecified" is being counted as a distinct value in the logic.

Thank you!!

It doesn't count unspecified values, since "unspecified" means there is no value. For example, in an eVar report, if you see unspecified, in-market, and out-of-market, the distinct count would be 2.

This is awesome!

Is there a way for the count distinct to ignore "unspecified" values?

My current solution is nested segmentation:

Any better methods?