File-Based Individual Flexible Contributions
Overview
Participants contribute total counts for a number of key metrics. Counts are broken down by zipcode + effective_start_date + effective_end_data + id_type + customer_id
Incremental individual counts. Reporting periods (effective start and end dates) should not overlap but be continuous.
Please escape any special characters such as embedded quotes with a '\' (backslash) before including it in any field in the file. See https://ustadigital.atlassian.net/wiki/spaces/DEV/pages/39648460801
File Submission Attributes
The following criteria applies to the data submissions
Attribute | Detail |
|---|---|
Frequency | Quarterly |
Timeframe to included | Incremental |
Inclusion Criteria | Only US Zipcodes should be included |
Effective Start/End Dates | Should be based on date of Service. If a year end occurs within the start - end dates this should be broken into 2 files - Start to end of year (12/31) and then start of year to end of reporting period. |
Aggregation Grain | effective_start_date, effective_end_date , id_type, customer_id, zipcode |
File Name Convention
Flexible files use the following naming convention
FLEXIBLE-INDIVIDUAL-[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 |
|---|---|---|---|---|
source | Required | Yes | Text | Contributor (USTA will assign) |
effective_start_date | Required | Yes | YYYY-MM-DD | Start of reported data (Date of of service),The start date of the reporting period. For an incremental based data set this should be the day following the last file’s effective end date. |
effective_end_date | Required | Yes | YYYY-MM-DD | End of reported data (Date of Service) - should always be the last day of the reporting month. ie 2026-03-31 |
id_type | Required | Yes | Text | Type of customer id presented - USTA or Anonymous. |
customer_id | Required | Yes | Text | Customer USTA # or Anonymized customer id. This should be a persistent id of the customer if anonymized. |
zip_code | Required | Yes | Text | 5 digit zip code - must include any leading zeros. Zip code of the customer. |
partner_type | Required | no | Text | Indicates the category or nature of services provided by a partner (streaming, tennisball, smart court, etc) |
court_type | Required | no | Text | identifies the type of court ie Tennis, paddle, pickleball, other, not applicable |
Dim_1 | Optional | no | Text | any other field needed for segments. if not used then should default to not applicable (ie demographics). If play based this could be the zip code of where play occurred. |
Dim_2 | Optional | no | Text | any other field needed for segments. if not used then should default to not applicable (ie demographics) |
Dim_3 | Optional | no | Text | any other field needed for segments. if not used then should default to not applicable (ie demographics) |
Count_Type | Required | no | Text | What the partner is counting (ie resurfaced_court_count, camera_activation_count, player count, facility count, average_ frequency_ of_ people_ activation, etc) - USTA will assign values based on desired measures from vendor |
Count | Required | no | number | count of the count_type |
Example
FLEXIBLE-INDIVIDUAL-[Source Name]-[Effective Date].csv
FLEXIBLE-INDIVIDUAL-ACTIONSPORTS-20260331.csv
Where:
Source Name: ACTIONSPORTS
Effective Date: 2026-03-31
source,effective_end_date,effective_end_date,id_type,internal_id,zip_code,partner_type,court_type,Dim_1,Dim_2,Dim_3,Count_Type,Count
ACTIONSPORTS,2026-01-01,2026-03-31,zip_code,32827,32827,Smart Court,Tennis,,,,unique_facility_count,25
ACTIONSPORTS,2026-01-01,2026-03-31,zip_code,32827,32827,Smart Court,Tennis,,,,unique_player_count,100
ACTIONSPORTS,2026-01-01,2026-03-31,facility,facilty1234,32827,Smart Court,Tennis,,,,unique_player_count_per_facility,25
ACTIONSPORTS,2026-01-01,2026-03-31,facility,facilty1234,32827,Smart Court,Tennis,,,,unique_court_count_per_facility,5
On This Page:
More Reading: