There isn't any documentation on this out of the box metric, so thought I'd post here to see if anyone has had experience using it.
Basically, we have a custom evar that captures the unique ID of visitors when they login to our mobile app.
Days since last visit ("DSLV") against the unqiue id evar however, seems to work only in some instances.
Client care advised that we need to set our id evar to 'never expire' (currently set to expire on visit) and that this was the issue.
However, further investigation reveals this information to be incorrect.
In production (with id evar expires on visit), DSLV against the id evar seems to work in some cases, even if the visitor has not returned since the last visit.
In development (with id evar never expires), DSLV against the id evar does not work if the visitor has not returned since the last visit, which seems counterintuitive. It also only works in some cases otherwise.
Curious to know if anyone has used this metric with good accuracy against a unique visitor ID. Thanks!
Days Since Last Visit is a dimension, not a metric. If a hit starts a new visit, it checks the timestamp of the last hit (if there is one), and buckets the visit based on the number of days in the past the previous hit was.
Are there any specific instances where you're seeing it work incorrectly?
Interesting that you mention it will only check on a new visit. As mentioned above, in production at the moment, we have multiple customer ids that last visited say 9 days ago, and have not visited since, yet Days Since Last Visit returns 9.
I don't see any specific instances where the dimension is not working correctly. Some customer ids we check have it recorded correctly, and others don't. I can't paste screenshots on the forum, but have sent them to client care and am waiting for a reply.