> For the complete documentation index, see [llms.txt](https://docs.flip.to/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flip.to/docs/integrations/advertising/google-ads.md).
# Google Ads
Integrating Google Ads with our platform takes a few clicks right from **Integrations** in your account.
{% hint style="warning" %}
**Before you begin:** you'll need read-only access (at a minimum) to the Google Ads accounts that you'd like to connect.
{% endhint %}
## Connect Google Ads
{% stepper %}
{% step %}
**Head over to Integrations**
Sign into [your Flip.to account](https://manage.flip.to/) and navigate to **Platform → Mission Control** or **Account Settings → Integrations**
{% endstep %}
{% step %}
**Click on Google Ads**
You'll find it in the **Marketing & Ads** section.
{% endstep %}
{% step %}
**Click Connect**
You'll be prompted to sign into your Google account and will then allow access to your Google Ads accounts.
{% endstep %}
{% step %}
**Select your Google Ads accounts**
After you've authorized Flip.to, you'll be prompted to select one or more of the Google Ads accounts that you'd like to connect to our platform.
{% endstep %}
{% endstepper %}
**Click Save and that's it.** Your Google Ads accounts are now connected and data should start flowing into your Flip.to platform in the next 24-48 hours.
---
# 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.flip.to/docs/integrations/advertising/google-ads.md?ask=&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.
