Learn business growth with Google Analytics 4 Forums Google Analytics 4 Abnormal elapsed time measurements in GA4 for iOS

  • Abnormal elapsed time measurements in GA4 for iOS

    Posted by Aiden on 12 June 2022 at 6:54 pm

    Hey folks! So, we’re using GA4 on iOS for a bunch of things, one being to track how much time a user spends on each view. Oddly enough, it’s showing us times in terms of days, not minutes or seconds like we expected. Has anyone else bumped into this issue while using GA4?

    Lucas replied 9 months, 3 weeks ago 3 Members · 2 Replies
  • 2 Replies
  • Wyatt

    Member
    30 August 2022 at 1:42 am

    So, just to put it out there, the ‘Elapsed Time’ we’re talking about here is actually a total, not an average. Meaning, each time a user moves from step 1 to step 2 in the funnel, that time gets piled up, not averaged out. I’ve tried finding a way to check the average or median of Elapsed Time but came up with nothing, which is a bummer since I think an average would be way more useful than a total. And I don’t think there’s a way to see how many times this shift from step 1 to step 2 actually happened, so even if you wanted to, you can’t do the math to get the average yourself.

  • Lucas

    Member
    20 September 2022 at 6:24 pm

    It sounds like there might be a misunderstanding in interpreting Google Analytics GA4. Typically, “Engagement Time” is recorded in seconds which is the raw data sent from your app to Google Analytics. However, when you observe the it in your analytics console, it might default display to days for the sake of simplicity. This could potentially happen if the overall time recorded is very large. Moreover, there might be some conversion or standardization applied when processing and displaying data. You might want to dive deeper into customizing your view settings or creating more specific segments to monitor the particular user engagement in seconds or minutes as required. If this is consistently problematic and doesn’t align with your expectation, contacting Google support or browsing forums may provide a solution.

Log in to reply.