# HubSpot Google Ads Integration: 7 Checks for Missing Leads and Conversions

A connected Google Ads account does not establish that every lead reaches HubSpot or that every qualified contact becomes a Google conversion. Diagnose the specific flow: campaign data entering the ads dashboard, website visits becoming attributed contacts, native lead forms creating CRM records, or HubSpot outcomes returning to Google.

Canonical URL: https://www.martechdevs.com/blog/hubspot-google-ads-integration

By [Jafrin Akter Alo](https://www.martechdevs.com/authors/jafrin-akter-alo)

Data Engineer and Co-founder at [Martechdevs](https://www.martechdevs.com) and [Growth and Analytics Partners](https://www.growthandanalytics.com)

[LinkedIn](https://linkedin.com/in/jafrinalo)

Last updated: 2026-10-27

Next step: [Google Ads conversion diagnostics: "setup is incomplete" and "needs attention" explained](https://www.martechdevs.com/blog/google-ads-conversion-diagnostics)

Start with one missing record and the result you expected. Write down the ad account, campaign, form or lifecycle event, relevant contact and actual outcome time. That evidence will tell you which of the seven checks below matters.

Use this guide for HubSpot's native integration and its boundaries. The [offline conversion import guide](https://www.martechdevs.com/blog/offline-conversion-import) covers a custom outcome ledger and delivery pipeline when native event semantics do not match the business requirement.

## 1. Is the correct individual Google Ads account connected?

Connect the individual advertising account with an authorized Google user, then confirm the HubSpot account and permissions on both sides.

HubSpot requires Ads publishing access and Google Ads Admin access for the individual account. A Google Ads manager account cannot be connected as though it were the advertising account beneath it. Cancelled accounts are also ineligible. Connection starts in HubSpot Settings, Marketing, Ads, then Connect account. [HubSpot connection requirements](https://knowledge.hubspot.com/ads/connect-your-google-ads-account-to-hubspot).

Before reconnecting, compare:

| Item | Evidence to inspect | Why it matters |
| --- | --- | --- |
| Google user | The identity authorizing the connection | A signed-in personal account may have different access |
| Individual Ads account | The actual customer account serving the campaigns | Access to a manager does not identify the intended child account |
| HubSpot account | The destination account containing the contacts | Similar company names can conceal separate environments |
| Integration owner | A current employee or approved operating identity | Access can change when staff or agencies leave |

HubSpot's connection troubleshooting specifically calls out the wrong signed-in Google user and altered app permissions. Check those before assuming a campaign or conversion rule is broken. [Google account connection troubleshooting](https://knowledge.hubspot.com/ads/troubleshoot-your-google-ads-account-connection).

Record the current connection and event configuration before a reset. Reconnection should solve an identified authorization problem, with a named owner checking the affected flows afterward.

## 2. Are you expecting contact tracking from an ad type that only supports reporting?

Separate campaign reporting from contact attribution because they have different requirements.

HubSpot reporting can display network-provided clicks and impressions for an ad that HubSpot cannot use for contact attribution. Its ads FAQ identifies YouTube ads as an example. Seeing spend and clicks in the dashboard therefore does not establish a working contact-tracking path. [HubSpot tracking versus reporting](https://knowledge.hubspot.com/ads/ads-faq).

Choose the symptom precisely:

| Symptom | Flow to inspect | Useful evidence |
| --- | --- | --- |
| Campaign itself is absent | Account connection and reporting scope | Correct account, campaign and report filters |
| Clicks appear but contacts do not | Ad tracking and website identity | Supported ad type, landing parameters and form journey |
| Native lead-form responses are absent | Lead syncing | Campaign/form association, mapping and sync errors |
| Qualified contacts are absent in Google | Outbound conversion events | Stage timing, eligibility, mapping and diagnostics |

Check the exact campaign type in HubSpot's support table before spending hours on a URL template. A limitation in contact tracking cannot be repaired by repeatedly copying a script onto the landing page.

Also distinguish a lead submitted inside an ad from a form completed on your website. The first uses the lead-sync flow. The second depends on the website's own submission and attribution implementation.

![The reader first chooses whether a record is missing in HubSpot or Google Ads. Missing HubSpot records branch by website form versus native ad form; missing Google outcomes lead to event eligibility and goal checks.](https://www.martechdevs.com/assets/blog/hubspot-google-ads-integration.svg)

Diagram connections:

- Where is the record missing? to Where was the form?: In HubSpot. 
- Where was the form? to Check tracking and submission: On the website. 
- Where was the form? to Check lead syncing: Inside the ad. 
- Where is the record missing? to Check event eligibility and goals: In Google Ads

This first decision prevents a common detour: editing website tracking for a lead that was submitted entirely inside Google's form.

## 3. Do the ad tracking parameters survive the website journey?

Inspect the final landing URL and its tracking configuration, then follow the visitor through the actual form submission.

HubSpot applies its Google Ads tracking template at campaign level. Ad-group or ad-level overrides can interfere; the campaign template must be compatible with HubSpot's requirements, including the opening `{lpurl}`. Google auto-tagging can coexist with HubSpot's template. HubSpot recommends a full, final destination URL without a redirect. [Google ad-tracking requirements](https://knowledge.hubspot.com/ads/track-and-report-on-google-ads-in-hubspot).

The implementation check is a journey:

1. Record the configured final URL and tracking settings for the affected ad.
2. Inspect the URL after the landing page finishes redirecting.
3. Confirm the relevant HubSpot and Google parameters remain intact.
4. Follow the real route to the form, including another domain or booking system.
5. Submit a controlled test under an allowed consent state.
6. Inspect the resulting contact's observed source and identifier fields.

Use the [HubSpot tracking-code checks](https://www.martechdevs.com/blog/hubspot-tracking-code) when the page collector or contact identity is missing. Use the [Forms API guide](https://www.martechdevs.com/blog/hubspot-forms-api) if a custom submission drops the browser context at a backend or proxy.

If the missing field is the Google click identifier, use the [GCLID handoff checks](https://www.martechdevs.com/blog/gclid) to compare the landing URL, form payload and saved CRM context.

A redirect can preserve some parameters while losing others. Inspect the actual output instead of treating the presence of one UTM as proof that all attribution context survived. Compare the exact values; a populated field can still contain a stale value from an earlier visit.

HubSpot exposes tracking errors by campaign and identifies edited or conflicting templates as specific Google Ads problems. [Ad-tracking diagnostics](https://knowledge.hubspot.com/ads/troubleshoot-ad-tracking-issues).

Before removing another tool's template, identify what it supplies and who owns it. Preserve required click-fraud, measurement or routing behavior through an agreed configuration. Deleting all custom parameters can make one diagnostic pass while breaking another team's measurement.

Keep campaign naming consistent with the [UTM naming convention](https://www.martechdevs.com/blog/utm-naming-convention). Identity parameters and descriptive campaign labels have different jobs; renaming a campaign should not rewrite the evidence of an earlier click.

## 4. Are Google lead-form submissions eligible for HubSpot's lead sync?

Enable the Google lead-sync flow for the correct account and verify the campaign-associated form, field mapping and submission timing.

HubSpot's Google lead syncing supports Google Lead Form Extensions submitted within Google or YouTube. Forms must be associated with a campaign, Google auto-tagging must be enabled, and Google Admin access is required. Google leads sync only after lead syncing is enabled, with no historical lead backfill through that setting. HubSpot allows up to two hours for new leads to sync. [Lead-sync requirements](https://knowledge.hubspot.com/ads/sync-leads-from-your-facebook-page-or-linkedin-ads-account-to-hubspot).

Keep a specific submission as the test case. Confirm that it occurred after the connection was enabled, then inspect the corresponding form and any sync error. Waiting cannot repair an invalid mapping, but checking immediately and declaring a failure can also misclassify normal processing.

For each mapped field, compare the ad form's question, the destination property and its intended meaning. A form asking for company size should not fill a property that the sales team uses for annual revenue simply because both accept a number.

Mapping changes affect newly synced leads; previously synced records retain their prior mapping. [HubSpot lead mapping behavior](https://knowledge.hubspot.com/ads/sync-leads-from-your-facebook-page-or-linkedin-ads-account-to-hubspot). Plan any historical correction separately, with the original submission available for comparison.

Do not turn lead syncing off and on expecting old Google submissions to reappear. Reconcile the missing population and choose an approved recovery route. Preserve its actual source, submission time and consent evidence.

## 5. Does the contact qualify for the native conversion event?

Check the event's creation time, contact eligibility and Google account configuration before expecting a lifecycle transition to sync.

HubSpot's native Google conversion events require Marketing Hub Starter, Professional or Enterprise. Lifecycle changes must occur after the event is created. Matching needs a GCLID or shared contact data. HubSpot requires the event's “Included in account-level goals” setting to be Yes and excludes MCC-based Enhanced Conversions syncing. Multiple configured lifecycle stages can each send an event. [Native Google conversion-event rules](https://knowledge.hubspot.com/ads/create-and-sync-ad-conversion-events-with-your-google-ads-account).

Build a small eligibility review around real transition history:

| Question | Evidence | Action when absent |
| --- | --- | --- |
| Did the defined stage change occur? | Contact stage history | Repair the business transition or its record |
| Did it happen after event creation? | Both actual times | Keep older outcomes separate from the native event's scope |
| Is matching data available and permitted? | Identifier and sharing settings | Fix capture or classify the record as ineligible |
| Is the intended population selected? | Event's contact-selection rule | Align the rule with the approved measurement population |
| Does the event target the intended account? | Account and conversion action | Correct the mapping before expanding the rollout |

Treat a synthetic contact as an implementation test. It cannot demonstrate attribution to a genuine advertising interaction. Do not invent a GCLID or copy one from another customer to force a match.

For form events, HubSpot can create a conversion action or enhance an existing one. A form can be used as an event trigger once. [HubSpot form-event configuration](https://knowledge.hubspot.com/ads/create-and-sync-ad-conversion-events-with-your-google-ads-account).

Document whether the form event represents the initial submission and whether a later lifecycle event represents qualification. Both can be useful, but they should remain distinguishable.

## 6. Does the conversion value match the business outcome?

Choose a value rule that matches the counting unit, and keep estimated stage value separate from actual deal revenue.

HubSpot's native Google lifecycle events use a fixed value; the previous “Use the Deal amount” option is unavailable. [Native lifecycle value setting](https://knowledge.hubspot.com/ads/create-and-sync-ad-conversion-events-with-your-google-ads-account).

A fixed qualification value can be useful if it reflects the economics of a consistent cohort. It should not be described as the revenue of each individual deal.

Consider this hypothetical model in USD. In a mature cohort, 25% of qualified opportunities become customers and average contribution per customer is USD 1,200. The expected contribution per qualified opportunity is USD 300.

| Input or output | Amount | Meaning |
| --- | ---: | --- |
| Opportunity-to-customer rate | 25% | Mature cohort assumption |
| Contribution per customer | USD 1,200 | Economic measure selected for the example |
| Expected contribution per opportunity | USD 300 | 25% × USD 1,200 |
| Value of 20 qualified opportunities | USD 6,000 | Twenty estimates, not recognized revenue |

Before using that model in a contact-stage event, establish whether one qualifying contact represents one opportunity. Three contacts on a single opportunity would produce USD 900 of estimated value if all three triggered the same USD 300 event. The arithmetic is correct for three contacts, but the model was defined per opportunity.

Choose a deal-based implementation when the business unit is the deal and native contact stages cannot represent it reliably. The [offline conversion integration guide](https://www.martechdevs.com/blog/offline-conversion-import) explains the outcome ledger, actual timestamps and supported delivery route.

## 7. Is Google using the intended action in the intended campaign?

Inspect conversion-action reporting and campaign goals together, because visibility and bidding participation are separate settings.

Google's “All conversions” view helps locate primary and secondary actions that may be absent from the campaign's “Conversions” column. Segment by conversion action before comparing totals. [Google conversion-reporting columns](https://support.google.com/google-ads/answer/12007894?hl=en).

Review the intended action's name, source, category, value rule, counting setting and campaign-goal membership. Similar names can hide an older website action, a new CRM action and an imported GA4 action that all represent the same initial lead.

For standard goals, primary actions participate in bidding when the campaign uses their goal. Secondary actions usually serve observation, but a secondary action included in a custom goal can still affect bidding. [Campaign-specific and custom goals](https://support.google.com/google-ads/answer/9143218?hl=en).

Avoid a blanket instruction to “make everything secondary during testing.” The connector's sync prerequisites and the campaign's goal configuration both need review. Agree on a controlled validation plan with the media owner before enabling an event that may change optimization.

In HubSpot's Events tab, open an affected event and inspect its error detail; the Needs Attention area identifies stopped syncs. Google reports attributed conversions, so its total need not equal every synced CRM event. [HubSpot event diagnostics](https://knowledge.hubspot.com/ads/create-and-sync-ad-conversion-events-with-your-google-ads-account).

For Google Ads Data Manager's separate HubSpot connection, inspect its own source, selection filters and field mapping. Google documents that route for Customer Match and conversion imports. Connecting it is a different configuration from HubSpot's own Ads events. [Google's HubSpot Data Manager connection](https://support.google.com/google-ads/answer/15293735?hl=en).

Choose one owner for each business outcome and destination action. If two integrations are active, document whether they enhance one conversion or send two separate occurrences. Do not infer deduplication merely because the event names match.

## What should an end-to-end HubSpot Google Ads acceptance test prove?

The acceptance test should prove the intended record movement and configuration, with any attribution uncertainty kept visible.

Use a bounded cohort of genuine eligible records to reconcile outcomes after the relevant processing period. Keep synthetic setup tests separate.

A hypothetical cohort might contain 40 recorded qualification transitions, of which 30 meet the selected event's timing, identifier and sharing rules. If the delivery evidence establishes 28 accepted outcomes, delivery coverage is 28 ÷ 30, or 93.3%. The two unresolved eligible outcomes need investigation. If Google attributes 21, that is a different count with a different eligibility question.

Do not label 21 ÷ 40 as the integration success rate. It combines business qualification, your selection rule, delivery and Google's attribution into one number. To keep that reconciliation in one report beside Google Ads spend, you can [connect HubSpot to Looker Studio](https://www.martechdevs.com/looker-studio-implementation#connect-hubspot).

Use this checklist:

## Checklist

- [ ] Correct individual Google Ads account and authorized integration owner.
- [ ] Campaign type checked for both reporting and contact tracking.
- [ ] Final landing URL and tracking-template ownership recorded.
- [ ] Known website journey preserves permitted identity and submission context.
- [ ] Native lead forms checked separately from website forms.
- [ ] Lifecycle transitions satisfy the event's timing and selection rules.
- [ ] Fixed values use the correct contact, opportunity or deal unit.
- [ ] Data sharing and consent mappings match the approved policy.
- [ ] Destination actions and campaign goals reviewed for duplication.
- [ ] Sync errors have an owner and a recoverable list of affected records.

If the failures cross ad templates, custom forms and CRM stages, [scope the tracking implementation](https://www.martechdevs.com/analytics-tracking) around the complete journey. Where stage criteria and ownership are also unclear, include [CRM and lifecycle implementation](https://www.martechdevs.com/crm-lifecycle) so the conversion represents a useful commercial outcome.

## Frequently asked questions

### Can connecting Google Ads fix old contacts with missing attribution?

A connection cannot reconstruct evidence your systems never captured. First distinguish missing integration access from missing historical click, visit or submission context. Preserve available records and identify which population can be reconciled under the supported route. Do not copy a current campaign onto older contacts simply to fill a blank source field; that changes the meaning of the history.

### What happens when an agency's Google user loses access?

The integration can lose the permissions it relied on, so review the connected identity as part of an agency handover. Document the intended replacement user, affected accounts and event settings before changing access. After reauthorization, check reporting, lead syncing and outbound events separately. One successful account connection screen does not establish that every dependent flow resumed.

### Can we use one lifecycle event for several products with different economics?

Use a shared fixed value only if it represents the combined population meaningfully. Products with materially different qualification rates or contribution may need separate definitions or a more detailed delivery design. Validate how the chosen configuration selects contacts and handles a person interested in several products. Keep business reporting at the appropriate product and opportunity level.

### Should HubSpot and GA4 show the same Google Ads lead count?

Expect differences when the systems observe different identities, consent coverage, event definitions or attribution scopes. Compare one clearly defined outcome and cohort first, then explain the remaining coverage gap. The [GA4 and HubSpot reporting guide](https://www.martechdevs.com/blog/ga4-hubspot) shows how to connect acquisition and CRM evidence without forcing their interface totals to represent the same population.

### Is it safe to delete an old conversion action after adding the new integration?

Review its campaign usage, historical reporting role and any other sender before removing it. Preserve a configuration record and agree on the replacement with the media owner. A similar name does not prove that the new action receives the same outcome or value. Validate the new path, then retire the old one through a deliberate change.

## Sources

1. [Connect Google Ads to HubSpot](https://knowledge.hubspot.com/ads/connect-your-google-ads-account-to-hubspot)

2. [Troubleshoot the Google Ads connection](https://knowledge.hubspot.com/ads/troubleshoot-your-google-ads-account-connection)

3. [HubSpot ads FAQ](https://knowledge.hubspot.com/ads/ads-faq)

4. [Track Google ads in HubSpot](https://knowledge.hubspot.com/ads/track-and-report-on-google-ads-in-hubspot)

5. [Troubleshoot ad tracking](https://knowledge.hubspot.com/ads/troubleshoot-ad-tracking-issues)

6. [Sync lead ad forms](https://knowledge.hubspot.com/ads/sync-leads-from-your-facebook-page-or-linkedin-ads-account-to-hubspot)

7. [HubSpot Google conversion events](https://knowledge.hubspot.com/ads/create-and-sync-ad-conversion-events-with-your-google-ads-account)

8. [Google conversion-reporting columns](https://support.google.com/google-ads/answer/12007894?hl=en)

9. [Google campaign-specific goals](https://support.google.com/google-ads/answer/9143218?hl=en)

10. [Google Ads Data Manager: HubSpot](https://support.google.com/google-ads/answer/15293735?hl=en)