In addition to the enriched customer file (the OUT file), LaunchPad provides a STATS file in JSON format. This file provides a high-level summary of the append process, key metrics, and any errors that may have occurred.
Here’s an example of the contents of the STATS file:
{
"client_name": "NYCOutdoors",
"file_name": "LEAP_V1_SPORTS_#_Customers_20250401.csv",
"start_date": "2025-09-18 12:42:25",
"records_read": 12045245,
"records_written": 12045245,
"status": "OK",
"error": null
}
Opening the File
The STATS file can be opened in a plain text editor such as Notepad on Windows, TextEdit on Mac, or Notepad++. When opened, the JSON may appear condensed and difficult to read. To make it easier to review, we recommend using a free online tool like jsonformatter.org. Simply paste the STATS file contents into the formatter, and it will automatically organize the data with indentation and highlighting.
Breaking Down the Fields
Every STAT file has the following fields/nodes.
| Field | Description |
|---|---|
| client_name | Relays the client code provided in the file name. This helps confirm attribution and troubleshoot across multiple accounts. |
| file_name | The original file name that was ingested. Use this to match the STATS file to the corresponding input and output files. |
| start_date | The timestamp at which the file was ingested. |
| records_read | The total number of records LaunchPad received from your input file. Confirms full ingestion. |
| records_written | Number of records successfully written to the output file. Check this while the file is being processed to get an idea of its progress. When completed, it will match the records_read value. |
| status | “OK”: The file has been successfully completed. “In-Progress”: The file is currently being processed. “Error”: An error has occurred with the file naming or format. |
| error | Provides error details if the job failed. A blank/null value means no errors were encountered. If populated, it will contain a descriptive error message. |
Error Encounter
The STATS file will report any show-stopping errors related to the file’s naming or formatting. For full file specifications, visit this link.
If an error occurs, the STATS file will contain three values under the “error” node/field. For example:
{
"client_name": "LEQA",
"file_name": "FILE_V1_SPORTS_#_Customers_20250401.csv",
"start_date": "2025-09-26 13:42:48",
"records_read": 0,
"records_written": 0,
"status": "ERROR",
"error": {
"code": 410,
"description": "The file name does not match the expected LEAP format",
"recommendation": "Check the LEAP documentation and ensure that the correct naming format is used, please refer to https://help.launchpadasap.com/incoming-file-specifications/ or contact support@launchpadasap.com."
}
}| Field | Description |
|---|---|
| error.code | Numeric error code that corresponds to the specific type of failure. |
| error.description | A human-readable explanation of the error. |
| error.recommendation | Guidance on how to resolve the issue. |
Helpful Tools
If you open the STATS file in a plain text editor, the JSON may appear condensed and difficult to read. To make it easier to review, we recommend using a free online tool like jsonformatter.org. Simply paste the STATS file contents into the formatter, and it will automatically organize the data with indentation and highlighting.