GA4 and funnel visibility audit
Use this prompt to check whether page interactions, sign-up, subscription, checkout, purchase, and conversion paths are measurable through GA4 events and parameters.
Scope and best-fit use
Use this prompt when the primary goal is analytics, event tracking, and conversion-funnel visibility. It does not diagnose GA4 data collection without event code, DebugView evidence, network logs, or GA4 export data.
Inputs required
Provide the page or flow, current GA4 implementation, event list, GTM/gtag code, business goal, and conversion path. Do not infer GA4 collection status without implementation or reporting evidence.
Copy-ready prompt
Copy the prompt and replace the MATERIALS block with the current flow, event code, event list, business goal, and any GA4 evidence.
Review GA4 and conversion-funnel visibility.
TASK:
Audit the supplied page, flow, analytics code, event list, or implementation notes to determine whether important user actions and conversion paths are measurable in GA4.
REVIEW SCOPE:
Focus on:
- GA4 recommended event mapping
- missing user-action events
- content interaction visibility
- login and sign-up visibility
- subscription-intent visibility
- checkout-step visibility
- purchase or conversion outcome visibility
- event parameter completeness
- conversion/key-event candidates
- reporting blind spots caused by missing instrumentation
EVIDENCE RULES:
- Base findings only on supplied flow material, supplied code, supplied GA4/GTM evidence, or cited official documentation.
- Do not claim that GA4 is receiving data unless GA4 export data, DebugView evidence, network logs, or implementation code supports it.
- Prefer GA4 recommended events when they fit the action.
- Use custom events only when no recommended event fits the measured action.
- Do not invent event names, parameters, conversion status, revenue data, attribution data, or funnel performance.
- If evidence is missing, mark the item NOT VERIFIED.
BASELINE EVENT CHECKS:
General/content actions:
- search
- select_content
- share
- login
- sign_up
Checkout/sales actions:
- begin_checkout
- add_payment_info
- purchase
Lead/subscription-adjacent actions:
- generate_lead when the flow represents a lead
- custom event only when the action is product-specific and no GA4 recommended event fits
CHECKS:
- Which user actions are business-critical?
- Which actions are already tracked?
- Which actions are not tracked?
- Are GA4 recommended event names used where appropriate?
- Are required or useful parameters supplied?
- Is sign-up or login visible?
- Is subscription intent visible?
- Is checkout start visible?
- Is payment or purchase outcome visible?
- Are content interactions such as internal search, copy, download, share, or CTA selection visible when relevant?
- Which events should be considered conversion/key-event candidates?
OUTPUT:
A) Measurement objective
B) Current observed tracking
C) Missing events
D) Recommended GA4 event mapping
E) Parameter gaps
F) Funnel visibility gaps
G) Conversion/key-event candidates
H) Exact implementation notes
I) NOT VERIFIED / missing evidence
J) Confidence
MATERIALS:
"""
Replace this block with:
- page or flow description
- current GA4/GTM/gtag implementation
- event list
- CTA list
- subscription or checkout steps
- business goal
- DebugView, GA4 export, or network evidence, if available
- current concern or recent change
"""
Prompt setup
Use this as a runtime analytics review prompt
Paste the flow, event code, event list, and measurement objective into the prompt. Keep reusable no-fabrication and evidence rules in the instruction layer.
Related visibility workflows
Use the related workflow when the task moves from analytics measurement to search discoverability and SEO readiness.