以下の詳しいガイドと説明用の事例は英語です。例に含まれる業務データは架空のものです。
Where Google Analytics 4 fits
A measurement plan for how visitors reach enquiries or purchases.
When to choose another approach
Traffic is not qualified demand. Consent choices, blockers and implementation gaps limit coverage.
Worked example and evidence
Fictional report: 120 consented service-page views, 12 form starts and 4 confirmed submissions. Separately, the owner marks 2 enquiries qualified in business records. These invented counts illustrate distinct measures.
What you need to supply
Property access, event definitions, consent policy, confirmation source and personal-data exclusions.
What acceptance should demonstrate
Each event has a definition, trigger and owner. Verify no duplicate conversions, no form contents in events and the chosen consent behaviour.
Running costs and responsibilities
Assign event maintenance, access reviews and interpretation. Reconcile business outcomes separately from analytics totals.
Technical scope to confirm
Consent mode changes tag behaviour according to consent signals. It does not decide your consent obligations.
A proposal should identify the systems and data, direction of sync, access feasibility, failure handling, named owners and included deliverables. Listing this technology does not imply a prebuilt connector, vendor partnership or included feature.
What can we measure when visitors decline analytics?
Follow the agreed consent design. Basic blocking does not load GA4. Necessary operational records may confirm submitted enquiries under the applicable policy, without complete visitor attribution.