Are “sites” and “modules” represented in a Losant application as Experience Groups, or are you delineating these using some other mechanism (i.e. device tags)?
Regardless, I’m not sure there are any additional details I can provide, as the highest level of granularity we can provide for usage statistics using the instance APIs is per application. We made that decision with the original rollout as a way of balancing end user privacy with the billing needs of the solution provider (i.e. the instance).
Like I stated originally, if a member of your instance also has access to the application(s) in question - as in, they are also members of the organizations holding the applications - then you can get a higher level of granularity using some of the endpoints I previously mentioned. That can get a little messy given that a device can be in multiple experience groups but is not necessarily so.
We have a feature request in the works for returning the number of devices associated with a given experience group - directly or as members of child groups - but not payload counts. I will add a feature request to also return payload counts broken down per group, but I can’t provide a timeline on when that will be delivered. We’ll have to do some thinking on our end as to where to log a payload in the cases where a device appears in multiple groups, as well as what counts as a payload to charge to a given gruop (experience endpoint requests to fetch data associated with a device? Workflows that run as a consequence of state / connection events? And so on.)