Timestamps and Custom Visitor ID

Avatar

Avatar

jorisdebeer

Avatar

jorisdebeer

jorisdebeer

26-02-2017

Hi,

I have a client who is setting a custom Visitor ID using the s.visitorID variable in their iOS and Android apps (SDK 4.x).

The will be setting the timestamp on every hit leaving the app.

They are keen to enable Timestamps option on the report suite, but have read the documentation that this is not supported, and that it can lead to out of order data.

Timestamps Optional

 

Important: If you are using Timestamps Optional, then do not set s.visitorID on data that is already timestamped. This can lead to out-of-order data and negatively impact time calculations (such as time spent values), attribution (eVar persistence), visit number/visit counts, and pathing reports.

 

  • Timestamps not allowed (setting s.visitorID supported)
  • Timestamps required (setting s.visitorID not supported)
  • Timestamps optional (setting s.visitorID supported but not on timestamped hits)

 

What is the reason for this limitation, and is it likely that this limitation will be addressed in the near future?

View Entire Topic

Avatar

Avatar

nickh86417692

Avatar

nickh86417692

nickh86417692

16-04-2019

I'd love an answer on this one too.

Does using s.visitorID on timestamped report suites force the processing to rely on hit_time_gmt rather than cust_hit_time_gmt? Depending on the answer, it may be worth it to have slightly out of order data, if it means we're able to see usage across multiple platforms by the same users.