# Set Up Integration

We support seamless integration with the major cloud providers. You can choose the one that fits your current technology stack:

* **Amazon Web Services (AWS):** We can grant access to our S3 bucket or replicate data directly to yours.
* **Google Cloud Platform (GCP):** We upload files directly to your Google Cloud Storage buckets.
* **Microsoft Azure:** We upload files directly to your Azure Blob Storage containers.

{% hint style="info" %}
Open Loyalty generates **daily** data exports, providing **delta changes** for the previous day in a CSV format. For detailed information about each export type, refer to the following article:

<https://help.openloyalty.io/technical-guide/s3-bucket-data-exports/data-structure-and-types>
{% endhint %}

{% hint style="success" %}
The export frequency is set to daily to ensure consistent and timely access to the data for all our customers.
{% endhint %}

{% hint style="warning" %}
There is one report set for the environment, regardless of the number of tenants created. There is a unique identifier (`tenantId`) for all the reports. Then you can create pipelines to further split the data per tenant.
{% endhint %}

***

## Key Considerations

* **Security & Least Privilege**: Regardless of the platform, ensure that the credentials you provide (Service Accounts, SAS Tokens, or IAM Roles) are configured with the principle of **least privilege**. You should grant only the specific "Write" or "Upload" permissions required for Open Loyalty to deliver the files, restricting read or delete access unless necessary for your internal processes.
* **Cloud Infrastructure Costs**: While Open Loyalty provides the data export feature, **your cloud provider will bill you** for the storage space and API write operations associated with receiving these files. We recommend monitoring your usage and configuring lifecycle rules (e.g., automatically moving older files to "Cold" or "Archive" storage tiers) to optimize expenses.
* **Pipeline Timing**: Exports are generated daily after midnight UTC (or another timezone, once you raise such a need with the Support Team). When setting up your downstream ETL pipelines or BI data refreshes, ensure they are scheduled to run **after** the data delivery window to capture the latest delta files.

## Learn more about

Find detailed guides on how to configure the integration for data exports for one of the following cloud providers:

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Amazon Web Services (AWS)</strong></td><td><a href="set-up-integration/amazon-web-services-aws">amazon-web-services-aws</a></td></tr><tr><td><strong>Google Cloud Platform (GCP)</strong></td><td><a href="set-up-integration/google-cloud-platform-gcp">google-cloud-platform-gcp</a></td></tr><tr><td><strong>Microsoft Azure</strong></td><td><a href="set-up-integration/microsoft-azure">microsoft-azure</a></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.openloyalty.io/technical-guide/data-exports/set-up-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.