# Check agency reports against Ads history Canonical page: https://agents.paretoid.com/workflows/check-agency-reports-against-ads-history/ Category: Google Ads Practice relevance: cross-practice. A general operational method. Review the stated tool and jurisdiction limits before use. Jurisdiction/provider scope: Compare dated agency work claims with account change records and supporting files. Status: Proposed / not tested. The public discussion supports the problem; the method source supports only the documented features. No outcome from this adapted recipe has been verified. Verification: The linked sources support the complaint and documented method components. We have not run this recipe or verified its results. The example below is synthetic, not a customer result. ## The problem Compare dated agency work claims with account change records and supporting files. Why it matters: A summary report may not show which account changes support an agency's claims. A dated evidence comparison gives the firm specific questions to ask without treating edit volume as quality or missing records as misconduct. ## Sources and evidence - pain: [Pain evidence: Public discussion](https://www.reddit.com/r/LawFirmMarketing/comments/1qpnsdk/is_it_normal_to_have_no_idea_what_your_marketing/) ; original post 2026-01-28. A firm-side poster cannot verify what its marketing agency actually does and finds the reporting opaque. - method: [Method: Google Ads change history](https://support.google.com/google-ads/answer/2454137?hl=en) Google documents two years of change history and actor, type, and campaign filters. Not every type of work appears in account history. - method: [Method: Google Ads change history · supporting guide 2](https://support.google.com/google-ads/answer/19888?hl=en-uk) Additional official capability reference. It does not validate the complete proposed recipe. Source checked: October 15, 2026. Pain reports are self-reported and identities are unverified. Method documentation supports components, not a tested end-to-end workflow. ## Suggested approach Start when: Monthly agency report 1. cross-reference dated change claims with account change-history export and deliverable links 2. Keep row or page references and mark missing or ambiguous evidence. Do not apply the suggested changes. 3. The responsible staff member checks the draft against the source records and approves any separate action. ## What you need - 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. - Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details. ## How to use Official native navigation documented; editorial AI analysis and human-review chain not personally tested - 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. Access and setup: - Account interface, access and live report contents were not personally tested. - No native Google Ads/Business Profile AI chat is claimed by this recipe. ### 1. Open and expand the change records Tool: Google Ads Location: Campaigns > Change history 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. Next step: Capture screenshots and manually transcribe relevant entries into the supplied evidence table; do not search for an unverified export control. Check before continuing: Review the correct account, dates and campaigns. Preserve truncated/missing detail as missing; do not infer an employee from a tool label. Execution status: Official documentation checked 2026-10-15; product account and workflow not personally tested Step documentation: https://support.google.com/google-ads/answer/2454137?hl=en https://support.google.com/google-ads/answer/19888?hl=en ### 2. Map claims and captured evidence Tool: Excel and original agency report Location: agency-claims.csv, ads-history.csv and review-scope.txt 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. Next step: Create a minimized analysis workbook from the checked tables and approved deliverable descriptions; keep identifying screenshots separately. Check before continuing: Check every transcription against its screenshot. Distinguish outside-Ads strategy/research/creative claims from account-edit claims. Unknown dates/timezones remain unknown. Execution status: Official documentation checked 2026-10-15; product account and workflow not personally tested Step 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 ### 3. Compare claims with evidence Tool: Excel Copilot Location: Analysis workbook > Copilot icon at lower right > Chat only 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. Prompt: ```text 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. Next step: Copy the ledger to the internal review sheet and reopen disputed evidence. Check before continuing: A missing match is unverified, not proof that work was not performed. Edit counts do not measure quality or explain performance causally. Execution status: Official documentation checked 2026-10-15; product account and workflow not personally tested Step 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 ### 4. Approve the factual agency questions Tool: Firm reviewer Location: Internal ledger and original agency report 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. Next step: Use the firm’s existing agency communication process; this path does not send a message. Check before continuing: Do not undo Ads changes, accuse misconduct or claim negligence/ROI from this evidence alone. Execution status: Official documentation checked 2026-10-15; product account and workflow not personally tested Step documentation: https://support.google.com/google-ads/answer/19888?hl=en ## What you will get agency-claim-review.csv: claim_id, status, supporting_change_ids, supporting_files, evidence_limit, question ## Human review and limits This is a verification aid, not proof of negligence or campaign success. Review before sending questions; no changes to campaign state. The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included. What to measure: During the pilot, count findings confirmed by the reviewer, false alarms, and missing-input cases. Do not infer time or money saved. ## Original prepared-input schema agency-claims.csv: claim_id, claimed_date, campaign_id, claimed_action, deliverable_reference ads-history.csv: change_id, changed_at, timezone, actor_alias, campaign_id, change_type, before_value, after_value review-scope.txt: account alias, period, timezone, capture coverage, approved campaign IDs; exclude credentials and client data Synthetic example input: ```text CL1: budget edit with matching change record CL2: keyword research with a supplied document but no Ads edit CL3: campaign edit with no matching history or file ``` Expected synthetic output: ```text CL1: supported by the cited history row CL2: assess the separate deliverable; no Ads record expected CL3: unverified, ask a neutral question ``` Failure check: Use an incomplete manual capture or a claim outside the available two-year history. Report the coverage gap, not an accusation. ## Starter files Native blank scaffolds and original synthetic examples may use different schemas. Follow NATIVE-INPUT-MAPPING where supplied. These files do not connect accounts or install automation. - [Download starter kit](https://agents.paretoid.com/assets/starter-kits/g19-starter-kit.zip) — All inputs, synthetic examples and review notes in one ZIP. No automation is installed. - [Start here: get the sources and prepare the review](https://agents.paretoid.com/assets/starter-kits/g19/START-HERE.txt) — Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits - [Setup and review checklist](https://agents.paretoid.com/assets/starter-kits/g19/README.txt) — Required inputs, file use, review steps and limits - [Agency claims blank CSV](https://agents.paretoid.com/assets/starter-kits/g19/agency-claims-template.csv) — Blank input headers for agency-claims.csv - [Agency claims synthetic example](https://agents.paretoid.com/assets/starter-kits/g19/agency-claims-example.csv) — Synthetic test records for agency-claims.csv - [Ads history blank CSV](https://agents.paretoid.com/assets/starter-kits/g19/ads-history-template.csv) — Blank input headers for ads-history.csv - [Ads history synthetic example](https://agents.paretoid.com/assets/starter-kits/g19/ads-history-example.csv) — Synthetic test records for ads-history.csv - [Review scope template](https://agents.paretoid.com/assets/starter-kits/g19/review-scope-template.txt) — Required policy or native-input preparation aid; synthetic when marked example - [Review scope example](https://agents.paretoid.com/assets/starter-kits/g19/review-scope-example.txt) — Required policy or native-input preparation aid; synthetic when marked example - [Keyword research example](https://agents.paretoid.com/assets/starter-kits/g19/keyword-research-example.txt) — Required policy or native-input preparation aid; synthetic when marked example - [Synthetic example expected results](https://agents.paretoid.com/assets/starter-kits/g19/expected-results.txt) — Compare a pilot result with the planted exceptions ## Optional original prepared-input prompt Destination: Excel Copilot · prepared inputs This original prompt uses its own prepared-input schema. Do not mix it with native-step tables without the supplied mapping. ```text Compare the agency's dated Ads work claims against this verified manual change-history capture. For each claim, link matching records or mark it unverified, and explain limits such as work done outside Ads. Summarize questions to clarify discrepancies. Do not equate edit volume with quality, accuse anyone of fraud or undo changes. INPUTS agency-claims.csv: claim_id, claimed_date, campaign_id, claimed_action, deliverable_reference ads-history.csv: change_id, changed_at, timezone, actor_alias, campaign_id, change_type, before_value, after_value review-scope.txt: account alias, period, timezone, capture coverage, approved campaign IDs; exclude credentials and client data OUTPUT agency-claim-review.csv: claim_id, status, supporting_change_ids, supporting_files, evidence_limit, question Use only the supplied synthetic or firm-approved inputs. Cite source row or page IDs for each finding. Keep unknowns unresolved. Return a draft for the responsible staff reviewer. Do not send messages, connect accounts, change records, move money, or make legal decisions. Keep source files unchanged. If an input or permission is missing, list what is needed and stop that check. ``` Proposed / not tested · editorial prompt Published by Law Firm Agents. Proposed adaptation; not tested. Not legal advice.