> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/functionality/coupler.io-storage.md).

# Coupler.io Storage

Coupler.io Storage is the layer between your sources and everything that uses your data. It collects data from your sources and keeps it in Coupler.io. From there it serves the data to your destinations, dashboards, and AI tools, without going back to the source app each time.

#### What you get with Coupler.io Storage

* **Keep data the source app no longer returns.** Many apps limit how far back you can fetch data. For example, Meta Ads keeps aggregate metrics for up to 37 months. For sources whose API supports it, Coupler.io fetches incrementally:&#x20;

  * The first run loads your full history.
  * Each later run adds only new data on top of it.

  Your history keeps growing in Coupler.io even after the source app stops returning older data.
* **Faster runs, fewer API requests.** With incremental fetching on top of data already in Storage, every run after the first fetches only new data and adds it to what’s already stored. Runs finish faster and use fewer API requests, which helps when your source app limits requests or charges for them.
* **Serve data without re-running flows.** Coupler.io serves stored data directly to your Data Studio dashboards, Google Sheets and Excel files, AI integrations like Claude, and the AI Agent. You don’t need to re-run the data flow every 15 minutes to keep them working. The data stays available within your plan’s retention period.
* **Control when data changes.** [Pause sources and destinations](https://docs.coupler.io/functionality/coupler.io-storage/pausing-sources-and-destinations-in-coupler.io.md) to keep data in the state you choose.
* **Reuse data in new ways.** Build new data set views on top of stored data with transformations, and send them to any destination.


---

# 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.coupler.io/functionality/coupler.io-storage.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.
