Skip to content
More support
Contact us
  • There are no suggestions because the search field is empty.

Why are New Member counts different from what I see in ABC CRS reports?

Please note that we query the member and member agreement APIs each morning for activity from the previous day. This means, for example, if you book a new member on the 10th you won't see it in Easalytics reports for the 10th until the next day the 11th.

Aside from the above, the 4 most common reasons for a New Member count discrepancy are listed below. Whatever the case, these differences tend to "correct" themselves over time and are likely to impact only narrow time ranges (daily, weekly) or where a member registration process overlaps last day of the month/first day of the month.

1. Your ABC agreement approval queues are set to require manual posting rather than auto-posting. The auto-posting option in ABC will regularly throughout the day, ensuring CRS contains the most up-to-date Posted new member counts. Easalytics queries ABC's API each morning and gets all Approval and Posted activity from the previous day. If you are posting agreement approvals manually on a less frequent basis, there may be an equivalent lag in updating new member counts in CRS.

2. You have provided us with Member Types you want excluded from Easalytics reports. CRS reports do not exclude any Member Types, so if you are excluding any Member Types in Easalytics reports any New Members in the excluded Member Types will not be counted.

3. CRS New Accounts/Members reports use the NewDate, while Easalytics New Members reports use the SinceDate. SinceDate is the date the New Member record is created in CRS, and is the only account start date made available to us via the CRS API.

4. CRS reports use the most recent member status that is applicable in your selected time range (see CRS document below*), ignoring any previous statuses. Easalytics stores all statuses that occurred during a time range, and can report on any relevant status that occurred at a specific point in time. 

For example, let’s look at two scenarios for a July 1 to July 30 time range:

  1. Member A joins on July 1st and cancels on July 20th
  2. Member B joins on July 1st and rewrites their contract on July 20th

 If you run reports in CRS and Easalytics for July 1st to July 1st:

  • CRS will count Member A and Member B as New Members
  • Easalytics will count Member A and Member B as New Members

However, if you run a report in CRS and Easalytics for July 1st to July 30th :

  • CRS will not include Member A or Member B as New Members because their status has changed from New to Cancel or Continual Rewrite during July, and CRS reports can look only at current status
  • Easalytics will include Member A and Member B, because Easalytics maintains historical data showing that Member A and Member B became New Members during the month of July, regardless of current status.

We believe this results in a more accurate count of New Members acquired during a given time frame. A new member who cancels was still a new member, and their loss will have a corresponding entry in the attrition report. A new member who rewrites soon after joining should not be excluded from a New Members report just because they changed their membership plan.

 

*From CRS New Accounts Help Doc:

Note: The member status will reflect the most recent member status on file during the selected time period and will not show all applicable statuses. For example, a member may join the club on the first day of the month and have a status of New. On the 20th day of the month, the member may move to RWC (continual rewrite) status. If you generate the report to include data for the first through the fifth day of the month the member's status will be New. If you then generate the report the include data for the first through the last day of the month, the member's status will be RWC (continual rewrite). Only the most recent status available as of the End Date (selected on the parameter page) will be displayed.