Match ad spend with recorded intake stages
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
- Aggregate spend alone cannot establish individual attribution. Existing CRM IDs/source capture and historical stage events may be absent.

STOP IF
- Missing existing cross-tool map, attribution window, comparable scope/currency or documented stage evidence.

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: ads.csv
firstLine: source_id,campaign_id,period,spend,currency,attribution_token
- file: attribution-review.csv
firstLine: source_id,spend,unique_inquiries,booked_consults,confirmed_retained,unmatched_count,denominator,coverage_warning
- file: intake.csv
firstLine: intake_alias,attribution_token,source_id,stage,stage_at
- file: scope.txt
firstLine: G02: scope.txt
- file: stage-dictionary.csv
firstLine: stage,approved_definition
requiredNativeInputs: - name: Spend
kind: editorial_table
proposedDistinctTemplate: native-spend-template.csv
columns: - campaign_alias
- period
- currency
- spend
- 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: Intake
kind: editorial_table
proposedDistinctTemplate: native-intake-template.csv
columns: - lead_alias
- campaign_alias
- created_at
- recorded_stage
- stage_at
- as_of
- 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.

Spend: native-spend-template.csv
Intake: native-intake-template.csv
Scope: native-scope-template.txt

STEP 1: Download scoped ad-spend data
Tool: Google Ads
Open: Correct customer account > Campaigns statistics table > date/columns/segments > Download > Excel CSV or XLSX
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

Display campaign identity, period, cost and selected measurement columns. Download the visible table after checking account, currency, timezone, dates and filters. Preserve native headers, totals and the source file.

Expected output: Native campaign-period statistics export.
Use it next: Open locally; capture all report settings in Scope.
Check: The download is aggregate advertising data, not a click-to-client ledger. Do not multiply each campaign spend by its number of lead rows.
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/2404176?hl=en

STEP 2: Ask the in-app assistant for the source report
Tool: Lawmatics Merlin Copilot, optional
Open: Left navigation > Merlin > Copilot
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: source_application_ai

With an already approved seat and firm-wide reporting access, paste the prompt. Open the returned report/export or inspect its preview; if unavailable or incomplete, use the native report route below. Do not accept mutation previews, routines or feature-request sending.

PASTE THIS PROMPT
Return a read-only intake matter report for [COHORT] with existing Source, Campaign, Created At, Converted At, Status and Stage, plus [EXACT EXISTING ATTRIBUTION FIELD] if recorded. Include record references where supported. Do not backfill IDs, infer sources, estimate missing stages or value, upload conversions, edit records or send data to Google.

Expected output: A report/one-time export or explicit unsupported/missing-field result; exact custom query coverage is not promised.
Use it next: Check actual fields and records, then use the native CSV path where a report is returned. Prose alone does not certify completeness.
Check: Existing firm-approved AI entitlement and data handling approval are prerequisites. Lawmatics Merlin reporting can operate at firm scope; do not use it across ethical walls or assume matter-level permissions protect aggregate/search output. The detailed Copilot article and September 2026 release notes describe availability; the suite overview still contains a stale Coming Soon heading. Verify actual account access, with no purchase or permission changes.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://help.lawmatics.com/en/articles/16139872-merlin-copilot
https://help.lawmatics.com/en/articles/15890617-merlin-ai-suite-overview
https://help.lawmatics.com/en/articles/15788585-recent-updates-q3-2026

STEP 3: Get the actual Lawmatics rows
Tool: Lawmatics
Open: Reports > Custom Reports > existing matter report > eye/view icon > Export
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

Use an existing authorized report, or have its owner prepare a targeted report with Source, Campaign, Created At, Converted At, Status, Stage and the exact existing attribution identifier if available. Record the agreed review period and matter scope, including which date field sets the range. Export the viewed report to CSV; large exports may arrive by email. Preserve headers and file unchanged. A report creation/save is a separate account write, not performed here. If no suitable report exists, use the documented Settings > Export > Export Matters route only in restricted storage, then minimize locally.

Expected output: Native matter/contact-field rows; no promise of task history, audit history, destination IDs or custom fields that the firm never recorded.
Use it next: Open in restricted Excel; compare rows to matter records before preparing aliases.
Check: A matter report may contain contact and matter fields. A contacts-only export omits matter fields. Date-created and date-converted scopes differ; exported grouping is not preserved.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://help.lawmatics.com/en/articles/10699961-exporting-custom-reports
https://help.lawmatics.com/en/articles/10699766-exporting-data
https://help.lawmatics.com/en/articles/10699953-custom-reporting-using-filters
https://help.lawmatics.com/en/articles/10699957-custom-reporting-columns-grouping

STEP 4: 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

Staff verifies existing campaign/source identifiers and approved stage definitions. Aggregate distinct lead aliases by the approved attribution key and cohort first, then join to one Spend row per campaign/period/currency. Keep current-stage/as-of reporting separate from event-in-period counts; earlier stages require their real timestamped records. Never fuzzy-match names or reconstruct absent click IDs. 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: Spend(campaign_alias,period,currency,spend,source_ref); Intake(lead_alias,campaign_alias,created_at,recorded_stage,stage_at,as_of,source_ref); Scope(cohort,attribution_window,stage_dictionary,matching_coverage)
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://help.lawmatics.com/en/articles/10699957-custom-reporting-columns-grouping
https://help.lawmatics.com/en/articles/10699953-custom-reporting-using-filters

STEP 5: 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 Spend, Intake and Scope. Validate unique spend keys and lead aliases before joining. Aggregate intake counts under the supplied cohort and stage definitions, then join spend once per campaign/period/currency. Show recorded inquiries, consultations and staff-confirmed retained counts only when evidenced; keep unmatched/unknown stages and late conversions explicit. Return denominators and source cells. No causal ROI, fabricated attribution, client-level value, fuzzy matching or conversion uploads. If the existing cross-tool map or cohort definition is absent, output a blocked measurement checklist instead of results.

Expected output: A source-linked campaign/cohort table and missing-measurement list.
Use it next: Copy checked results into a new Review sheet, retaining source references and unresolved blockers.
Check: Reconcile aggregate cost back to Ads once, check stage evidence and show unmapped proportion.
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 6: 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

Marketing and intake owners approve mapping, cohort, stage meaning and arithmetic. Save a provisional report if capture is partial.

Expected output: Reviewed recorded-attribution report; no causal or profitability claim.
Use it next: Any tracking implementation or conversion upload is a separate privacy-reviewed project.
Check: No personal data, legal circumstances or client outcomes are uploaded to any ad platform.
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/2404176?hl=en
https://help.lawmatics.com/en/articles/10699957-custom-reporting-columns-grouping

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.