# Check original brand and marketing source Canonical page: https://agents.paretoid.com/workflows/check-original-brand-and-marketing-source/ Category: CRM & Follow-up Practice relevance: cross-practice. A general operational method. Review the stated tool and jurisdiction limits before use. Jurisdiction/provider scope: Find missing or conflicting brand/source data without overwriting first-touch history. Status: Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified. Verification: Source methods and reported problems have been reviewed. We have not run the adapted workflow. The sample below describes expected behavior on synthetic data, not a customer result. ## The problem Find missing or conflicting brand/source data without overwriting first-touch history. Why it matters: Lost or overwritten source details can make the wrong brand or campaign appear responsible for an inquiry. Checking current fields and supplied history helps the firm find attribution conflicts without inventing missing origins. ## Sources and evidence - pain: [Pain evidence: Public discussion](https://www.reddit.com/r/LawFirmMarketing/comments/1wub11m/comment/pd1q2lg/) author post/comment 2026-09-30. A two-brand firm wants original brand and source retained through the lead lifecycle. - method: [Method: Lawmatics source matching](https://help.lawmatics.com/en/articles/10699987-callrail-integration) The guides describe CallRail attribution, UTM matching, and custom fields. A custom brand field does not establish full brand isolation or separate sending identities. - method: [Method: Lawmatics source matching · supporting guide 2](https://help.lawmatics.com/en/articles/15063044-marketing-tracking-overview) Additional official capability reference. The complete adapted recipe has not been tested. - method: [Method: Lawmatics source matching · supporting guide 3](https://help.lawmatics.com/en/articles/10699769-types-of-custom-fields) Additional official capability reference. The complete adapted recipe has not been tested. Source checked: October 15, 2026. Pain accounts are self-reported. Documentation supports components; this adapted recipe and prompt have not been tested. Several CRM jobs come from the same firm discussion, not independent firms. ## Suggested approach Start when: New tracked inquiry or weekly attribution audit 1. compare tracking-number/UTM rules, original source fields and brand assignment 2. Keep source references and report unknowns instead of filling gaps. 3. The responsible reviewer checks the report before any separately approved action. ## What you need - 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. - 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 Documentation-checked component path; proposed workflow, not tested - No universal brand field or export of full old/new field history was verified. CallRail first-touch data depends on tracking actually installed. Access and setup: - The live account, entitlement, exact headers, records and field coverage have not been observed. ### 1. Ask the in-app assistant for the source report Tool: Lawmatics Merlin Copilot, optional Location: Left navigation > Merlin > Copilot 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. Prompt: ```text For [SCOPE], return existing current Source, Campaign and Created At values and our recorded original-brand/original-source fields [EXACT FIELDS] if present. Identify unavailable fields. Do not claim these current values are immutable first-touch history. Return record references or a report; do not change attribution. ``` Expected output: A report/one-time export or explicit unsupported/missing-field result; exact custom query coverage is not promised. Next step: Check actual fields and records, then use the native CSV path where a report is returned. Prose alone does not certify completeness. Check before continuing: 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. Execution status: Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Step 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 ### 2. Get the actual Lawmatics rows Tool: Lawmatics Location: Reports > Custom Reports > existing matter report > eye/view icon > Export Use an existing authorized report, or have its owner prepare a targeted report with Source, Campaign, Created At and exact existing original-brand/original-source fields. 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. Next step: Open in restricted Excel; compare rows to matter records before preparing aliases. Check before continuing: 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. Execution status: Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Step 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 ### 3. Capture the source evidence and present mapping Tool: CallRail and Lawmatics Location: CallRail Analytics > Activity > Call log > Timeline; Lawmatics phone icon > Assigned / Unassigned / All Callers; Settings > Marketing Sources Manually capture the relevant first-touch/call source evidence and the existing mapping values. Inspect source and campaign settings without saving. Separately collect retained historical form/call captures or logged field-change evidence showing original value, later value and timestamp. Expected output: Current mapping plus an evidence ledger; a current snapshot is not history. Next step: Assign evidence IDs; copy only brand/source labels and timestamps into the analysis workbook. Check before continuing: Lawmatics CallRail matching uses phone numbers; later calls do not overwrite existing source/campaign. Settings changes affect subsequent calls. Current rules cannot prove past configuration. Execution status: Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Step documentation: https://support.callrail.com/hc/en-us/articles/5711366294285-Viewing-caller-timelines-with-visitor-tracking https://help.lawmatics.com/en/articles/10699987-callrail-integration ### 4. Make the checked, minimized handoff Tool: Excel / source-record reviewer Location: Restricted original workbook > separate analysis workbook > Scope worksheet Keep current_field, original_capture and change_evidence separate. Do not reconstruct first brand from the latest landing page. 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: Attribution(lead_alias,current_brand,current_source,current_campaign,current_capture_at,original_brand,original_source,original_capture_at,change_evidence_ref,coverage); SourceHistory(lead_alias,field,old_value,new_value,changed_at,source_ref) Next step: Format each approved range as a named table. Carry source-row references and coverage into the analysis workbook. Check before continuing: Every field has an observed source or an explicit missing reason; staff assignments are marked editorial, not native. Execution status: Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Step documentation: https://support.microsoft.com/en-us/excel/merge-queries-power-query https://help.lawmatics.com/en/articles/10699825-matter-profile-overview ### 5. Ask AI to inspect the checked inputs Tool: Excel Copilot, optional Location: Analysis workbook > Copilot icon at lower right > Chat only Open the minimized workbook containing the named tables and Scope. Paste the exact prompt; if unavailable, perform the same rule checks manually. Prompt: ```text Use Attribution, SourceHistory and Scope. Compare current source/brand against recorded original captures only. For each mismatch cite the original and later evidence and timestamp. Without old/new/timestamp evidence, say original attribution not verifiable. Separate wrong-current-value, legitimate later-touch difference and unknown history. Do not overwrite fields, infer causal marketing credit or invent a brand. ``` Expected output: Evidence-bounded discrepancy list. Next step: Copy checked results into a new Review sheet, retaining source references and unresolved blockers. Check before continuing: No current field or present mapping alone establishes original source. Execution status: Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Step documentation: https://support.microsoft.com/en-us/excel/copilot/get-started-with-copilot-in-excel ### 6. Human review and final action Tool: Responsible firm reviewer Location: Internal Review worksheet / review document Marketing and intake reviewers validate each discrepancy against preserved original evidence. Save a factual correction proposal. Expected output: Reviewed attribution proposal and unknown-history list. Next step: Any correction goes to the exact original CRM record after separate approval. Check before continuing: Never reattribute historical leads merely to improve campaign results. Execution status: Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Step documentation: https://help.lawmatics.com/en/articles/10699987-callrail-integration ## What you will get source-review.csv: lead_alias, rule_ids, brand_conflict, original_source_evidence, later_touch_evidence, proposed_rule_test ## Human review and limits Do not combine separate firms' clients merely because a person appears in both. No blind retroactive attribution changes or cross-brand communications. 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: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed. ## Original prepared-input schema leads.csv: lead_alias, brand_id, original_source, later_source, tracking_number_token, utm_source, utm_campaign tracking-rules.csv: rule_id, brand_id, number_token, utm_match, priority; first-touch-policy.txt: approved rules and scope source-history.csv: lead_alias, field, old_value, new_value, changed_at, source_ref; absence means overwrite history is unknown Synthetic example input: ```text L1: one tracking token maps to two brands L2: source-history H2 records original_source changing from Organic to Paid, with timestamp and source_ref L3: no source evidence ``` Expected synthetic output: ```text L1: ambiguous rule L2: observed source-history change citing H2; review against approved policy L3: unknown, no guessed attribution ``` Failure check: Do not combine separate firms' clients merely because a person appears in both. No blind retroactive attribution changes or cross-brand communications. ## 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/g08-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/g08/START-HERE.txt) — Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits - [Input template: leads.csv](https://agents.paretoid.com/assets/starter-kits/g08/leads.csv) — Header-only input template; preserve exact names and order - [Synthetic input: leads.csv](https://agents.paretoid.com/assets/starter-kits/g08/leads-example.csv) — Fabricated sample rows for an offline manual trial - [Input template: tracking-rules.csv](https://agents.paretoid.com/assets/starter-kits/g08/tracking-rules.csv) — Header-only input template; preserve exact names and order - [Synthetic input: tracking-rules.csv](https://agents.paretoid.com/assets/starter-kits/g08/tracking-rules-example.csv) — Fabricated sample rows for an offline manual trial - [Input template: source-history.csv](https://agents.paretoid.com/assets/starter-kits/g08/source-history.csv) — Header-only input template; preserve exact names and order - [Synthetic input: source-history.csv](https://agents.paretoid.com/assets/starter-kits/g08/source-history-example.csv) — Fabricated sample rows for an offline manual trial - [Output template: source-review.csv](https://agents.paretoid.com/assets/starter-kits/g08/source-review.csv) — Header-only output template; preserve exact names and order - [Expected output: source-review.csv](https://agents.paretoid.com/assets/starter-kits/g08/source-review-example.csv) — Hand-authored synthetic expected result; not an executed workflow result - [Policy/input template: first-touch-policy.txt](https://agents.paretoid.com/assets/starter-kits/g08/first-touch-policy.txt) — Required source/policy preparation scaffold; not populated with firm instructions - [Synthetic policy/input: first-touch-policy.txt](https://agents.paretoid.com/assets/starter-kits/g08/first-touch-policy-example.txt) — Fixture-only context; not an approved production policy - [Synthetic fixture expectations](https://agents.paretoid.com/assets/starter-kits/g08/fixture-expectations.txt) — Acceptance targets and failure checks; no claim of workflow execution - [Review prompt](https://agents.paretoid.com/assets/starter-kits/g08/starter-prompt.txt) — Copyable offline review prompt; no executable automation - [Setup and prerequisites](https://agents.paretoid.com/assets/starter-kits/g08/README.txt) — Recipe-specific setup, evidence sources and usage boundaries - [Native input scaffold: Attribution](https://agents.paretoid.com/assets/starter-kits/g08/native-attribution-template.csv) — Empty editorial table for Attribution; populate from verified source evidence after reviewed mapping; not a native export - [Native input scaffold: SourceHistory](https://agents.paretoid.com/assets/starter-kits/g08/native-sourcehistory-template.csv) — Empty editorial table for SourceHistory; populate from verified source evidence after reviewed mapping; not a native export - [Native input scaffold: Scope](https://agents.paretoid.com/assets/starter-kits/g08/native-scope-template.txt) — Approved text input for Scope; complete from verified evidence and include in the AI-visible packet - [Native input mapping and scope guide](https://agents.paretoid.com/assets/starter-kits/g08/NATIVE-INPUT-MAPPING.txt) — Old-file-to-native-input compatibility map, acquisition requirements, privacy and blocking gates ## Optional original prepared-input prompt Destination: Your firm-approved AI assistant · prepared files This original prompt uses its own prepared-input schema. Do not mix it with native-step tables without the supplied mapping. ```text Audit these anonymized lead records and tracking rules. Find shared tracking numbers, broad UTM matches, missing brand IDs and overwritten original-source fields. Produce proposed rule corrections and synthetic tests. Keep first-touch and later touches separate. Never guess a missing source or write back changes. INPUTS leads.csv: lead_alias, brand_id, original_source, later_source, tracking_number_token, utm_source, utm_campaign tracking-rules.csv: rule_id, brand_id, number_token, utm_match, priority; first-touch-policy.txt: approved rules and scope source-history.csv: lead_alias, field, old_value, new_value, changed_at, source_ref; absence means overwrite history is unknown Use source-history rows to support any overwrite finding. Current fields alone cannot prove an overwrite. If history is absent, report only current-field conflicts and mark overwrite history unknown. OUTPUT source-review.csv: lead_alias, rule_ids, brand_conflict, original_source_evidence, later_touch_evidence, proposed_rule_test Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing. ``` Proposed / not tested · editorial prompt Published by Law Firm Agents. Proposed adaptation; not tested. Not legal advice.