new-site/site/public/js
justin 60d5d3b9d8 analytics: attribute price-test arm per click + A/B/C scoreboard
So we can see whether a discount helps the CTA (clicks) AND the sale (paid
orders), per arm:

1. pw-analytics.js: include the ?code= (the price-test arm) on the campaign-click
   Umami event, and fire it when EITHER a utm OR a code is present (coupon links
   often carry code with no utm, so those human clicks were being dropped). Also
   strip a stray @TrackLink suffix Listmonk glues onto the last query value.

2. coupon_ab_scoreboard.py: one report combining HUMAN clicks (Umami, already
   bot-filtered) and PAID conversions (compliance_orders) per arm. Discount arms
   map by code->pct (campaign-daily:<date>:<pct> marker); the no-code control arm
   is recovered by re-hashing customer_email the same way the builder bucketed it.
   Prints clicks, paid orders, revenue, and click->order per arm.
2026-06-30 16:39:26 -05:00
..
pw-analytics.js analytics: attribute price-test arm per click + A/B/C scoreboard 2026-06-30 16:39:26 -05:00
pw-bot-filter.js analytics: filter email-scanner / headless traffic out of Umami stats 2026-06-18 02:02:34 -05:00
pw-cookie-consent.js trust/security: DMARC p=reject; MTA-STS cert+HTTPS policy live; cookie consent banner (CSP-safe); /accessibility page; footer legal links (Security/Accessibility) on all pages; scope TrustedSite to /order payment pages only 2026-06-06 21:01:36 -05:00
pw-crtc-collapse.css crtc page: add 5-min-read TL;DR + collapsible deep-detail sections (non-destructive JS/CSS enhancement) 2026-06-20 01:08:41 -05:00
pw-crtc-collapse.js Add Ontario alongside BC on CRTC page 2026-06-20 06:40:18 -05:00