Note that there are some explanatory texts on larger screens.

plurals
  1. POGoogle Analytics - List event values per event label
    primarykey
    data
    text
    <p><strong>My current situation:</strong> </p> <p><em>I might have the complete wrong approach on this, so please tell me if I should do this differently.</em></p> <p>I send an event from my Android app to track DB load times. </p> <ul> <li>Event Category: 'DB'</li> <li>Event Label: 'DBLoadTime'</li> <li>Event Value: 2356 (Or however long the DB took to load in milliseconds)</li> </ul> <p>In Analytics I would like to get a table view of all the different load times, listed under each other. From the analytics <a href="https://developers.google.com/analytics/devguides/collection/gajs/eventTrackerGuide#Values">documentation</a> I could see that they seem to accumulate all the event values as they are received. This means I can only get the total value, or an average value. however, they also use a similar example to what I have, where they use the event value to store 'doanload time' for a video.</p> <p><strong>My question</strong></p> <ol> <li>Is this at all possible, or are values from similar event labels accumulated by default, and there is no way to get them listed as separate values.</li> <li>If it is not possible, how can I get this info? Maybe by sending the load time as an event label?</li> </ol> <p><strong>Why I need to know:</strong></p> <p>Highest value does not really serve me any purpose, as there might be one guy with one really slow device experiencing long load times, where the 2nd longest load time is already half of that. Average value does not tell me much either, as there are many people trying the app out, with just one or two records in the DB, which will always load fast.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload