- Fixed all 'undefined NaN, NaN' dates in metadata divs across all 22 posts - Removed draft instruction from qr-code-scan-statistics-2026 - Removed duplicate 'Trackable / dynamic QR code' section from trackable-qr-codes - All posts now have proper 'Last updated' dates showing January 26, 2026
1.8 KiB
1.8 KiB
QRMaster Tracking Spec
Why this exists
QRMaster growth pages should not be judged by traffic alone. Each page must support a measurable movement into signup or first product value.
Core event set
Required marketing events:
landing_page_viewedcta_clickedsignup_startedsignup_completedlogin_startedlogin_completedqr_created_firsttool_qr_generated(optional, for free tools)
Required properties
Use these whenever possible:
landing_page_slugpage_typeclusteruse_casecta_labelcta_locationdestinationutm_sourceutm_mediumutm_campaignutm_content
Page-type model
Recommended page_type values:
homepagecommercialuse_case_hubuse_caseblog_postlearn_hubpillartoolauth
Funnel interpretation
The minimum useful path is:
landing_page_viewed -> cta_clicked -> signup_started -> signup_completed -> qr_created_first
Use this to answer:
- which pages bring qualified visitors
- which pages push users into signup
- which signups actually reach first QR creation
Known repo findings from prior QRMaster review
- PostHog is the real custom-event system.
- GA is wired mainly for pageviews.
- Cookie consent is client-side via
localStorage['cookieConsent']. - CTA tracking was previously inconsistent.
- Prior analysis suggested likely duplicate pageviews from repeated PostHog/Facebook pixel mounts.
If you implement tracking later in the QRMaster repo, verify those points again before shipping changes.
Decision rules
- do not create new events that do not support a decision
- do not track only clicks without tying them to page context
- do not judge SEO pages only by sessions; inspect signup and activation movement too