> For the complete documentation index, see [llms.txt](https://docs.corraldata.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.corraldata.com/kb/getting-started/reverse-etl.md).

# Reverse ETL

Reverse ETL (or bi-directional sync) sends up-to-the-minute data from the CorralData platform back to your everyday systems like CRMs, marketing automation platforms, and support tools.

<figure><img src="https://3884465703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX1EfMFQH2czMeSc77MEN%2Fuploads%2Fkp62mqyItgxqKM9qttEq%2FReverseETL.gif?alt=media&amp;token=755d421c-4685-48a8-b275-ce7925ae860f" alt=""><figcaption></figcaption></figure>

**Implementing Reverse ETL can help you and your team manage:**

* Offline Conversions: (e.g., tracking lead-to-revenue impact for ad optimization)
* Custom Audiences (e.g., refining audience targeting for ad platforms)
* Marketing & Operational Automations (e.g., updating CRM fields, generating reports)
* Other Applications (e.g., lead scoring, health scoring, weekly reporting)

**Here’s an example of how Reverse ETL can give you a holistic view of your data:**

A new customer converts from your paid Google ad and books an appointment — but did they actually show up? CorralData’s Reverse ETL connects the dots by sending visit and revenue data back to your CRM, helping sales and marketing know who showed up, how much they spent, and where to invest next.

{% hint style="info" %}
Want to add Reverse ETL to your account? Drop a line to <support@corraldata.com> and we'll get you set up.
{% endhint %}


---

# 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.corraldata.com/kb/getting-started/reverse-etl.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.
