Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.

Bug Filtering by app version not working

Discussion in 'Unity Analytics' started by Captain_Flaush, Jan 30, 2023.

  1. Captain_Flaush

    Captain_Flaush

    Joined:
    Apr 20, 2017
    Posts:
    63
    Hello,

    This is a very straight forward and 100% reproductible bug.
    Use case: I want to see the retention of my app for each version.

    Using legacy analytics:
    - I create a segment
    - I go to Data Explorer
    - D1 retentions displayed ok (around 28%)

    Using the new analytics system (method 1)
    - I open Dashboard->Retention tab
    - I filter by version
    - D1 retention displayed faulty (around 2.5%)

    Using the new analytics system (method 2)
    - I open Dashboard->Retention tab
    - I filter by audience
    - I create a new audience with the version condition
    - D1 retention displayed faulty (around 2.5%)

    Using Firebase the D1 retention is again displayed correctly for each version (around 28%)

    Another related issue regarding version filtering is session duration reporting.
    If I don't use any filter the session duration is reported ok.
    upload_2023-1-30_11-19-49.png
    Once I apply the version filter the session length displays faulty data.
    upload_2023-1-30_11-21-26.png


    I have tested this behavior in December and again this month using two app versions.
    We have enough DAU (around 3K) to make the statistics significant.

    Is there any bug report regarding this or any plan to fix this?
    Maybe the implementation of Analytics on my side is missing something? (I don't really see how though)

    Thanks a lot!
     
    Captain_Flaush, Jan 30, 2023
    #1

  2. RandolfKlemola

    RandolfKlemola

    Unity Technologies

    Joined:
    May 1, 2020
    Posts:
    118
    Hi Captain_Flaush,

    Thank you for reaching out to the support team! This is a really detailed, really well-written bug post. I really appreciate that! I've forwarded all of this over to our engineering team to get it fixed. I do not think it has anything to do with your integration but more with how the chart is filtering the Version data to display the chart.

    Best,
    Randy
     
    RandolfKlemola, Jan 31, 2023
    #2

  3. RandolfKlemola

    RandolfKlemola

    Unity Technologies

    Joined:
    May 1, 2020
    Posts:
    118
    Can you verify if your UGS Analytics shows a lot of events with the sdkMethod: UA1_SDKLESS? You can use this query, which will also highlight which Client Version is associated with which SDK Method.

    select 
    
    EVENT_JSON:sdkMethod::STRING, 
    
    CLIENT_VERSION, 
    
    count(*) 
    
from 
    
    events 
    
where 
    
    CLIENT_VERSION is not null 
    
group by 
    
    1,
    
    2;
     
    RandolfKlemola, Jan 31, 2023
    #3

  4. Captain_Flaush

    Captain_Flaush

    Joined:
    Apr 20, 2017
    Posts:
    63
    Hello,

    There are indeed a lot of events with the sdkMethod: UA1_SDKLESS
    Below the result for the last 3 versions:
    UA1_SDKLESS 0.7.32 308744
    UA1_SDKLESS 0.7.33 150672
    UA1_SDKLESS 0.7.34 22219

    I have also attached the results for the entire query.

    What does this mean?
     

    Attached Files:

    Captain_Flaush, Feb 1, 2023
    #4

  5. RandolfKlemola

    RandolfKlemola

    Unity Technologies

    Joined:
    May 1, 2020
    Posts:
    118
    Hi again Captain_Flaush,

    Okay, great. That is the cause of the issue that we're investigating. It's caused by the migration of Legacy Analytics not correctly identifying versions in the transition in the events used to populate those charts (mainly gameStarted & gameRunning).

    The bug has been written and we really appreciate your help.

    Best,
    Randy
     
    RandolfKlemola, Feb 1, 2023
    #5
    Captain_Flaush likes this.

  6. Captain_Flaush

    Captain_Flaush

    Joined:
    Apr 20, 2017
    Posts:
    63
    Do you have an approximate ETA for this fix?
    I would really love to move to the new analytics and stop doing segments that take a day to create and populate with the old one :D
    Thank you!
     
    Captain_Flaush, Feb 8, 2023
    #6

  7. RandolfKlemola

    RandolfKlemola

    Unity Technologies

    Joined:
    May 1, 2020
    Posts:
    118
    Hi Captain_Flaush,

    No ETA at the moment, but hoping to see it fixed over the next 2-3 weeks. I should make it clear that this issue is only caused by Legacy Analytics that are being filtered into UGS Analytics. It is not something that will occur for UGS Analytic events.

    Best,
    Randy
     
    RandolfKlemola, Feb 10, 2023
    #7