Fini funnel blueprint

How usefini.com's ~95 pages, one conversion path, and every tracked click fit together — drawn, not just listed.

usefini.com·GA4 + GTM·7 Sep 2026 crawl
Access

GA isn't connected to Fini yet — the live analytics connection only reaches Nbyula's own properties. Add ai.team@navigus.in as Editor on Fini's GA4 property (or reconnect the right Google account) to unblock the build below. Framer write access already works.

01 — Mechanism

How a click becomes a report

usefini.com Framer site Tag Manager triggers + tags GA4 property event stream Funnel report exploration + key events data-track click gtag() event streams in
Every tracked element in this plan gets a stable data-track attribute in Framer (not a CSS class — those hashes change on every republish). GTM listens for it, fires the matching GA4 tag, and GA4 streams the event live.
02 — What we're tracking

The six-stage funnel

Acquisition Engagement Consideration Intent Conversion Post-conv.
page_view — first landing, any channel
scroll, file_download, outbound_click — blog / guides / glossary / resource library
page_view +competitor_slug/industry_slug/customer_slug — compare, industries, case studies, pricing view
cta_click, pricing_toggle — any "Book a demo" / "Get Started" / "Contact us"
generate_lead — the one form on /company/contact, the primary key event
outbound_click to docs./security. — a converted lead exploring further
Structural fact

Fini has exactly one commercial path today — no signup, no Calendly, no pricing calculator. Every CTA site-wide feeds the same funnel into the same form. That's why one generate_lead event can serve as the single primary key event.

03 — Where it's set up

Every page, grouped by template

low-intent entry engagement consideration intent conversion outside the funnel
Homepage
1
/
Product
7
platform, atlas, scout…
Pricing
1
/pricing
Industries
5
finance, health, e-com…
Case studies
7
hub + 6 stories
Comparison
6 +10 draft
hub + 5 live /compare
Blog
19
hub + ~18 posts
Guides
13
hub + 12 guides
Glossary
30
hub + ~29 terms
Contact
1
/company/contact — the form
About / community
4
about, podcast x2, hall-of-fame
Resource library
5
hub + 4 whitepapers
Security / legal
5 +2 subdomains
ToS, DPA, privacy…
~95 URLs, 13 templates. Instrumentation attaches to the template, so a new blog post or glossary term inherits tracking with zero extra config. Block color = which funnel stage that template feeds.
04 — UX decisions

Exactly what gets a tag, and what doesn't

1 2 3 4 footer nav + legal links — not tracked
Homepage — 1 nav CTA · 2 hero CTA · 3 case-study card CTA · 4 footer marketplace badge (outbound). Plain footer links and legal text: not tracked.
5 Growth Scale Enterprise 6 FAQ accordion 7
Pricing — 5 billing toggle · 6 tier "Get Started" (label carries which tier) · 7 FAQ accordion is deliberately not instrumented in v1 — low signal value, revisit if the page underperforms.
05 — Coverage

Which event fires where

Template page_view+scrollcta_clickpricing_togglefile_downloadoutbound_clickform_startgenerate_leademail_click
Homepage
Product
Pricing
Industries
Case studies
Comparison
Blog / Guides
Glossary
Resource library
Contact
Community
Security / legal
page_view+ means page_view enriched with template/slug parameters, not a separate event (see §02). Filled dot = fires; the green dot on Contact/generate_lead is the one primary key event.
Verify before build

Four unknowns a live browser pass will settle: the real /company/contact submit behavior (native form vs. embed, and its success signal), whether the 4 whitepapers are email-gated, whether docs./security. subdomains run on Framer at all, and whether any page embeds video (none found via static crawl, but JS-rendered players wouldn't show).