Overview
Participants contribute total bookings counts for a number of key metrics. Counts are broken down by zipcode + effective_start_date + effective_end_data.
In the event that you want to contribute player participation data, ie how many players have played during the collection period, use the following fields:
unique_player_count_per_facility
unique_player_reserved_court_count
Please escape any special characters such as embedded quotes with a '\' (backslash) before including it in any field in the file. See Special Characters
File Submission Attributes
The following criteria applies to the data submissions
Attribute | Detail |
|---|---|
Frequency | Monthly |
Timeframe to included | Cummulative Year to Date based on Reservation date |
Inclusion Criteria | Only US Zipcodes should be included |
Effective Start/End Dates | Should be based on Reservation Date |
Aggregation Grain | effective_start_date, |
File Name Convention
Player files use the following naming convention
BOOKINGS-[SOURCENAME]-[YYYYMMDD].csv
Where:
SOURCENAME: The contributor name assigned by USTA.
YYYYMMDD: Effective date of contribution
Column Definitions
The following table lists the fields and formats.
Field | Required/Optional | Identifying | Format | Description | |
|---|---|---|---|---|---|
| 1 | source_name | Required | Yes | Text | Contributor (USTA will assign) |
| 2 | zip_code | Required | Yes | 5 digit zipcode - must include any leading zeros | Postal code |
| 3 | effective_start_date | Required | Yes | YYYY-MM-DD | Start of reported data (Reservation date), |
| 4 | effective_end_date | Required | Yes | YYYY-MM-DD | End of reported data (Reservation date) - should always be the last day of the reporting month, ie 2023-10-31 |
| 5 | game_type | Required | Yes | Text | TENNIS/PICKLEBALL |
| 6 | facility_id | Required | Yes | Text | Unique id (or name) assigned by the participating vendor for the facility |
| 7 | unique_player_count_per_facility | Optional | No | Number | Unique players based on aggregation grain. Includes unique players for court reservations, event reservations and lesson reservations. |
| 8 | unique_player_reserved_court_count | Optional | No | Number | Unique players based on aggregation grain. Includes unique players for court reservations only. |
| 9 | unique_player_reserved_event_count | Optional | No | Number | Unique players based on aggregation grain. Includes unique players for event reservations only. |
| 10 | unique_player_reserved_lesson_count | Optional | No | Number | Unique players based on aggregation grain. Includes unique players for lesson reservations only. |
| 11 | court_reservation_count | Optional | No | Number | Total count of court reservations based on aggregation grain. (Includes repeats by individuals) |
| 12 | event_booking_count | Optional | No | Number | Total count of event reservations based on aggregation grain. (Includes repeats by individuals) |
| 13 | lesson_booking_count | Optional | No | Number | Total count of lesson reservations based on aggregation grain. (Includes repeats by individuals) |
Example
BOOKINGS-ACTIONSPORTS-20240620.csv
Where:
Source Name: ACTIONSPORTS
Effective Date: 2024-06-20
source_name, zip_code, effective_start_date, effective_end_date, game_type, facility_id, unique_player_count_per_facility, unique_player_reserved_court_count, unique_player_reserved_event_count, unique_player_reserved_lesson_count, court_reservation_count, event_booking_count, lesson_booking_count ACTIONSPORTS, 10577, 2023-01-01, 2023-12-31, TENNIS, 201812345, 5000, 3210, 55, 450, 7250, 55, 775