> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/sync-with-your-data-warehouse.md).

# Sync with your data warehouse

Connect a cloud data warehouse and keep profiles and events in step with it.

## Your goal

Connect the warehouse where your data already lives, and decide what the platform does with it: read from it to feed the datamart, or treat it as the source of truth for the whole datamart.

## Expected outcome

A declared warehouse connection, a synchronisation strategy per table that matches how that table changes, and - if the warehouse is your source of truth - collection and computation running against it.

{% hint style="info" %}
This feature is in Alpha. Contact your account manager to learn more.
{% endhint %}

## One connection, two jobs

The same warehouse connection serves two quite different arrangements, and which one you are in is set by the datamart's [deployment mode](/setup-and-monitor/plan-and-integrate/choose-your-deployment-mode.md).

{% columns %}
{% column %}

### A collection route

The datamart holds its own data, and the warehouse is one of the routes that feeds it, alongside real-time tracking and batch imports.

This is the Hosted arrangement, and it is what the rest of this page describes.
{% endcolumn %}

{% column %}

### The source of truth

The warehouse holds the data of record. Live tracking is written there, segments and the identity graph are computed there, and the platform stores nothing long-term.

This is a Hybrid or Zero-copy deployment. It adds two jobs to the ones below.
{% endcolumn %}
{% endcolumns %}

## Decide what to set up

{% stepper %}
{% step %}

### Which warehouse, and what access you grant

The supported providers and the exact permissions each one needs.

[Warehouse compatibilities](/setup-and-monitor/collect-and-manage-your-data/sync-with-your-data-warehouse/warehouse-compatibilities.md)
{% endstep %}

{% step %}

### How each table is synchronised

The strategy determines whether updates and deletes reach the datamart, or only inserts.

[Data warehouse sync](/setup-and-monitor/collect-and-manage-your-data/sync-with-your-data-warehouse/data-warehouse-sync.md)
{% endstep %}

{% step %}

### Where live tracking is stored

Only in a Hybrid or Zero-copy deployment. Tracked activity comes to rest in your warehouse rather than in the datamart.

[Replicate live tracking to your warehouse](/setup-and-monitor/collect-and-manage-your-data/sync-with-your-data-warehouse/replicate-live-tracking-to-your-warehouse.md)
{% endstep %}

{% step %}

### What executes on your warehouse

Only in a Hybrid or Zero-copy deployment. Segmentation and identity resolution run there, on your compute budget.

[Run your computation in the warehouse](/setup-and-monitor/collect-and-manage-your-data/sync-with-your-data-warehouse/run-your-computation-in-the-warehouse.md)
{% endstep %}
{% endstepper %}

## The decision that shapes everything else

Whether you create a **working schema** in your warehouse.

{% columns %}
{% column %}

### With a working schema

The service account gets editing rights on that schema, which the platform uses to create temporary tables and track changes on your tables.

Unlocks the strategies that handle **updates and deletes**.
{% endcolumn %}

{% column %}

### Without a working schema

Only **append-only** strategies are available: timestamp-based for event data, and full import for profile data.

Simpler to grant, but a deletion in your warehouse never reaches the datamart.
{% endcolumn %}
{% endcolumns %}

| Strategy            | Needs a working schema     |
| ------------------- | -------------------------- |
| **Timestamp based** | Events: no. Profiles: yes. |
| **Full import**     | No.                        |
| **Hash table**      | Yes.                       |

## How it relates to the other collection routes

This comparison describes a datamart that holds its own data. Where the warehouse is the source of truth, it is not one route among three: it is where the data of record lives, and the other routes write into it.

|                 | Real-time tracking        | Batch import                         | Warehouse sync                                            |
| --------------- | ------------------------- | ------------------------------------ | --------------------------------------------------------- |
| Who initiates   | Your site, app, or server | You, per file                        | The platform, on a schedule                               |
| Latency         | Immediate                 | Per upload                           | Per synchronisation                                       |
| Handles deletes | No                        | Through explicit delete operations   | Yes, with a working schema                                |
| Best for        | Behaviour as it happens   | One-off or nightly loads you control | Data that already lives in a warehouse and keeps changing |

## In this section

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Warehouse compatibilities</strong></td><td>Supported providers, and the access to grant.</td><td><a href="/setup-and-monitor/collect-and-manage-your-data/sync-with-your-data-warehouse/warehouse-compatibilities.md">Warehouse compatibilities</a></td></tr><tr><td><strong>Data warehouse sync</strong></td><td>Declaring the warehouse and choosing strategies.</td><td><a href="/setup-and-monitor/collect-and-manage-your-data/sync-with-your-data-warehouse/data-warehouse-sync.md">Data warehouse sync</a></td></tr><tr><td><strong>Replicate live tracking to your warehouse</strong></td><td>Where tracked activity is stored when the warehouse is the source of truth.</td><td><a href="/setup-and-monitor/collect-and-manage-your-data/sync-with-your-data-warehouse/replicate-live-tracking-to-your-warehouse.md">Replicate live tracking to your warehouse</a></td></tr><tr><td><strong>Run your computation in the warehouse</strong></td><td>Segmentation and identity resolution, executed on your warehouse.</td><td><a href="/setup-and-monitor/collect-and-manage-your-data/sync-with-your-data-warehouse/run-your-computation-in-the-warehouse.md">Run your computation in the warehouse</a></td></tr></tbody></table>

## Related pages

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Choose your deployment mode</strong></td><td>Which of the two arrangements applies to your datamart.</td><td><a href="/setup-and-monitor/plan-and-integrate/choose-your-deployment-mode.md">Choose your deployment mode</a></td></tr><tr><td><strong>Import data in batch</strong></td><td>The file-based alternative.</td><td><a href="/setup-and-monitor/collect-and-manage-your-data/import-data-in-batch.md">Import data in batch</a></td></tr><tr><td><strong>Data warehouse export</strong></td><td>The reverse direction - datamart to warehouse.</td><td><a href="/setup-and-monitor/collect-and-manage-your-data/export-your-data/data-warehouse-export.md">Data warehouse export</a></td></tr><tr><td><strong>Cleaning rules</strong></td><td>Why some warehouse events are not imported.</td><td><a href="/setup-and-monitor/collect-and-manage-your-data/clean-and-delete-data/cleaning-rules.md">Cleaning rules</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/sync-with-your-data-warehouse.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.