Total daily count with deduplication logic and timezone adjustment
Events exported via pipelines (i.e. raw exports) can contain duplicates. Deduplication should be performed using 4 event properties:event_name, time, distinct_id, and insert_id (docs here). This is an example of a total daily count, converted to a specific timezone and deduplicated.
Unique user count with user ID resolution
Raw events may contain the originaldistinct_id associated with the user at the time of the event instead of the final canonical distinct_id for the user after authentication. The mp_identity_mappings_data_view contains mappings of the original distinct_ids to the resolved ones (i.e. canonical distinct_ids). You can use this mapping to make sure that the unique users calculations account for ID management and therefore more accurate.
Top 20 events by volume
Querying duplicate events
Raw exported events can contain duplicates. You can use these 4 event properties to identify duplicates:event_name, time, distinct_id, and insert_id (docs here). This is an example of a query you can use to identify duplicate events in your raw data.