# Data Exports

Once you have connected your data sources and BigQuery data warehouse to Weavely, you can set up data exports to begin transferring data into your data warehouse. Follow the steps below to configure exports and manage your datasets.

{% embed url="<https://www.loom.com/share/ee92eddc8c324ea7b7cf10829e40baa6?sid=26d2e10d-a4ff-4b4e-9d54-d6efd0ebc981>" %}

## Access Data Export Settings

1. Go to the **Data** tab in Weavely.
2. Check if BigQuery is connected. If it is not, you will see a warning, and you can click on it to navigate directly to the data warehouse connection settings.

## Configure Export Schedule

1. Review the current export schedule at the top of the page (default is daily at 4 a.m. GMT).
2. Adjust the schedule and time zone as needed to fit your reporting requirements.

## Select and Enable Data Tables for Export

1. In the **Export** section, you’ll see all available integrations and their associated data tables.
2. For each integration (e.g., Google Ads), expand to view available tables, such as the **Campaigns** table.
3. View the dimensions and metrics for each table. To enable a table, toggle it on. Once enabled, Weavely will:
   * Perform an initial backfill of data (up to two years where available).
   * Pull recent data first, followed by historical data, which can take a few minutes to several hours depending on dataset size.

## Verify Data in BigQuery

1. Switch over to your BigQuery project to confirm data export.
2. For each integration, Weavely creates a new dataset with the prefix “Weavely,” such as **Weavely Google Ads** or **Weavely Microsoft Ads**.
3. Within each dataset, enabled tables will appear, allowing you to view the schema and preview the data.

{% hint style="info" %}
Note that every table will have a `compiled_view` created for it — this is the table you should connect to as it will ensure all data is deduplicated.&#x20;
{% endhint %}

## Special Dataset: Weavely Clients

* **Weavely Clients** is an automatically generated dataset containing client information and metadata. This includes:
  * **Client Information**: Name, industry vertical, spend model, and more.
  * **Mapping Table**: Maps Weavely’s client and data source IDs to external IDs (e.g., Google Ads ID, Microsoft Ads ID) for use in cross-channel reporting.

This mapping allows you to combine data across platforms (e.g., Search Console and Google Ads) by joining on the client ID.

Your data exports are now set up, and you’re ready to build cross-channel reports with a unified dataset.


---

# 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://weavely.gitbook.io/weavely-help-centre/setting-up-data-exports.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.