What this means for your store
Ads offline conversion sync sends CRM stage changes to Google Ads and Meta after the original ad click. Platforms receive Qualified Lead, Opportunity, or Closed Won with value and timestamp - so Smart Bidding optimizes toward pipeline and revenue, not $2 form fills from bots. Uses each platform's native HubSpot integration or scheduled uploads; separate from browser pixels and from sGTM CRM apps.
Scenario on a real storefront
A fintech SaaS selling to ecommerce merchants runs Google Search to a demo form. HubSpot creates the contact; sales marks SQL after discovery. The Google Ads integration uploads an offline qualified_lead event with the gclid captured on submit:
# HubSpot form - hidden click ID field
Field: gclid (from URL param or first-party cookie script)
# HubSpot → Settings → Integrations → Google Ads
# Map lifecycle stages to conversion actions:
# Form submitted → online (already in account)
# SQL → offline (+$400 estimated value)
# Closed Won → offline (actual deal amount)
# Meta → Integrations → Facebook Ads
# Offline "Purchase" or custom event for closed-won deals
# Capture fbclid on paid-social landing forms
# Workflow fallback (any ad platform)
Trigger: dealstage = closedwon
Action: HTTP POST to Google Ads Offline Conversion API
gclid, conversion_action, conversion_time, value
# Hygiene: dedupe - do not re-send Closed Won on amount edits
What to do next
- Optimize Google campaigns on SQL or closed-won, not raw leads - CPL drops while pipeline quality rises.
- Require gclid/fbclid on every paid landing form; without click IDs the CRM event cannot attach to an ad click.
- Send conversion timestamps inside Google's click window (90 days) - late uploads are dropped silently.
Bottom line
Capture click IDs on forms, map HubSpot stages to ad conversion actions, and let bidding chase qualified leads and closed revenue - not form volume alone.