PRD — Consent Mode v2 + Enhanced Conversions

Status: BACKLOG · Owner: growth/ads · Last updated: 2026-07-01

Source: Zak inbound on 2026-07-01: add Consent Mode v2 and enhanced conversions for compliant remarketing and better ad attribution.

1. Purpose

Make Fair Home Cash and any Soldi-owned seller acquisition pages ready for compliant Google Ads measurement in a housing-sensitive funnel. The first slice should add a consent-aware tracking foundation before more spend flows through search or retargeting.

This is a tracking and compliance backlog item only. Do not implement tags or send any ad events until the exact Google Ads account, consent banner policy, and legal copy are approved.

2. Scope

In scope:

  • Consent Mode v2 state model for ad_storage, ad_user_data, ad_personalization, and analytics_storage.
  • A page-level consent banner or existing consent surface integration for FHC pages.
  • Google tag loading only after the consent defaults and update path are defined.
  • Enhanced conversions design for lead-submit events using normalized, hashed first-party fields where permitted.
  • A documented fallback state where analytics can still record aggregate, non-personalized events when consent is denied.

Out of scope:

  • Auto-enabling remarketing audiences.
  • Uploading customer lists.
  • Changing lead form copy or consent language without review.
  • Adding non-Google pixels.

3. Effort Estimate

Small to medium: 1-2 focused engineering days after the Google Ads account IDs, conversion action IDs, and approved consent copy are available.

Risk is mostly compliance and data-handling review, not code volume.

4. Success Criteria

  • Consent defaults are set before any Google tag can send data.
  • A user can accept, reject, or leave consent unset, and the emitted tag state matches that choice.
  • Lead-submit conversion fires only with allowed consent state.
  • Enhanced conversion payload uses normalized hashed fields only, never raw PII in client-visible logs.
  • Browser QA proves no Google network calls happen before consent defaults initialize.
  • A Google Tag Assistant or equivalent debug session shows the conversion action receiving the expected test event.

5. Validation Plan

  • Unit/programmatic: test consent-state helper logic and event payload normalization.
  • Browser: verify first load, accept, reject, and revisit states.
  • Network: inspect Google requests for consent params and absence of raw email/phone values.
  • Docs: record the exact account/conversion IDs and screenshot the debug proof once configured.

6. Recommendation

needs_legal_or_payments_review