> 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/integration/integration-google-ads-and-gmail/google-ads-conversions.md). # Google Ads Conversions This quick tutorial assumes that you already have your Google Ads account connected and integrated with SprintHub and that you have already configured conversions within the Google Ads dashboard. If you have not done so yet, click the tutorial below to configure it: {% content-ref url="/pages/613076f7d6d57092bc5c5a44ce33a48f4719c2e3" %} [Integration - Google Ads and Gmail](/en/topics/integration/integration-google-ads-and-gmail.md) {% endcontent-ref %} {% content-ref url="/pages/062bfd7c5f3beaa8f040de887d41e9778254129f" %} [Creating conversions in Google Ads to send via SprintHub](/en/topics/integration/integration-google-ads-and-gmail/creating-conversions-in-google-ads-to-send-via-sprinthub.md) {% endcontent-ref %} In the default Google Ads configuration in SprintHub, it is possible to leave enabled to send conversions automatically whenever a Lead is created, CRM Lead Won, Score modified or Lead Lost. This is useful if 100% of the leads that arrive come from Google. If that is not your case and you have Leads coming from other channels such as Meta Ads or Tiktok Ads or LinkedIn Ads, disable this option:
Leave everything disabled. After Qualifying the Lead using AI or some human SDR and you send the Lead to the CRM, creating an opportunity for this Lead, send the conversion only if the GCLID exists, inside the "Third Party Data" tab of the Contact/Lead, as shown below.
#### 1. Why you should NOT send leads exclusive to Meta or another platform to Google If a lead came purely from Meta Ads and never interacted with your Google ad, sending that conversion to Google Ads brings two problems: * Processing Error: To record an offline conversion (lead import), Google requires a "link" key. The main key is the GCLID (Google Click ID). If the lead came from Facebook, it does not have a GCLID. If you try to upload without this ID, Google will simply reject the row or report an error. * Data Poisoning: If you, for some reason, try to force this conversion (using customer data such as email for *broad* match *), you will be telling Google:*"Look, bring more people like this" #### . The algorithm will try to find patterns in those users. If the behavior pattern of those who convert on Facebook is different from those who convert on Google, you will confuse the artificial intelligence, worsening the optimization of your bids. 2\. The exception: The Cross-Channel Path What if the user clicked on Google Ads AND then clicked on Meta Ads? * In this case, the best approach depends on the attribution model, but technically you should send it if the lead has a GCLID associated with it in your CRM, even if the "last conversion" came from Meta. * How it works: If your CRM stored the GCLID from a click made 5 days ago, and the customer converted today via Facebook, by sending that GCLID to Google, the system will identify that it participated in the journey. #### --- # 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/integration/integration-google-ads-and-gmail/google-ads-conversions.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.