> ## 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.

# Which Data Connection Path Should I Use?

> Use this guide to choose the right Provalytics connection path for native connectors, warehouse data, recurring files, and custom sources.

## Overview

Provalytics supports more than one way to get data into the platform because client data rarely comes from one perfectly uniform source system.

Use this guide when you need to decide whether a source should be connected through a native platform connector, a warehouse route, a recurring delivery workflow, or a one-time file.

## Use a native connector when the platform is already supported

Use a native connector when the source already maps cleanly to a supported recurring connection such as:

* Google Ads
* Google Analytics 4
* Meta
* LinkedIn
* TikTok
* YouTube
* Shopify

This is usually the best fit when:

* the platform already has a supported connector path
* the data should refresh on a recurring cadence
* the source is a standard marketing or analytics system

Start here:

* [Connecting Data](/integrations/supported-connectors)

## Use Snowflake or BigQuery when the source already lives in a warehouse

Use a warehouse route when the client already maintains curated reporting tables and wants Provalytics to read from that environment directly.

Choose this when:

* the data is already structured in the warehouse
* the source is custom or non-conforming
* the upstream team prefers direct warehouse access over recurring files

Use:

* [Snowflake Delivery](/integrations/snowflake-delivery)
* [BigQuery Delivery](/integrations/shared-bigquery)

## Use S3 when the upstream team wants to push recurring files automatically

Use S3 Bucket Delivery when the client or partner wants a secure machine-to-machine handoff and can push a fresh file to the same location repeatedly.

Choose this when:

* the source is warehouse-derived or operational
* recurring files are already produced
* the team wants automated delivery without granting direct warehouse access

Use:

* [S3 Bucket Delivery](/integrations/s3-source-access)

## Use SharePoint or Google Sheets when the client already operates there

Use these routes when the data is already being managed in the client’s preferred collaboration tool.

Choose this when:

* the team already maintains structured files in SharePoint
* the team already maintains structured rows in Google Sheets
* the source is relatively stable and operational

Use:

* [SharePoint Delivery](/integrations/sharepoint)
* [Google Sheets Delivery](/integrations/google-sheets)

## Use recurring email delivery when a repeatable file process exists but a stronger connector is not practical yet

Use recurring email delivery when a team can send files or automatically retrievable links on a stable cadence, but the source does not justify a more direct connection path.

Choose this when:

* the source is file-based
* the process is repeatable
* a warehouse or bucket route is not practical yet

Use:

* [Recurring Email Delivery](/integrations/helpscout-file-feeds)

## Use manual uploads for one-time or exception cases

Manual uploads are best for:

* historical backfills
* one-time corrections
* special offline files
* onboarding situations where the recurring route is not ready yet

They are useful, but they are usually not the best long-term answer for recurring delivery.

Use:

* [Manual File Uploads](/integrations/manual-uploads)

## The simplest rule

* If the source is standard and supported, use a native connector.
* If the source is custom but already structured in a warehouse, use Snowflake or BigQuery.
* If the source is custom and delivered as recurring files, use S3, SharePoint, Sheets, or recurring email delivery.
* If the source is temporary or exceptional, use manual uploads.

If you are not sure, work with your CSR and start here:

* [Custom & Non-Conforming Data](/integrations/custom-and-non-conforming-data)