> ## Documentation Index
> Fetch the complete documentation index at: https://docs.invoca.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Signal File Uploads: Formatting & Data Prep

> Avoid the most common Signal file upload errors, most of which come from formatting automatically applied by spreadsheet software.

When you upload Signal insights or Marketing Data values to your Invoca account using file upload features, sometimes it takes extra effort to format your data correctly — often due to formatting edits made automatically by your spreadsheet software.

Here are a few practices to help you avoid formatting errors.

## Remove external formatting in your spreadsheets

Before saving your spreadsheet, select all cells and use the "remove formatting" option in your spreadsheet program.

## Timestamp formats

The following formats are supported for both `call_start_time` and `occurred_at_time`. All examples below correspond to a date and time of April 11, 2016 at 1 PM Pacific Time.

| Format           | Description                                                                                                                                                            | Example                                                                                                                                                           |
| :--------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Epoch            | A 10-digit timestamp in UTC seconds since 1/1/70 (Unix `time_t`). UTC milliseconds since 1/1/70 (the JavaScript default) are also supported, as a 13-digit start time. | `1460404800` (10 digits) or `1460404800000` (13 digits)                                                                                                           |
| Compressed       | A 17-digit timestamp always parsed in UTC, in the format `YYYYMMDDHHMMSSsss`.                                                                                          | `20160411130000000`                                                                                                                                               |
| ISO 8601         | Timestamp with a +/- UTC offset or "Z" to indicate UTC. Milliseconds are optional. Format: `YYYY/MM/DDTHH:MM:SS.sss+hh:mm`                                             | `2016/04/11T23:00:00.000+03:00` (UTC+3), `2016/04/11T13:00:00.000-07:00` (UTC-7), `2016/04/11T20:00:00.000Z` (UTC), `2016/04/11T13:00:00-07:00` (no milliseconds) |
| Excel Compatible | Timestamp parsed in the timezone of the OAuth token's associated network. Milliseconds are optional. Format: `YYYY/MM/DD HH:MM:SS.sss AM/PM`                           | `2016/04/11 13:00:00.000 PM`, or `2016/04/11 13:00:00 PM` (no milliseconds)                                                                                       |

The file upload interface includes a timezone dropdown that lets you select which timezone this format is parsed in. Use this format for Excel date cells: `yyyy/mm/dd hh:mm:ss.000 AM/PM`.

## Other fields

* **calling\_phone\_number:** format as ANI in E.164 format (`+country national_number`) — for example, `+18885551212`.
* **advertiser\_id\_from\_network** and **advertiser\_campaign\_id\_from\_network:** these columns are only used to restrict Signal insights to calls from certain partners or campaigns. In most cases, you can leave them blank.

## Bundled calls

If reporting a Signal on a bundled campaign using `transaction_id` as the matching identifier, we recommend reporting on the final/destination campaign. If reporting a Signal on a `call_record_id` associated with a bundled call, the Signal applies to the last call leg associated with the child campaign in the organization reporting the Signal — this allows payouts to propagate appropriately.

If `transaction_id` or `call_record_id` aren't available, matching is still possible using `call_start_time` with an additional optional parameter, such as call duration or calling phone number.

## Where to go next

* [Signal File Uploads: Conversion Importing](/s/article/signal-file-uploads-conversion-importing)