Tell me what you are trying to build, fix, govern, prove, or launch, and I will point you to the public Folium page that fits. It uses public routes only, so do not send private data here.
Analytics boundary
Measure what helps the site improve without turning visitors into the product.
Folium should understand what pages help buyers, but the first public launch does not need invasive tracking. The analytics path should be privacy-friendly, legally reviewed, and focused on aggregate site improvement.
Measure pages, not people
Prefer privacy-friendly aggregate analytics that show which pages help buyers without building invasive visitor profiles.
No hidden intake
Do not collect form content, chat prompts, or tool inputs until production intake and retention rules are approved.
Review before enablement
Legal and privacy review should happen before adding analytics, CRM, email tracking, pixels, or remarketing.
Use the data to simplify
Analytics should answer which paths convert, where buyers drop off, and which review materials matter enough to keep improving.
Recommended first metrics
Track clarity, not surveillance.
Visits to the 90-second page.
Clicks from role routing into service paths.
Downloads of public review, trust, market, and risk PDFs.
Visits to case studies and flagship review walkthrough.
Contact-page visits after review or case-study pages.
Launch-control and trust-page review before inquiry.
Start here
Good analytics should make the public site clearer.
The goal is not to track everything. The goal is to learn which review paths help serious buyers move forward.
- 01 Scope
- 02 Build
- 03 Prove
- 04 Operate