Skip to content

Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
Minds Backend - Engine
Minds Backend - Engine
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
    • Insights
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 216
    • Issues 216
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 38
    • Merge Requests 38
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Security & Compliance
    • Security & Compliance
    • Dependency List
  • Packages
    • Packages
    • List
    • Container Registry
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Minds
  • Minds Backend - EngineMinds Backend - Engine
  • Issues
  • #855

Our Privacy Policy has changed, please visit https://about.gitlab.com/privacy to review these changes.

Closed
Open
Opened 4 days ago by Rami Albatal@ramialbatal
  • Report abuse
  • New issue
Report abuse New issue

Kite state transition from "Resurrected" to "New"

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:

Screen_Shot_2019-09-23_at_4.16.47_PM

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

Please solve the reCAPTCHA

We want to be sure it is you, please confirm you are not a robot.

Edited 1 day ago by Rami Albatal

Related issues
0

    • Discussion 3
    • Designs 0
    • Rami Albatal @ramialbatal changed the description 2 times within 4 minutes 1 day ago

      changed the description 2 times within 4 minutes

    • Rami Albatal @ramialbatal changed the description 3 times within 2 minutes 1 day ago

      changed the description 3 times within 2 minutes

    • Guy Thouret
      Guy Thouret @gthouret · 2 hours ago
      Developer

      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.

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply

    The one place for your designs

    Upload and view the latest designs for this issue. Consistent and easy to find, so everyone is up to date.

    2 Assignees
    Mark Harding's avatar
    Guy Thouret's avatar
    Assign to
    none
    Epic
    None
    None
    Milestone
    None
    Assign milestone
    None
    Time tracking
    No estimate or time spent
    None
    Due date
    None
    0
    Labels
    None
    Assign labels
    • View project labels
    None
    Weight
    None
    Confidentiality
    Not confidential
    Lock issue
    Unlocked
    3
    3 participants
    user avatar
    Mark Harding
    user avatar
    Guy Thouret
    user avatar
    Rami Albatal
    Reference: minds/engine#855