Require opt-in consent for website analytics and enquiry attribution

[Kailramiya]

Summary

The public site loaded GA and TruConversion before visitors could choose. This repair keeps optional analytics off until explicit opt-in and adds accessible Allow analytics, Decline analytics and persistent Privacy choices controls. Revocation blocks collection and clears GA cookies; declined enquiries still submit without attribution or lead events. TruConversion is disabled pending verified input masking and revocation. Success messages now say submitted rather than implying inbox delivery.

Issue Or Context

• Area changed: marketing web consent/measurement and its operational handoff.
• Reconciled against main 0a05067 and the live integration before edits. Fresh GA setup check confirms once-per-event, no default value and all three EVENT dimensions; no GA registrations/scopes were changed.
• GA history pageviews stay ON and manual pageviews OFF. Existing Monday private reporting and staged IVR work are preserved.

Verification

• 68 web tests, web type check, lint and production build pass.
• Scoped SEO claims gate passes for 192 public content files. Broad scan still flags existing unreviewed legacy material outside this repair.
• Production-build browser QA: default/declined zero tracking; keyboard allow/decline/reopen and focus return; persisted choice; blocked storage defaults off; revocation across tabs; mobile layout.
• Intercepted form QA: invalid zero requests; failure zero leads with fields retained; retry receipt stable; declined success zero leads/context; consented success one sanitized lead. No GA ingestion or email delivery is claimed.
• Initial opt-in, reload, SPA, back and forward each emit one automatic pageview with matching route/title after dispatch settles. Revocation then navigation emits zero collection requests.
• Exact Coolify app IDs and nonsecret build/runtime settings are documented in docs/marketing/seo/follow-up-2026-09-21.md.
• No dependency, CI, shared server, auth, billing or database changes. Local checks are scoped to the changed web app; repository CI remains required.

Launch And Positioning Guardrails

No new product, competitor or customer claims. Provider acceptance remains distinct from inbox delivery and business qualification. No paid DataForSEO calls, secret values, private analytics records or reporting schedule changes.

Screenshots Or Recordings

Real 375px screenshot from the local production build:

Maintainer Review Notes

One bounded consent/attribution repair. Production deployment through existing authorized Coolify access and a safely classified real QA receipt/inbox match remain gates. Do not broaden token scopes or change pageview ownership. No new environment variable is needed for consent.

Merged revision and deployment outcome — September 21, 2026

Merged at 06:12 UTC as c5ed952ab2da5595d4c51c088b5e0dc52d4cd82b. Main CI 35567462027 and security 35567462041 both passed.

The existing deployment workflow 35567686623 passed the current-main and required-check gates, then stopped at 06:15:53 UTC on its first Coolify GET: HTTP 403 (API permission restriction). No hosting environment mutation or deployment request occurred. Inputs were contact attribution preserve and manual pageviews disable. Token scopes were not broadened.

Supervisor handoff: authenticated Coolify Root Team, marketing app 76d9ooqtvm1hl9tbzmza3few (quickvoice.co / www.quickvoice.co), deploy the merged revision above. Keep NEXT_PUBLIC_GA_MANUAL_PAGEVIEWS=false (build/runtime) and GA history measurement ON. Consent requires no new setting. Enable runtime CONTACT_ATTRIBUTION_ENABLED=true only after verifying healthy compatible API app udefnayjdhyb2ketfxrbvwdq and matching existing webhook configuration. Preserve the existing GA ID and console URL. The full handoff is in the September 21 record.

The repair is merged and locally verified, not verified live. Live homepage, contact, existing IVR, scheduling and multilingual routes returned HTTP 200; the sitemap still contains 101 URLs. The contact page still has the legacy tracker and no consent controls. A safely classified real enquiry with matched receipt and recipient inbox remains blocked by deployment/receiver verification. Intercepted QA is not counted as leads or inbox delivery. No private report schedule or OAuth grant changed; IVR content remains staged; zero paid DataForSEO calls.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.