Conversions go-live: the call runbook

Look up Shawna Rocha (phone ending 3908) (came in 7/15) and caller with phone ending 1268 (7/16). Both should exist there. Tell Michael the result and he purges the final 2 CareCompass copies. The other 12 are already purged and verified.

Three things can send Attend Lead events today: the GHL workflow's native FB Conversion API action (confirmed still firing), the attend-capi-sync script (form flows), and CareCompass (test-coded, fires on arrival). Recommended: webhook-connected flows hand off to CareCompass; turning off the GHL action in the Cincinnati workflow becomes part of the cutover.

Clearing the Meta test code is blocked by a known save bug in the Conversion Destinations panel. Michael has the fix scoped (including the new credential-merge semantics). Decide: ship standalone this week, or bundle with the first Google UI touches.

Once 1 + 2 land: clear TEST38746 from the Attend destination, confirm one real event on the production pixel (Events Manager Overview tab, not Test), watch match quality for 24h, confirm counts match the step-1 decision. Michael runs it and reports.

In Attend's Google Ads. Secondary means observed only, no Smart Bidding impact: it is the Google analog of Meta's test-events lane for the validation phase. Promote to Primary at go-live.

Ahron: create or designate the CareCompass Google Cloud project, set up the OAuth consent screen branded as CareCompass, and submit the application for CareCompass's own Google Ads developer token. Google's review takes days to weeks, so the clock should start now even though the connect-flow UI comes later.

Either validate the merged adapter now with an interim credential (an OAuth login limited to Attend's account under existing agency API access), or wait for CareCompass's own token and validate through the real flow. Standing rule either way: credentials scoped to Attend only, nothing MCC-wide stored in CareCompass.

Before any Google wiring decision: what that workflow action actually sends and when it skips (it skipped on the call leads we observed). Same sender-of-record question as step 1, answered on facts.

Future CareCompass customers click Connect, sign into Google or Meta, pick their ad account from a list, done. No tokens, no account IDs, credentials inherently scoped to the customer's own accounts. The merged adapters and destination storage already support this; the connect flow is a UI + OAuth-redirect feature on top. Michael delivers a UX research pass and spec; Ahron scopes it into the roadmap.

Recap the outage: O5 code was published before its migration, and intake returned 500 on every inbound lead until migrations 0039 through 0043 were applied. The rule: apply migrations through the ledgered channel BEFORE publishing code that needs them, with the manifest as the checklist. Michael files the small PR flipping 0038-0043 to applied so the ledger matches the live database.

Only Ahron can Republish the production deployment today. Options: Trey gets Publisher access, or publishes stay Ahron-only with a ping protocol. Note that his v223 publish carried fire-on-arrival live without coordination and it worked out fine, so either cadence is viable.