Created the live child thank-you page at https://aguiarinjurylawyers.com/contact-us/thank-you/ and kept the current WordPress header/footer by duplicating the existing thank-you page design under the Contact Us parent.
Added a Contact Us page-level script that patches the existing rendered form before submit so successful /sal/v1/contact-intake submissions redirect to the child thank-you URL. Added a thank-you page conversion script that emits sail_contact_form_submit plus the GA4 recommended generate_lead event through dataLayer/gtag, gated by session storage so direct thank-you page visits do not fire the event.
Confirmed the site already has Google tag/GTM surfaces present: GT-P82NMV7 and GTM-PRWV2N8. Set Rank Math robots for the thank-you page to nofollow, noindex through the Rank Math REST endpoint.
Public Contact Us and thank-you pages returned 200. Browser automation checked desktop and mobile DOM: the form was visible and success_redirect became https://aguiarinjurylawyers.com/contact-us/thank-you/. The thank-you page H1 is Thank you for contacting Sam Aguiar Injury Lawyers and the conversion script is present. A no-send honeypot REST test returned success with the thank-you redirect and did not create a fake lead. Live Salesforce read confirmed recent real Web_Form__c rows continue to contain paid attribution and GCLID data.
WordPress content backups were saved at /Users/samaguiar/Documents/Claude/wp-content-backups/contact-us-56-2026-05-17-174000-pre-thank-you-route.json, /Users/samaguiar/Documents/Claude/wp-content-backups/contact-us-thank-you-67008-2026-05-17-174000-pre-thank-you-route.json, and /Users/samaguiar/Documents/Claude/wp-content-backups/thank-you-root-2026-05-17-173151-pre-child-duplicate.json. MU plugin working files and backups are under /Users/samaguiar/Documents/Projects/admin/session_logs/contact-thank-you-conversion-2026-05-17/.
Google Ads API-side conversion-action creation was not completed. NotFair returned Auth required; direct Google Ads API returned deleted_client for the stored OAuth client. The website-side event is firing-ready, but the Ads-side conversion action should be created or confirmed after Google Ads OAuth is repaired or via authenticated Google Ads/GTM UI access.
Repair the Google Ads OAuth client/token path, then create or confirm a secondary Website Contact Form Submit conversion action tied to the thank-you event. Keep signed-retainer/offline Litify conversions as the primary bidding signal unless future data supports changing that.