#lead generation tracking

Google Ads Offline Conversion Import Planner for Lead Gen: GCLID Capture in Hidden Fields, CRM Stage to Conversion Action Mapping, Upload CSV Headers and Time Zone, 90 Day Window, Primary vs Secondary Goals, and Error Fixes

Feed real sales outcomes back into Google Ads: capture the GCLID on every form, store it in the CRM, map lead stages to import conversion actions, build an upload file with the right headers, time zone, and values, respect the click window, choose which actions are primary for bidding, and fix the usual upload errors.

Act as a paid search analyst who sets up Google Ads offline conversion imports for service businesses with long sales cycles, and who has fixed uploads rejected for missing click IDs, conversion times before the click, and conversion names with a stray space. Inputs: - Business and sales process: what a lead is, the CRM stages a lead passes through, and typical time from lead to sale: [SalesProcess] - CRM or lead store and how forms reach it (website form tool, call tracking, chat): [LeadStack] - Current Google Ads conversion actions, which are primary, and the bid strategy in use: [CurrentConversions] - Values you can stand behind per stage (average contract value, or a value only at close): [StageValues] - Account time zone and the time zone the CRM stores timestamps in: [TimeZones] - Consent setup for ad user data where required, and who owns the upload: [ConsentAndOwner] - Output format: [Format] Generate: 1. A GCLID capture plan from LeadStack: auto tagging on, a hidden form field that stores gclid from the landing URL (and gbraid or wbraid if present), persistence across pages, and a CRM field to hold it. Mark CHECK for any tool specific step. 2. A stage to conversion action map: one import conversion action per CRM stage worth optimizing, with exact names, count setting (one per lead), value from StageValues, and click through window. 3. Primary vs secondary: which action bidding should use given CurrentConversions and how many conversions per month each stage produces, and which stay secondary for reporting so nothing is double counted. 4. The upload file: a Parameters:TimeZone line from TimeZones, then the headers Google Click ID, Conversion Name, Conversion Time, Conversion Value, Conversion Currency, with three sample rows and the time format. 5. Timing rules: conversion time must be after the click, clicks older than the action's window will be rejected, and how often to upload (scheduled file, Sheets, or API). 6. A fallback for leads with no click ID: enhanced conversions for leads with hashed email, and where consent from ConsentAndOwner limits it. 7. An upload error table: common errors, what causes each, and the fix. 8. A first month QA plan: compare CRM counts to imported counts by week and flag gaps over a set threshold. Constraints: - Use only facts from Inputs. Never promise lower cost per lead or quote typical lift. Mark UI paths that may have moved as CHECK. - Plain language for the business owner; no em dashes.