Just looked into the member counts on the dashboard, they're wrong as it's more than the last 30 days, it's usually last month + up until today and if that range covers more than 1 month it double counts new members if they have a payment for each of those months crossed in that range.
How we count new members:
query is made between a start and end date range
user been created within the requested date range
joins payments made by the user that are within the date range
counts effective the number of payments new users have made in the range (this is a bug when the range crosses more than 1 month)
start date as: now minus 30 days = whichever month that is => start of that month, e.g. Feb 26 minus 30 days = Jan 28 => start of Jan is Jan 1st.
end date as : now
making the request: Jan 1st to Feb 26th in this example, crossing 2 months, typically members make a payment each month, as the date gets more near the end of the current month, it's highly probable all new members in the last 2 months are double counted.
laftho
commented
4 years ago
Just looked into the member counts on the dashboard, they're wrong as it's more than the last 30 days, it's usually last month + up until today and if that range covers more than 1 month it double counts new members if they have a payment for each of those months crossed in that range.
How we count new members:
The dashboard makes a request as:
I'll make a fix for this and review the other metrics to make sure we aren't double counting in other places.