Cost per SQL by Google Ads campaign
Ask for last month and the agent matches each Google Ads campaign's cost to its new HubSpot leads, SQLs and customers, with cost per SQL.
Combine HubSpot + Google Ads and move ad data into HubSpot. Just ask Letaido's AI agent and watch it do the work.
Use this HubSpot Google Ads integration for cost per SQL by campaign, ad click details on new contacts and pausing campaigns with no SQLs.
Ask for last month and the agent matches each Google Ads campaign's cost to its new HubSpot leads, SQLs and customers, with cost per SQL.
Every morning, the agent matches recent new contacts to their Google Ads clicks and writes the campaign, ad group and keyword on each one.
Ask and the agent finds campaigns that spent over your limit in 60 days without one HubSpot SQL, shows you the list, then pauses them.
HubSpot's ads tool syncs Google Ads data for you. Leta answers questions across both and acts on them.
| Option | Cost next to leads and SQLs | Ad click details on contacts | Pauses campaigns | Sends audiences and conversions to Google | Applies your own rules |
|---|---|---|---|---|---|
| Yes | Yes | Yes | No | Yes | |
| HubSpot's Google Ads integration (ads tool) | Yes | Partly | Yes | Yes | No |
| Google Ads Data Manager | No | No | No | Yes | No |
| Zapier | Partly | Partly | Yes | Yes | Partly |
| Option | Which way data goes | How a run begins | Good at | Keep in mind |
|---|---|---|---|---|
| Letaido AI agent | Google Ads into HubSpot, and HubSpot SQLs back into Google Ads decisions such as pausing a campaign | A set time, such as every morning at 7am, or a request in chat | Cost per lead and per SQL by campaign, the campaign and keyword on new contacts, pausing campaigns that bring no SQLs | Campaigns are matched by name, so HubSpot's ad tracking (or the same utm_campaign) needs to be on. No job here sends audiences or conversions to Google Ads |
| HubSpot's Google Ads integration (ads tool) | Spend and clicks into HubSpot. Audiences, and lifecycle stage conversion events, back to Google Ads | Its own sync once you connect the ad account in HubSpot's ads settings | An ads dashboard with spend next to contacts, SQLs and deals, UTM auto-tracking, pausing by hand, and audiences | No manager accounts. Conversion events need Marketing Hub Starter or higher and use a fixed value, not each deal's amount |
| Google Ads Data Manager | HubSpot into Google Ads only | Imports you set up from Google Ads, with HubSpot as the data source | Customer Match lists from a HubSpot list, and offline conversion imports or enhanced conversions for leads | One HubSpot list per audience. Conversion conditions must use the Lifecycle Stage field. Nothing comes back into HubSpot |
| Zapier | Either way: Google Ads actions include Send Offline Conversion, Add Contact to Customer List and Set Campaign Status | A trigger such as a new HubSpot form submission or a new Google Ads lead form entry. Many of these triggers poll for new data on a timer | Templates such as new HubSpot contacts in Google Ads customer lists, or offline conversions for new HubSpot form submissions | You build one Zap per recipe, and each successful action step counts as a task. Putting campaign cost next to HubSpot stages takes additional Zap steps, such as Create Report in Google Ads plus Find CRM Object in HubSpot, and a step that joins them |
Saved as an automation, like “Google Ads keyword on new HubSpot contacts”: every day at 7am. These jobs run on a schedule or when you ask.
Ask in chat; Leta picks from 105 actions.
Allow all read operations once per app; approve each kind of write once.
Get CRM object · Create contact · Delete company · Get deal
List ad groups · Remove campaign budget · Update campaign · API request
Yes. HubSpot's ads tool connects a Google Ads account, syncs spend into HubSpot and sends audiences and conversion events back. Leta, Letaido's AI agent, adds jobs on top: cost per SQL by campaign, ad click details on new contacts, and pausing campaigns that bring no SQLs.
For HubSpot, create a Service Key in HubSpot and paste it into Letaido. For Google Ads, sign in and approve if the connect card shows Connect with Google Ads; otherwise use your own OAuth client with the Google Ads API enabled.
By campaign name. HubSpot's ad tracking saves the campaign name in a contact's original source drill-down 1, and Leta matches it to the campaign in Google Ads. For the keyword job, it matches HubSpot's Google ad click ID to the click in Google Ads.
No. These jobs run on a schedule, such as every morning at 7am, or when you ask in a chat. A contact whose click isn't in the Google Ads report yet is tried again the next morning.
Not with the jobs on this page. HubSpot's own conversion events and Google Ads Data Manager do that. Leta uses your HubSpot SQLs to decide which campaigns to pause instead.
Allow all read operations once per app; approve each kind of write once. The pause job also shows you the campaigns first and waits for your yes before it pauses any. It only changes their status, so budgets, bids and keywords stay as they are.
Connect HubSpot and Google Ads, then ask for a job like "Show last month's cost per SQL by Google Ads campaign". Leta gets it done on your schedule, or the moment you ask.
Get Letaido