Many users are moving from "Resurrected" to "New".

Example of users with this pattern in August 2019:

+-------------------+-------------------------------+
|user_guid_kite     |journey_string                 |
+-------------------+-------------------------------+
|1003452005647130643|resurrected, new, curious, cold|
|1003452092720881668|resurrected, new, curious, cold|
|1003452215974699011|resurrected, new, curious, cold|
|1003452303409160198|resurrected, new, curious, cold|
|1003452584448499723|resurrected, new, curious, cold|
|1003452662076678154|resurrected, new, curious, cold|
|1003452714325123076|resurrected, new, curious, cold|
|1003452818838790156|resurrected, new, curious, cold|
|1003452841710329863|resurrected, new, curious, cold|
|1003453225631752204|resurrected, new, curious, cold|
|1003453273140633602|resurrected, new, curious, cold|
|1003453281386635271|resurrected, new, curious, cold|
|1003453356783443971|resurrected, new, curious, cold|
|1003453479206789136|resurrected, new, curious, cold|
|1003453534567407624|resurrected, new, curious, cold|
|1003453692046745605|resurrected, new, curious, cold|
|1003453723172675588|resurrected, new, curious, cold|
|1003454204951404556|resurrected, new, curious, cold|
|1003454372992000012|resurrected, new, curious, cold|
|1003454424493858820|resurrected, new, curious, cold|
+-------------------+-------------------------------+

If we focus on the first user for example, we can see the follow:

For reference check the kite records: 1003452005647130643-1564617600000 (1st of August 2019, resurrected), followed by 1003452005647130643-1564704000000 (2nd of August 2019, new)

After we do the potential user's analysis, we need to make sure that kite is working properly.

There's this bug as reported by Rami

And there are also the gaps in the data. Every user should have a entry for each day of activity until they drop off the map.

Assigning this to @ramialbatal first so he can get together any issues he was having with the current kite algorithm

So, the way we calculate new users might be the source of this false positives

A user is marked new based on the timestamp of their guid compared to the past 24 hours when the job is run

A user is marked resurrected if their bucket has activity for the first day

All the logic for these lives in UserActivityBuckets.php

changed the description

changed the description

Resurrected state is 1 day of activity within 7 day period and that day is the most recent day.

New state is determined by the guid being within a range of guids that represent the 24 hours up to the reference day start.

This makes sense now. The new state is only seen during the second day, during the first day if there is activity on that day it actually fits the logic for resurrected so there would be a transition from resurrected -> new.

This is still the case after the changes I have made because I preserved the flawed new state logic. It's also a sporadic state to test because it's only seen when a new user is created.

added 1 deleted label

added scoped label

added scoped labels

@brianhatchet can you chime in here?

removed 1 deleted label

added scoped label

assigned to @brianhatchet

added scoped label and automatically removed label

added scoped label and automatically removed label

added scoped label and automatically removed label

unassigned @gthouret

unassigned @markeharding

unassigned @brianhatchet

added 1 deleted label

added scoped label and automatically removed label

changed weight to 4

changed time estimate to 4h

@gthouret we going to need to get the flawed logic fixed here to help out @ramialbatal 's data initiative.

added scoped label and automatically removed label

added scoped label and automatically removed label

assigned to @edgebal

changed weight to 8

changed the description

changed time estimate to 1d

added scoped label and automatically removed label

added scoped label

changed milestone to %Sprint:01/29 Abatic Aenome

added to epic &32

@brianhatchet I have checked the flows indeed the Resurrected --> new transitions is a problem... no baps was found in the last couple of months. The logic of the state transitions themselves, especially with the curious states is still a bit problematic for me. We discuss this asap.

changed the description

@brianhatchet

assigned to @eiennohi

unassigned @edgebal

added scoped label and automatically removed label

changed milestone to %Sprint::02/12 Bartone Baboon

added scoped label and automatically removed label

unassigned @eiennohi

removed label

removed milestone

Removing this from sprint until we figure this out in more detail.

changed milestone to %Sprint::02/26 Calculated Cricket

added scoped label and automatically removed label