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

# S3 Bucket Delivery

> Learn how recurring data can be pushed to a Provalytics-managed S3 bucket for automatic daily retrieval.

## Overview

S3 Bucket Delivery is the recurring push-to-Provalytics option for teams that want to send data from a warehouse or another custom source into the platform.

Provalytics provides a unique S3 bucket destination, and the platform automatically retrieves the file each day.

This is a strong fit for:

* custom marketing data
* custom conversion data
* warehouse-derived files
* recurring operational feeds that should land in Provalytics automatically

## How it works

When this route is enabled, Provalytics provides the bucket path and access details needed for the upstream system to deliver files securely.

If you want this delivery pattern, contact your CSR or email [help@provalytics.com](mailto:help@provalytics.com) and Provalytics will provide the setup details.

## What it is best for

S3 is useful when:

* a client or partner already produces recurring files from a warehouse or operational system
* the upstream team wants a secure machine-to-machine handoff
* the file should be retrieved automatically every day
* the source is not best connected through a direct app connector

## Why teams use it

S3 works well for:

* recurring warehouse exports
* custom marketing or conversion feeds
* centralized operational pipelines
* secure automated file delivery

It is especially useful when the upstream team wants a secure push destination rather than giving direct access to their systems.

## Upload instructions

1. Upload CSV files to the exact S3 path provided by Provalytics.
2. Preferred format: UTF-8 CSV.
3. Keep the same columns and file structure each day.
4. Preferred delivery pattern: overwrite the file daily at the same path.

## Recommended operating model

* Send a fresh complete CSV file each day.
* Overwrite the same file path daily.

This keeps the retrieval pattern reliable and makes downstream ingestion much easier to manage.