> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/integrations/integration-google-ads-and-gmail.md). # Integration - Google Ads and Gmail {% embed url="" %} To integrate Google Ads, first you need to create a project in the [**Google Cloud Console**](https://console.cloud.google.com/apis/credentials) and configure the OAuth 2.0 credentials.
Follow the steps below:
1\. Create a new project or select an existing one
2\. Enable the Google Ads API
3\. Configure the OAuth 2.0 credentials for a Web application {% hint style="warning" %} **Important:** In the OAuth settings, add **** as an authorized redirect URL.\ If you already have connected Google Ads accounts, you will need to redo the integrations after updating the credentials. {% endhint %} *** ### Configuring the Integration with SAC 360º
When accessing the email account settings, you will find the following options: When you enable this option, the email account starts working as a SAC 360º support channel. * Each email received from a **new contact** automatically creates a support ticket in SAC 360º. * Message delivery happens through the **IMAP**protocol, with automatic synchronization every **1 to 5 minutes**. > **Important:** Only new contacts automatically create a support ticket. Other messages are linked to the existing history. *** ### Mark emails as read Defines the behavior of emails in the provider's inbox after they are synchronized. #### Enabled After being imported into SprintHub, the emails are automatically marked as **read** in the provider's inbox. #### Disabled (Default) The emails remain **unread** in the provider's inbox, even after being synchronized with SprintHub. *** ### Conversation Model Defines how messages will be organized within the support ticket in SAC 360º. #### Continuous Conversation Displays the contact's entire email history in a single support ticket, making it easier to view the full communication. Recommended for teams that want to track the entire customer journey in a single conversation. #### Ticket Each support ticket has its own message history, showing only the emails related to that specific ticket. Recommended for teams that work with independent requests and want to keep each request separate. *** ### Sender Name Defines which name will be shown in the **"From"** field of emails sent by SAC 360º. #### Account Name Uses the name configured in the email account itself. **Example:** **SprintHub Support** [support@company.com.br](mailto:suporte@empresa.com.br) #### Agent Name Uses the name of the user responsible for the support ticket. **Example:** **John Silva** [support@company.com.br](mailto:suporte@empresa.com.br) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sprinthub.com/en/topics/integrations/integration-google-ads-and-gmail.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.