Days since last visit -- A userID must have a single day as a last day since last visit. But I am seeing UserID is 0days,1days, 2days,,,,, how come this ?

[#1]

Hi Team,

I am trying to pull DaySinceLastVisit(DSLV) for a userID. As per the DSLV, a userID must have a day/days since last visit, only one row of data may be 0day or 1 day or 2 days. But I am seeing in the report, same userID have 0day,1day, 2day,... My question is how come a UserID have multiple DSLV values? Please help me.

Thanks,

Dinesh 

[dinesh_b_kumar_]

Hi Dinesh,

I believe the issue is related, probably, to your date range. If you have a long date range, the dimension will show all the hits associated with the user ID. Have a look in the example below:

Because my date rage is almost a month of data, I'm pulling all the hits associated, to this user, with the "days since last visit" as a dimension.

This might be the reason you're seeing multiple figures in the dimensions.

[dinesh_b_kumar_]

Sorry, I am not convinced with the answer. I am expecting when a user visit in any date range, DaysSinceLastVisit should report the latest visit day. Otherwise DSLV is not serving the purpose. This issue holds good for DaysSInceLastPurchase. Please rethink & help me.

PFB the screen shot, where date range is for 1 day (Mar23), still there 0days, 1days,2days....  for the user. how come?

[ForgotPassword4Times]

This is the correct response.

I think it is helpful to interpret this as its a database. When a new visit is instantiated for the visit, the following math happens Round(today-day of last visit).

This happens for each visit, which is why a user with 3+ within a time period would have 2 + values (the first visit wouldn't have a days since, because its the first time ever). This value is not dynamically generated at report run, rather produced at the time of the hit.

[ForgotPassword4Times]

This is the correct response. I think it is helpful to interpret this as its a database. When a new visit is instantiated for the visit, the following math happens Round(today-day of last visit).

[dinesh_b_kumar_]

Sorry, again not convinced with the answer. Once (today-day of last visit) = 0(if visit exist) then no need to check for other values. What you say? if you agree then please do the needful changes in the DSLV calculations. This is applicable to DaysSinceLastPurchase numbers too.

[ForgotPassword4Times]

Its also possible that if this is based on an eVar the user might be using multiple devices or browsers

[dinesh_b_kumar_]

Even though the User use different devices, each device will have unique visitor ID specific to each device as we don't have implemented MCID. So DSLV values should be independent of device type or browser type. Am I correct?