Investigate a drop in Local Services Ads leads
Get the source data and prepare the review

Documentation-checked component path; proposed workflow, not tested

WHAT WAS CHECKED
Public official documentation and supplied candidate artifacts only. No product login, account exports, client data, installation, credential access, external writes, advertising spend, template imports or live tests. Proposed prompts do not prove a feature supports every requested field. Missing required source data blocks execution.

BEFORE YOU START
- 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.

DATA ACQUISITION LIMITS
- Legacy Reports is documented as a view, not a universal CSV export. Migrated pay-per-lead UI/export schema was not verified here.

STOP IF
- No comparable periods, migration/reporting discontinuity, absent historic report evidence or unverified current interface.

KEEP THE ANALYSIS COPY SEPARATE
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.

INPUT FORMAT LIMIT
All capitalized analysis tables and alias fields are editorial contracts. Native exports retain real vendor headers; mapping is explicit. No blank starter template is evidence of available data.

NATIVE REVIEW INPUTS
version: 1
status: Requires distinct native-input templates or an explicit reviewed mapping; existing kit is not drop-in compatible
compatibleWithoutMapping: False
existingKitFilesInspected: - file: changes.csv
firstLine: change_id,changed_at,setting,old_value,new_value
- file: lead-decline-review.csv
firstLine: period,observed_metric,comparator,difference,coverage,possible_explanation,next_evidence_check
- file: lsa-periods.csv
firstLine: period_start,period_end,lead_id,lead_type,charged_amount,credit_status,currency
- file: scope.txt
firstLine: G03: scope.txt
requiredNativeInputs: - name: Periods
kind: editorial_table
proposedDistinctTemplate: native-periods-template.csv
columns: - period_alias
- start
- end
- lead_metric
- lead_count
- spend
- credits
- currency
- source_ref
acquisitionRequirement: Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts.
- name: Changes
kind: editorial_table
proposedDistinctTemplate: native-changes-template.csv
columns: - change_at
- setting
- old_value
- new_value
- source_ref
acquisitionRequirement: Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts.
- name: Scope
kind: approved_text_section
proposedDistinctTemplate: native-scope-template.txt
requiredContent: 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.
templateFilesCreatedByThisTask: False
requiredGate: Kit owner must add the named inputs or document field-level mapping before replacing an existing kit prompt. Preserve the old kit contract; never rename headers without acquiring missing evidence.

OPEN THE INPUT MAPPING GUIDE
NATIVE-INPUT-MAPPING.txt
Use the distinct native input scaffolds listed below. Complete them from the acquired, reviewed evidence and include every required scope section in the AI-visible packet. Existing synthetic examples exercise the original review prompt only. They are not acquired evidence or a test of this native chain.

Periods: native-periods-template.csv
Changes: native-changes-template.csv
Scope: native-scope-template.txt

STEP 1: Identify the account’s reporting version first
Tool: Local Services Ads / Google Ads
Open: Existing LSA inbox banner or redirect; account migration notice
Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included.
AI role: not_an_ai_step

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.

Expected output: Legacy/migrated status and historical coverage note.
Use it next: Use the legacy capture below only while that inbox exists; otherwise retain a current-UI verification blocker.
Check: 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.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://support.google.com/google-ads/answer/17213585?hl=en

STEP 2: Capture the actual legacy report and status evidence
Tool: Local Services Ads
Open: Lead inbox > menu > Reports; menu > Profile & Budget; Google Ads > Campaigns > Change history
Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included.
AI role: not_an_ai_step

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.

Expected output: Report/settings evidence packet with captured values and source images; not a fabricated CSV.
Use it next: Transcribe reviewed aggregate figures into Periods and observed changes into Changes.
Check: A point-in-time setting does not prove historical state. An ad failing to appear in one personal search does not prove non-delivery.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
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

STEP 3: Make the checked, minimized handoff
Tool: Excel / source-record reviewer
Open: Restricted original workbook > separate analysis workbook > Scope worksheet
Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included.
AI role: not_an_ai_step

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.

Expected output: Periods(period_alias,start,end,lead_metric,lead_count,spend,credits,currency,source_ref); Changes(change_at,setting,old_value,new_value,source_ref)
Use it next: Format each approved range as a named table. Carry source-row references and coverage into the analysis workbook.
Check: Every field has an observed source or an explicit missing reason; staff assignments are marked editorial, not native.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://support.microsoft.com/en-us/excel/merge-queries-power-query
https://support.google.com/localservices/answer/6226265?hl=en

STEP 4: Ask AI to inspect the checked inputs
Tool: Excel Copilot, optional
Open: Analysis workbook > Copilot icon at lower right > Chat only
Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included.
AI role: downstream_application_ai

Open the minimized workbook containing the named tables and Scope. Paste the exact prompt; if unavailable, perform the same rule checks manually.

PASTE THIS PROMPT
Use Periods, Changes and Scope. Verify equal duration, same account, timezone and metric definitions. Compute observed count/spend differences; identify whether lead mix, credits or a migration/reporting break coincides. Separate documented changes from hypotheses and provide the smallest read-only check for each hypothesis. Missing old settings or unobserved platform changes remain unknown. Do not name a cause without evidence, recommend an automatic budget increase or change ads.

Expected output: Factual anomaly brief with discriminating checks and coverage blockers.
Use it next: Copy checked results into a new Review sheet, retaining source references and unresolved blockers.
Check: A spend or budget association is not causal proof; no fabricated historical series.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://support.microsoft.com/en-us/excel/copilot/get-started-with-copilot-in-excel

STEP 5: Human review and final action
Tool: Responsible firm reviewer
Open: Internal Review worksheet / review document
Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included.
AI role: not_an_ai_step

Marketer verifies the arithmetic and checks documented alerts/changes. Save the brief and decide which further account evidence is needed.

Expected output: Reviewed explanation hypotheses and next checks.
Use it next: Any appeal, support message, budget, bid or targeting change requires separate approval.
Check: Migrated-account reporting remains blocked until actual current menus/schema are verified.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://support.google.com/google-ads/answer/17213585?hl=en
https://support.google.com/localservices/answer/12491365?hl=en

ACCOUNT AND SOURCE CHECKS STILL NEEDED
- The live account, entitlement, exact headers, records and field coverage have not been observed.

USING THE FILES IN THIS KIT
Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs.

The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.
