G03: native input mapping Investigate a drop in Local Services Ads leads Purpose and compatibility A blank file is an input scaffold, not a native export or completed mapping. Preserve the exact column names/order and input names. Populate only from the documented native acquisition or explicit manual evidence. Stop if a required input, permission, privacy condition or coverage requirement is missing. Do not replace an old prompt until the named inputs and field-level mapping are reviewed. These files do not authorize login, setup, imports, account changes, message sending, publication, test submissions or spending. Contract status: Requires distinct native-input templates or an explicit reviewed mapping; existing kit is not drop-in compatible Compatible without mapping: false Required inputs Periods -> native-periods-template.csv Exact columns: period_alias,start,end,lead_metric,lead_count,spend,credits,currency,source_ref Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. Changes -> native-changes-template.csv Exact columns: change_at,setting,old_value,new_value,source_ref Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. Scope -> native-scope-template.txt Required content: Full approved scope, source account aliases, date filters, date basis/timezone, as-of capture time, definitions, source-to-alias map provenance, matching rules, inspected/excluded records, permission/privacy limits, missing-data reasons, coverage and responsible reviewer. Include recipe-specific policies, versions and tests. Scope must be inside the AI workbook or pasted packet, not merely a separate unprovided file. Complete each required field from approved source evidence. Old files and reviewed mapping changes.csv Original first line: change_id,changed_at,setting,old_value,new_value lead-decline-review.csv Original first line: period,observed_metric,comparator,difference,coverage,possible_explanation,next_evidence_check lsa-periods.csv Original first line: period_start,period_end,lead_id,lead_type,charged_amount,credit_status,currency scope.txt Original first line: G03: scope.txt lsa-periods.csv -> Periods requires reviewed aggregation or direct source-report totals for equal-length comparable periods. Define lead_metric and count only actual captured records with complete coverage. charged_amount and credit_status do not automatically supply total spend/credits. Acquire period_alias, lead_count and source_ref with their basis. changes.csv -> Changes: verify changed_at -> change_at, setting, old_value and new_value; add source_ref from actual change-history evidence. change_id alone does not prove the change. scope.txt -> Scope: carry legacy/migrated interface, historical availability, lead-type definitions, timezone and period completeness. lead-decline-review.csv is an old output. Do not combine discontinuous interfaces or claim an unverified native CSV. How to perform the handoff 1. Keep original exports and raw evidence unchanged in restricted firm storage. Check actual source fields, dates, coverage, privacy and access before mapping. 2. Prepare the distinct native inputs above. Record every mapped field, derived interpretation, missing value and observed source reference in Scope. Identically named columns still require source/evidence validation. 3. Create a separate minimized analysis workbook or text packet. Name tables/sections exactly as listed. A CSV file does not itself create a named Excel table. 4. Include the full completed Scope in the same AI-visible workbook or pasted packet. Verify exclusions, denominator, matching rules and unknowns. Do not hide raw client data on another worksheet. 5. Obtain the responsible reviewer’s approval of the completed mapping and evidence coverage before using the native prompt. Keep all blocked items visible. Any later external action is a separately authorized human step. Acquisition and privacy requirements Use approved minimized administrative metadata and aliases only. Aliases alone do not guarantee anonymity. Keep untouched exports/screenshots, identifying source maps, full documents and sensitive narratives in restricted firm storage. A hidden worksheet is not a privacy boundary. Do not insert credentials, payment/tax identifiers, raw client documents or unsanitized review text. Unknown is not zero, false, completed or absent. Existing authorized access to the correct source account and records; no new login, credentials, installation or permission grant is included. Responsible lawyer/operations reviewer approves scope, definitions and any later action. AI optional; use only approved minimized data and retain originals separately. Legacy Reports is documented as a view, not a universal CSV export. Migrated pay-per-lead UI/export schema was not verified here. The live account, entitlement, exact headers, records and field coverage have not been observed. Recipe acquisition / manual mapping instructions Identify the account’s reporting version first Location: Existing LSA inbox banner or redirect; account migration notice Read the current account notice and preserve the observed interface/version. Legacy and migrated reports must not be silently combined. If migrated, obtain the actual current reporting menu and historical evidence from the account owner. Verification: Migration is phased. Google says historical LSA performance reports will not migrate, advises screenshots if needed now, and describes a historical download as forthcoming. No assumed downloadable archive. https://support.google.com/google-ads/answer/17213585?hl=en Capture the actual legacy report and status evidence Location: Lead inbox > menu > Reports; menu > Profile & Budget; Google Ads > Campaigns > Change history For two equal-length comparable periods, manually preserve report totals, displayed lead types, charges/credits, dates and screenshots. Read ad status, schedule, hours, service areas and budget indicators without editing. Expand relevant existing change-history entries manually. Verification: A point-in-time setting does not prove historical state. An ad failing to appear in one personal search does not prove non-delivery. https://support.google.com/localservices/answer/6226265?hl=en https://support.google.com/localservices/answer/12491365?hl=en https://support.google.com/localservices/answer/7435507?hl=en https://support.google.com/google-ads/answer/2454137?hl=en Make the checked, minimized handoff Location: Restricted original workbook > separate analysis workbook > Scope worksheet Create period rows only from captured figures; keep charged leads, all leads and credited leads distinct. Include migration, timezone, current-period incompleteness and missing historical settings in Scope. Keep untouched original exports/screenshots and the identifying source map in restricted firm storage. Build a separate minimized analysis file; do not hide raw client data on another tab. Include the complete Scope/coverage note in the AI-visible workbook or prompt. Use aliases and administrative metadata only. Unknown is not zero, false, completed or absent. Verification: Every field has an observed source or an explicit missing reason; staff assignments are marked editorial, not native. https://support.microsoft.com/en-us/excel/merge-queries-power-query https://support.google.com/localservices/answer/6226265?hl=en Do not proceed when - No comparable periods, migration/reporting discontinuity, absent historic report evidence or unverified current interface. Scope template requirements Full approved scope, source account aliases, date filters, date basis/timezone, as-of capture time, definitions, source-to-alias map provenance, matching rules, inspected/excluded records, permission/privacy limits, missing-data reasons, coverage and responsible reviewer. Include recipe-specific policies, versions and tests. Scope must be inside the AI workbook or pasted packet, not merely a separate unprovided file. Old examples and validation limits Legacy synthetic examples and negative cases belong to their old prompts. They do not automatically test the native route and must not be fed into a new prompt without an explicit reviewed mapping and separately approved test design. These new files contain no synthetic values, source exports, account results or live-test evidence. Documentation-checked component path; proposed workflow, not tested Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Local validation covers only exact scaffold schemas, placeholder presence, blank CSV rows and required warnings. It does not establish live account coverage, native export validity, successful integration or completed workflow tests.