Validate the offline conversion sync
before you switch bidding.

RoleYou are validating the HubSpot → Google Ads offline conversion sync for my B2B SaaS company. The goal is to verify the end-to-end pipeline is firing correctly across six components before I switch (or if already switched, while running) Smart Bidding to optimize on the offline conversion event. Output should be a 6-component validation table with each component flagged CONFIGURED, MISCONFIGURED, or NOT FIRING, plus prioritized fix order. My BrandBrand: [your B2B SaaS brand name] Average sales cycle: [in days — typical B2B SaaS is 60-120] HubSpot lifecycle stages used: [e.g. Lead → MQL → SQL → Opportunity → Customer] Primary offline conversion event: [which lifecycle transition is the SQL/optimization signal — typically MQL or SQL] Average ACV: [your typical deal size — for value mapping validation] Current Google Ads bidding strategy: [e.g. Maximize Conversions, Target CPA, Manual CPC] TaskRun validation across all 6 components. For each component, return CONFIGURED, MISCONFIGURED, or NOT FIRING with the specific finding. COMPONENT 01 · GCLID capture rate 1. Pull all HubSpot contacts created in last 90 days where Original Source = Google Ads (or contains "google" / "cpc"). Use growthspree-mcp hubspot connector. 2. For each contact, check if the GCLID custom property has a non-empty value. 3. Calculate match rate: contacts with GCLID / total Google Ads contacts. 4. Flag CONFIGURED if rate >= 85%, MISCONFIGURED if 50-85%, NOT FIRING if < 50%. 5. If < 85%, identify which forms are losing GCLID — usually multi-step forms or pages that don't pass the gclid URL parameter through. COMPONENT 02 · HubSpot lifecycle triggers 1. Pull HubSpot contacts that transitioned to the primary offline conversion stage (MQL/SQL) in last 30 days. 2. Cross-reference against HubSpot workflow execution logs — did the Google Ads export workflow run for each transition? 3. Flag CONFIGURED if execution rate >= 95%, MISCONFIGURED if 70-95%, NOT FIRING if < 70%. 4. If < 95%, identify why workflows aren't firing — usually filter conditions that exclude expected contacts. COMPONENT 03 · Google Ads import conversions 1. Pull Google Ads conversion data using growthspree-mcp google_ads connector. Query conversions in last 30 days where Source = "Import" or "Offline". 2. Compare count of import conversions to count of HubSpot lifecycle transitions for the same period. 3. Flag CONFIGURED if Google Ads import count is within 10% of HubSpot trigger count, MISCONFIGURED if 30-70% gap, NOT FIRING if < 30% of expected. 4. If gap exists, the most common cause is GCLID match failure on Google Ads side — events arrive but can't be attributed to a click. COMPONENT 04 · Conversion value mapping 1. For a sample of recent import conversions, compare the conversion value in Google Ads vs the value sent from HubSpot. 2. Validate the values reflect lifecycle stage hierarchy — SQL value > MQL value, Opportunity > SQL, Closed-Won = full deal value. 3. Flag CONFIGURED if values match and follow hierarchy, MISCONFIGURED if values are wrong magnitude or hierarchy is inverted, NOT FIRING if values are all zero or null. 4. Common failure: all events given the same flat value (e.g. $1) which prevents value-based bidding from working. COMPONENT 05 · Conversion window alignment 1. Pull Google Ads conversion action settings for the offline conversion event. 2. Validate conversion window length against the brand's average sales cycle. 3. Flag CONFIGURED if window is within 1.2x of average cycle (e.g. 90-day window for 75-day cycle), MISCONFIGURED if shorter than cycle, NOT FIRING if window is set to default (30 days for B2B SaaS with 60-120 day cycle is functionally not firing for most conversions). COMPONENT 06 · Bidding strategy alignment 1. Pull current Google Ads bidding strategy and primary conversion goal. 2. Validate the primary conversion is the offline conversion event (not the form fill). 3. Validate Smart Bidding has 30+ conversions in the optimization window — too few and the algorithm doesn't have signal. 4. Flag CONFIGURED if primary = offline event AND volume is sufficient, MISCONFIGURED if primary is form fill but offline events exist, NOT FIRING if Smart Bidding is disabled or pointing at the wrong event. Output format1. Headline: overall pipeline status. ALL CONFIGURED / SOME MISCONFIGURED / CRITICAL FAILURES. Highlight the single highest-leverage fix. 2. Validation table: 6 rows, one per component, with status pill (CONFIGURED / MISCONFIGURED / NOT FIRING) and the specific finding for each. 3. Prioritized fix order — usually fix in pipeline sequence (GCLID first because everything downstream depends on it; bidding strategy last because it depends on volume from upstream working). 4. Honest calibration notes: - If volume is too low to validate (e.g. fewer than 30 Google Ads contacts in 90 days), flag that conclusions are tentative — re-run after volume builds. - If account is brand new (offline conversions configured < 14 days ago), flag that initialization period may explain low Google Ads import counts. - If multiple components are NOT FIRING, recommend NOT switching bidding strategy yet — the gain from value-based bidding is wiped out by corrupted signals. // Be specific. Name the actual misconfigured form, the actual conversion value, the actual window length. // Don't just say "GCLID capture is low" — say "62% match rate, primary loss is on the multi-step trial form." // If a component passes, say so explicitly — don't pretend everything is broken. // Recommend the implementation guides for fixes, don't try to walk through the fix steps in the validation output.