Compare agency claims with Google Ads change history
Get the source data and prepare the review

Official native navigation documented; editorial AI analysis and human-review chain not personally tested

WHAT WAS CHECKED
Public official product documentation only. No product login, account write, real client data, installation, or live workflow test. Prompts and schemas are proposed editorial adaptations; vendor documentation verifies component features, not these end-to-end recipes. Native exports retain their real headers; kit schemas require the explicit mapping steps below.

BEFORE YOU START
- Existing read-only account access is sufficient for the intended inspection; do not request edit access merely for this audit .
- An authorized copy of the agency's dated report, relevant deliverable links, campaign scope and agreed reporting period. Preserve the agency's wording and original source location.
- Firm-approved Excel Copilot or Acrobat AI access only for the named optional AI step; read-only native source acquisition is separate.

DATA ACQUISITION LIMITS
- History covers the past two years. Some account-level settings and changes by Google representatives may not be listed. Entry details can be limited, particularly for large batches .
- UI changes may identify the login email; automated/internal systems and API tools can use system/tool labels rather than an individual .
- History includes automated rules, Ads API and Ads Editor changes, but not password changes .
- An agency's work outside Ads and the quality or causal effect of its decisions require other evidence; this ledger cannot establish negligence or ROI.
- The official Change history guides reviewed do not verify a Download control. This path uses manual screenshot-linked capture; it does not claim the live screen lacks export.
- ads-history.csv is a manually transcribed evidence log, not a verified native export. Its change_id and actor_alias are local identifiers; preserve raw screenshots in restricted storage.

STEP 1: Open and expand the change records
Tool: Google Ads
Open: Campaigns > Change history
Access needed: See recipe prerequisites; exact firm subscription and account permissions not tested.

Set dates at the upper right and select all relevant campaigns through the Views bar. Start with no actor filter. Expand relevant entries with the adjacent arrow. Inspect User, Tool, Change type and Item changed filters only as needed and record each applied filter.

Expected output: Visible dated change records with whatever expanded details the account supplies.
Use it next: Capture screenshots and manually transcribe relevant entries into the supplied evidence table; do not search for an unverified export control.
Check: Review the correct account, dates and campaigns. Preserve truncated/missing detail as missing; do not infer an employee from a tool label.
Documentation limit: Linked official documentation supports the named feature/menu. The workflow-specific prompt, schema, mapping and reviewer rules are editorial adaptations.
Source documentation:
https://support.google.com/google-ads/answer/2454137?hl=en
https://support.google.com/google-ads/answer/19888?hl=en

STEP 2: Map claims and captured evidence
Tool: Excel and original agency report
Open: agency-claims.csv, ads-history.csv and review-scope.txt
Access needed: See recipe prerequisites; exact firm subscription and account permissions not tested.

Assign each claim a claim_id and copy its actual claimed_date, campaign reference, claimed_action and deliverable_reference. For each screenshot assign a local change_id and record displayed changed_at, known timezone, actor_alias, campaign_id, change_type and visible before_value/after_value only. Keep screenshot references in review-scope.txt or a source-index worksheet. If only campaign names are visible, assign consistent local aliases and state that they are not numeric Ads IDs.

Expected output: Claim and manual-history tables matching the kit headers, plus a capture manifest with scope, filters, timestamp, screenshot references and gaps.
Use it next: Create a minimized analysis workbook from the checked tables and approved deliverable descriptions; keep identifying screenshots separately.
Check: Check every transcription against its screenshot. Distinguish outside-Ads strategy/research/creative claims from account-edit claims. Unknown dates/timezones remain unknown.
Documentation limit: Linked official documentation supports the named feature/menu. The workflow-specific prompt, schema, mapping and reviewer rules are editorial adaptations.
Source documentation:
https://support.google.com/google-ads/answer/2454137?hl=en
https://support.microsoft.com/en-us/excel/tutorial-import-data-into-excel-and-create-a-data-model

STEP 3: Compare claims with evidence
Tool: Excel Copilot
Open: Analysis workbook > Copilot icon at lower right > Chat only
Access needed: See recipe prerequisites; exact firm subscription and account permissions not tested.

Paste all review-scope.txt contents, capture limitations and source-index references into a visible Scope worksheet/table in this same minimized analysis workbook, or directly into the prompt. Use the prompt against the claims, history and Scope data. If Copilot is unavailable, compare claims manually using the same status definitions.

PASTE THIS PROMPT
Compare these dated agency claims with the verified manual Google Ads change-history capture and linked deliverables. For each claim return claim ID, source reference, matching evidence IDs, supported / unverified / inconsistent status, reasoning, coverage limitations, and a neutral clarification question. Use inconsistent only when affirmative evidence contradicts a claim. Separate outside-Ads work. Do not equate edit volume with quality, infer causation or misconduct, contact the agency, or undo changes. Use only this workbook and approved supplied deliverable descriptions; do not search private files, change the workbook or send anything. The complete review-scope data must be in this workbook or pasted below; if it is absent, stop and request it. [PASTE COMPLETE REVIEW-SCOPE DATA IF NOT IN SCOPE WORKSHEET]

Expected output: claim_id,source_reference,matching_evidence_ids,status,reasoning,coverage_limits,clarification_question.
Use it next: Copy the ledger to the internal review sheet and reopen disputed evidence.
Check: A missing match is unverified, not proof that work was not performed. Edit counts do not measure quality or explain performance causally.
Documentation limit: Linked official documentation supports the named feature/menu. The workflow-specific prompt, schema, mapping and reviewer rules are editorial adaptations.
Source documentation:
https://support.microsoft.com/en-us/excel/copilot/get-started-with-copilot-in-excel
https://support.google.com/google-ads/answer/19888?hl=en

STEP 4: Approve the factual agency questions
Tool: Firm reviewer
Open: Internal ledger and original agency report
Access needed: See recipe prerequisites; exact firm subscription and account permissions not tested.

Check contradictory claims against affirmative evidence, correct unsupported assessments and select neutral questions for discussion. Any external message is separately reviewed and authorized.

Expected output: Evidence-linked claim ledger, missing-evidence list and approved discussion questions.
Use it next: Use the firm’s existing agency communication process; this path does not send a message.
Check: Do not undo Ads changes, accuse misconduct or claim negligence/ROI from this evidence alone.
Documentation limit: Linked official documentation supports the named feature/menu. The workflow-specific prompt, schema, mapping and reviewer rules are editorial adaptations.
Source documentation:
https://support.google.com/google-ads/answer/19888?hl=en

ACCOUNT AND SOURCE CHECKS STILL NEEDED
- Account interface, access and live report contents were not personally tested.
- No native Google Ads/Business Profile AI chat is claimed by this recipe.

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.
