# Export your data models and segments to Google Cloud Storage

### Overview

This destination service allows DinMo to insert new files or update existing ones in a Google Cloud Storage bucket, based on your DinMo models or segments.

To use this service, follow these three steps:

1. **Create a Google Cloud Storage destination**. Follow the step-by-step guide above to establish this connection using a service account JSON key.
2. **Create your DinMo model or segment** representing the data you want to send to your Google Cloud Storage bucket.
3. **Activate your model or segment** with the Google Cloud Storage destination to start synchronization.

The exact export behavior depends on the **Run Type** and **Sync Mode** selected for the activation.

For example, some configurations generate a full file on each run, while others export only new or changed records.

If you don't want to overwrite existing files, we recommend using a **timestamp in your file name**.

### Activation Setup

Once the Google Cloud Storage destination is configured, create an activation to begin syncing your data.

To do so:

1. Go to the **Activations** tab.
2. Click on **New activation**.
3. Select the **model or segment** you want to export.
4. Choose your **Google Cloud Storage destination** from the list.

You’ll then configure the activation:

* **Folder Path**: Specify the folder path inside the bucket where you want to store the file. By default, files are stored at the root of the bucket.
* **Indicate the name you wish to give to your file.**

If you don't want to override existing files, we recommend including timestamp variables in the filename. To do so, you just need to surround each variable with `{}`. DinMo supports these timestamp variables:

* **`{YYYY}`**: Full year (e.g., 2025)
* **`{YY}`**: Last two digits of the year (e.g., 25)
* **`{MM}`**: Month (01-12)
* **`{DD}`**: Day of the month (01-31)
* **`{HH}`**: Hour (00-23)
* **`{mm}`**: Minute (00-59)
* **`{ss}`**: Second (00-59)
* **`{ms}`**: Millisecond (000-999)
* **`{X}`**: Unix timestamp in seconds
* **`{x}`**: Unix timestamp in milliseconds

For example: `{YY}-{MM}-{DD}_export` will be `25-04-14_export.csv` for the upload of April 14th 2025.

* **File Format**: Choose between CSV, JSON, XML, or Apache Parquet.
  * For CSV: select a delimiter and whether to include headers.
* **Attribute Mapping**: Map any fields from your model or segment to custom column names in the destination file. You can rename fields freely.

#### Run Types and Sync Modes

When configuring your sync, you will be asked to choose the Run Type and the Sync Mode.

For Google Cloud Storage activations, here are the available options:

<table data-full-width="true"><thead><tr><th>Run Type</th><th>Description</th><th>Use Case</th><th>Behavior</th></tr></thead><tbody><tr><td><strong>FULL ONLY</strong></td><td>Every sync processes <em>all</em> records from the source and exports a complete file <em>(or several, if size limit is reached).</em></td><td>When the exported file must always contain a full extract, and incremental updates are not required.</td><td><ul><li>No delta logic</li><li>Every sync rebuilds the full export</li><li>Recommended for Snapshot mode</li></ul></td></tr><tr><td><strong>FULL THEN DELTA</strong></td><td>The first sync exports all records. All following syncs export only changed records, based on DinMo’s delta detection logic.</td><td>When exporting large datasets frequently and wanting to reduce file size or processing time.</td><td><ul><li>Sync 1 → Full export</li><li>Next syncs → Only changed records (new, updated).</li><li>Compatible with INSERT, UPSERT, and DIFFERENCE modes</li></ul></td></tr></tbody></table>

Sync modes determine how data is synchronized between your data source and destination. They control whether to insert new records, update existing ones, or both, and how to handle the synchronization process.

For the Google Cloud Storage destination, here are the available options:

<table data-full-width="true"><thead><tr><th>Sync Mode</th><th>Description</th><th>Use Case</th><th>Behavior</th></tr></thead><tbody><tr><td><strong>SNAPSHOT</strong></td><td>Exports a complete snapshot of all records at the time of sync. Each sync can generate a new file with a timestamped name.</td><td>Useful for backups or systems expecting full “point-in-time” extracts.</td><td><ul><li>Always exports the full segment / model</li><li>Creates a new file with timestamp</li><li>No incremental logic</li></ul></td></tr><tr><td><strong>UPSERT</strong></td><td>Writes all updated or new records into the exported file.</td><td>Keeps files up-to-date with the latest source data.</td><td><ul><li>New records → included in the exported file</li><li>Existing records → included <strong>if, and only if</strong>, there are updated values</li><li>Deleted records → simply not present in the file</li></ul></td></tr><tr><td><strong>INSERT</strong></td><td>Adds only new records to the exported file. Existing records are never modified.</td><td>Useful for append-only files, such as historical logs or event tracking.</td><td><ul><li>New records → added to file</li><li>Existing records → ignored</li><li>Missing records → no action</li></ul></td></tr><tr><td><strong>DIFFERENCE</strong></td><td>Generates separate files for added, updated, and removed records between syncs.</td><td>For audit trails, incremental processing, or systems needing change-specific files.</td><td><ul><li>Creates <code>_added.csv</code>, <code>_updated.csv</code>, <code>_removed.csv</code> <em>(or other extensions)</em></li><li>Each file contains only the relevant change type</li></ul></td></tr></tbody></table>

#### Scheduling

Define how frequently your data is exported to your Google Cloud Storage bucket.

Each scheduled execution performs a delta operation, inserting the rows that were added since the last sync. This helps optimize bandwidth and storage costs while keeping your exports fresh and relevant.

{% hint style="warning" %}
The service account used by DinMo must have write access to the target bucket and folder path. If a sync fails, verify both the bucket permissions and the configured folder path.
{% endhint %}


---

# 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://docs.dinmo.io/integrations/destination-platforms/google-cloud-storage/export-your-data-models-and-segments-to-google-cloud-storage.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.