# Statistics regarding registrations (native versus external)
**URL:** https://meta.discourse.org/t/statistics-regarding-registrations-native-versus-external/14442
**Category:** Feature
**Created:** [3 Abril , 2014 20:46 UTC](https://meta.discourse.org/t/statistics-regarding-registrations-native-versus-external/14442 "2014-04-03T20:46:08Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@AdamCapriola](https://meta.discourse.org/u/AdamCapriola)
#### Post date: [3 Abril , 2014 20:46 UTC](https://meta.discourse.org/t/statistics-regarding-registrations-native-versus-external/14442/1 "2014-04-03T20:46:09Z")
It would be nice to know which users register through one of the external options (Google, Twitter, Facebook, Yahoo, etc.) versus creating an account natively through Discourse. If I knew very few people were using the external options, I might remove some (or all) to make the login form simpler.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [3 Abril , 2014 21:49 UTC](https://meta.discourse.org/t/statistics-regarding-registrations-native-versus-external/14442/2 "2014-04-03T21:49:05Z")
Agreed, that would be a good thing to show in the admin dashboard at some point @neil.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [14 Agosto , 2018 07:33 UTC](https://meta.discourse.org/t/statistics-regarding-registrations-native-versus-external/14442/3 "2018-08-14T07:33:49Z")
I don’t think we really need this on the dashboard, but a custom report in `/admin/reports` makes sense. There are quite a few tables involved though, so reporting is not easy once plugins are involved.
@david I think we kind of forgot about this use case when we redid the interfaces. Not sure how we could swing this short of painfully iterating through every user.
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [14 Agosto , 2018 10:21 UTC](https://meta.discourse.org/t/statistics-regarding-registrations-native-versus-external/14442/4 "2018-08-14T10:21:33Z")
This is something that a new data structure could help with. I’ve written down what I was thinking of here for reference:
> [@Future Social Authentication Improvements](https://meta.discourse.org/t/future-social-authentication-improvements/94691):
>
> Discourse now has the ability to connect and disconnect different authentication providers to your account. This is good, but there is still more we can do. These are things I intended to do with my last round of improvements, but have not managed to complete before needing to move on to another project. Track ‘last used’ date for social login Log ‘connect’/‘revoke’ events in UserHistories [Provide statistics to administrators](https://meta.discourse.org/t/statistics-regarding-registrations-native-versus-external/14442/3) As @fantasticfears pointed out [here](https://meta.discourse.org/t/ability-to-connect-with-oauth-providers-when-user-is-registered/42457/3), features like this ar…
At the moment we could still implement this for core auth providers - just read the user\_ids from `{google,twitter,facebook,...}_user_info` tables. Plugins **tend** to use `oauth2_user_infos`, so that is achievable. Plugins that use their own data format in PluginStoreRows will be pretty much impossible to provide statistics for with the current structure.
---
### Author:  [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [4 Dezembro , 2025 11:10 UTC](https://meta.discourse.org/t/statistics-regarding-registrations-native-versus-external/14442/6 "2025-12-04T11:10:02Z")