G20: native input mapping Check Google Ads inquiry counts 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 Actions -> native-actions-template.csv Exact columns: action_alias,event_definition,source,count_setting,primary_secondary,window,evidence_ref Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. AggregateCounts -> native-aggregatecounts-template.csv Exact columns: system,metric,period,count,scope_ref Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. ExistingTests -> native-existingtests-template.csv Exact columns: test_id,expected_event,observed_events,evidence_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 conversion-actions-template.csv Original first line: action_id,source,event_definition,count_setting,primary_or_secondary,attribution_model,conversion_window,timezone measurement-plan-template.txt Original first line: Approved inquiry definition: [required] conversion-actions-template.csv: Map action_id to verified action_alias; primary_or_secondary to primary_secondary; conversion_window to window. Keep attribution_model/timezone in Scope. Add actual settings evidence_ref; never pretend these are native export headers. measurement-plan-template.txt: Carry the complete approved inquiry, comparison, timezone and attribution definitions into Scope. It contains no actual AggregateCounts. synthetic-test-plan-template.csv: Expected test_id/action_ids/event_sequence/expected_business_inquiries describe a plan only. They cannot populate observed_events or claim tests ran. ExistingTests requires separate actual controlled-test evidence; otherwise mark absent/untested. NEW native-aggregatecounts-template.csv: Acquire real Ads/GA4 report metrics and their scopes as described. No existing starter file supplies these counts. 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. Aggregate counts cannot prove real inquiries or deduplication. No production-event test performed. The live account, entitlement, exact headers, records and field coverage have not been observed. Recipe acquisition / manual mapping instructions Read conversion-action definitions and settings Location: Goals > Conversions > Summary > selected conversion action > settings/details Capture actual action name/source, primary/secondary status, Count, windows and the business-event definition. If Edit settings is needed to view Count, inspect without changing or saving. Record whether the attribution setting makes a control managed in Analytics. Verification: One counts per ad click/action, not unique people across all clicks/actions. Changing it affects future reporting. https://support.google.com/google-ads/answer/3438531?hl=en https://support.google.com/google-ads/answer/3123169?hl=en https://support.google.com/google-ads/answer/2375435?hl=en Download the actual aggregate reports Location: Ads relevant statistics table > selected date/columns > Download > Excel CSV/XLSX; GA4 Reports > selected existing report > Share this report > Download File > Download CSV Preserve original reports and date/filter/timezone context. Record whether Ads uses interaction-date or conversion-time columns and which action/metric the GA4 report shows; capture threshold/coverage warnings. Verification: An Ads/GA4 total mismatch is not proof of duplicate firing. Attribution date, windows, imports and primary/secondary scopes can differ. https://support.google.com/google-ads/answer/2404176?hl=en https://support.google.com/analytics/answer/9317657?hl=en https://support.google.com/google-ads/answer/2375435?hl=en Acquire implementation evidence safely Location: GTM existing container/workspace configuration; future controlled test: Workspace > Preview > Tag Assistant For this read-only recipe use already recorded configuration/test evidence, or return a test-plan blocker. A separately approved technician can later inspect event order in Tag Assistant using a synthetic isolated test path. No preview session or form submission is run here. Verification: Preview is not guaranteed side-effect-free: tags/forms may still send data. Transaction IDs are not reported in Ads, so a report cannot prove deduplication; unique IDs must be verified in implementation/test evidence. https://support.google.com/tagmanager/answer/6107056?hl=en https://support.google.com/google-ads/answer/6386790?hl=en Make the checked, minimized handoff Location: Restricted original workbook > separate analysis workbook > Scope worksheet Build Actions, AggregateCounts and ExistingTests with actual definitions. Scope includes attribution/date differences and untested repeat-submit scenarios. 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/google-ads/answer/3438531?hl=en Do not proceed when - Missing event definition, implementation evidence, comparable windows or isolated approved test path. 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.