Upload to S3
You can also provide in-app behavioral data via a scheduled job that uploads CSV files into an SFTP / S3 destination. This method is less optimal than SDK or S2S because it introduces a delay in information sharing, which will slightly affect performance, and allows more instances for data errors. We highly recommend Option A and B whenever possible.
- The column names should adhere to the mapping specified in the macros table above
- New events should be uploaded at a regular cadence - ideally hourly, and at least once a day.
- Files should be uploaded with the appropriate extension (.csv), but the specific file name does not matter.
- Uploaded files will be automatically deleted after 14 days.
The CSV files should be uploaded to an endpoint that will be established later.