Analytics Tracking

Start with the business action, then define its event name, trigger, parameters, metric scope, owner and verification. A CTA click measures intent; it is not automatically a signup or purchase. For article CTAs, record the content URL and placement, then compare with separately verified outcomes before claiming content ROI.

Confirm property, stream, measurement ID, tag coverage and consent behavior across relevant domains. Check enhanced measurement (page views, scrolls, outbound clicks, site search, downloads and eligible video engagement) against manual events to avoid duplicates. Distinguish automatic, enhanced, recommended and custom events. Prefer GA4 recommended events such as sign_up, login, purchase, search, view_item and add_to_cart when the actual action matches. Custom names should be consistent, readable and checked against current event limits. Define parameter types and allowed values; avoid collecting everything merely because it can be collected.

Use a stable first-party User-ID only after identification, without direct personal identifiers. Clear it on logout. Verify reporting identity and distinguish users, sessions, event counts and backend accounts. Earlier data is not retroactively reprocessed. Follow Google's User-ID guidance.

Document which events are GA4 key events, their values and currency, and how their totals reconcile to production outcomes. A GA4 key-event count is not a unique paid-user count. For attribution, preserve source/medium and campaign scope; use traffic-analysis for channel interpretation. A warehouse, ad pixels or server-side events may help a mature measurement stack, but they are not prerequisites for every small site; define the minimum viable setup from the decision being made.

Verify the browser request, tag preview where used, Realtime, DebugView and a settled report. Test duplicate actions, login/logout, consent, mobile and cross-domain paths as applicable. Deliver an event specification, implementation notes, test evidence and unresolved data-quality limits.

Open Analytics' current conversions contract stores event counts. It does not yet implement a conversion funnel or verified revenue attribution. Do not describe those as computed outcomes.