Better analytics needed

We’ve got an audio training app, and would need to assess which audio sessions are mostly being consumed by users, and which are not. I cannot find the data in Adalo or Mixpanel analytics. As it’s a pretty basic requirement, I assume the data is there but I just can’t find it. Any ideas?

I feel the whole analytics side is a big letdown as it currently is.

Hi @Mikko ,

I have read somewhere that mixpanel only track the screens regardless the data passed through inside it.

So in your use case, it might need additional collection as a log, every time users go to that session, do action create to this log.

Hi Yongki, thanks for the very useful insight!

It’s a big ask, but would you be able to help me with the specifics (I’m fairly new to Adolo, with a non-technical background), and not sure how to make this happen…

I need to look at the database setup first, all our logic depends on it.

Ok, would you like to? Is there a way?

Take multiple screenshots inside the collection.



Does this help?

You can create additional collection called Listened Exercises and the fields are

  1. Name, this is default, can be used as concatenated of logged in user>full name (or email), current exercise.trainer>full name and current exercise.sports>name
  2. Listening user, relationship to users, multiple listened exercises to 1 user
  3. Listened Exercise, relationship to Exercises, multiple listened exercises to 1 exercise
  4. (optional) Trainer, relationship to trainers, multiple listened exercises to 1 trainer (as a shortcut and duplication)
  5. (optional) Sports, relationship to sports, multiple listened exercises to 1 sport (as a shortcut and duplication)

1 basic field, 4 relationship fields

At Exercises collection, you can add numbers field called counter, this is where we add +1

At Trainer collection, you can add numbers field called counter, this is where we add +1 (same logic)

At Sports collection, you can add numbers field called counter, this is where we add +1 (same logic)

Now for the logic on screen,
Whenever user play the audio session, add action to create this new collection, Listened Exercises and fill the relevant information with current available data.

Add another action to update +1 at Exercises collection, with syntax current exercises>counter+1 (this will hold life time value of this exercise is played by users)

Add another action to update +1 at Trainer collection, with syntax current exercises.trainer>counter+1 (this will hold life time value of all exercises by this trainer is played by users)

Add another action to update +1 at Sports collection, with syntax current exercises.sports>counter+1 (this will hold life time value of all exercises by this sport is played by users)

So, when we want to know which exercises are most listened, we can use count for this new collection, or as backup field, we have counter in the exercise collection that hold life time value of how many user visit this exercise, but if we want to go deeper who are the users, we should use count in the listened exercise collection.

The same logic goes for trainers and sports, they have their own life time value that can work as subtotal of the new collection.

1 Like

Oh wow, this is so helpful! Thank you so much, takes me a while to decode but should be able to implement. I’m very grateful, @Yongki!

1 Like