local-business-conversion-analytics

What problem does it solve?

It solves unreliable paid-traffic conversion measurement for local business websites by wiring a consent-mode-aware analytics stack that preserves first-touch attribution and sends PPC-usable conversion signals even when cookies are blocked.

Core Features & Use Cases

• Four-layer analytics stack: Fires Plausible cookieless baseline, then consent-gated GA4/GTM and Meta Pixel signals using Consent Mode v2.
• First-touch attribution (30-day TTL): Captures click identifiers (gclid/fbclid/utm and related IDs) on landing and attaches stored attribution to later conversion events.
• Google Ads Enhanced Conversions: Hashes normalized email/phone (SHA-256) and pushes enhanced_conversion_data to the GTM dataLayer for better iOS/Safari matching.
• Meta event mapping + backup conversion: Maps events to Meta standard Lead and Contact, uses lead_thank_you_view as a resilient mirror, and routes the rest to trackCustom.
• Click delegation + smart event tracking: Auto-tags phone/mail/WhatsApp links and outbound clicks, while supporting a vocabulary of conversion and engagement events.
• Smart-bidding value hints: Converts property size selections into indicative GBP values to improve optimization weighting.

Use cases: new analytics installation, retrofitting Enhanced Conversions for existing Google Ads campaigns with weak iOS attribution, and improving ROAS reporting accuracy by preventing last-touch over-crediting.

Quick Start

Use the local-business-conversion-analytics skill to implement the site’s analytics + attribution layer by adding the provided client analytics helpers to your web/lib and wiring the root components so attribution is captured on page load and events are tracked from global click delegation.