Summary of work done

Ran the prescribed automation runner from the canonical repo after confirming the inherited worktree path was stale. The machine-readable source of truth is /Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/output/gclid-propagation-automation/daily-2026-05-27T10-22-15-047Z/daily-gclid-propagation-report.json.

Runner status was completed-with-blockers on the canonical-local-repo surface. Vault loading, LITIFY_ORG validation, CallRail key detection, and Google service account detection all passed. No Salesforce writes were made by the webform lane because one conflicting intake GCLID remains. Google Ads sheet sync ran in dry-run mode only.

CallRail lane reviewed the current apply artifact from scheduled-2026-05-27T10-05-05Z. That artifact shows 94 CallRail calls with GCLID, 91 matched Salesforce call logs, 3 unmatched CallRail calls, 0 conflicts, and 2 safe CallRail-driven call log updates plus 2 intake updates already performed by the scheduled CallRail sync before this audit. This daily runner itself did not perform any new apply action.

Live findings

Before and after counts were unchanged during this run: 553 intakes with GCLID, 59 matters with GCLID, 108 CallRail logs with GCLID, and 94 intakes with UTM source. Seven-day snapshot: 130 intakes, 17 with GCLID, 38 matters all blank for GCLID, 332 CallRail logs with 14 GCLID and 114 linked blank GCLID, 12 webforms with GCLID and only 5 linked to intake.

The remaining webform blocker is intake INT-26042754516 where linked webforms carry two different GCLIDs and the existing intake GCLID differs from one of them. Conflict CSV: /Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/output/webform-gclid-sync/daily-dry-run-2026-05-27T10-22-15-047Z/webform-gclid-conflicts.csv.

Outlook, Intaker, and Speed AI audit

Website intake emails:

Intaker emails:

Speed AI and call cross-reference: