New · Feature Engagement

Ship the feature.
Watch it get used.

Your analytics knows what happened on your site. FishLadder knows what shipped. Feature Engagement is the join: connect the analytics you already run, map a roadmap project to its pages, and see real usage rise right where the release lives.

Start Free Trial → How it works
Works with Google Analytics 4 and Cloudflare Web Analytics
Reports v2
GA4 · synced nightly
Daily page views — /app/reports*
⚑ Released Jun 12
10 weeks agotoday

The before-and-after of shipping, shown on the project itself. Board cards get a 30-day sparkline.

Map once.
Nightly after that.

There's nothing to instrument and nothing to maintain. You tell FishLadder which pages belong to which project; it pulls the numbers from your provider while you sleep.

Engagement is page-based. That makes it a natural fit for pages, sections, and docs (a pricing page, a reports area, a help center). Features that live inside a single view of a single-page app won't show up as their own page views.

Full details in the docs: Feature Engagement.

1
Connect your analytics provider
Google Analytics 4 or Cloudflare Web Analytics, from Settings → Integrations. Read-only access, verified before anything is stored.
2
Map a project to its paths
In the project drawer: exact paths like /pricing, or a prefix like /app/reports* to cover a whole section.
3
Charts fill in overnight
Daily views and visitors for the mapped paths, with the target or release date marked. About 90 days are backfilled on connect, so nothing starts empty, and recent days are re-fetched each night to pick up late corrections from the provider.
Providers

Bring the analytics you already run.

Feature Engagement reads from the reporting API of the analytics you've already deployed, so there's no new tracker to adopt.

Google Analytics 4
sign in and pick
Genuinely one click of consent.
Sign in with Google from the Web Analytics card
Approve read-only access to Analytics
Pick your property from a dropdown
No GCP console. No service accounts to create, no IDs to type. (A service-account option exists for locked-down Google setups.)
Cloudflare Web Analytics
one API token
Connect with a single API token.
Open the pre-filled token link (the one permission it needs, Account Analytics: Read, comes pre-selected)
Paste the token
Pick your account and site from dropdowns
Cloudflare reports visits rather than unique visitors, and FishLadder labels the numbers accordingly.

Built as a provider layer, with more on the way. Run something else? Tell us which; it helps us pick what's next.

Privacy

The join, without
a second tracker.

FishLadder never collects analytics itself. There is no script to put on your site, no beacon, and no visitor data changing hands. It reads only the daily aggregates your provider already computed.

nothing on your site
No JS snippet, no pixel, no cookie. Your visitors never touch FishLadder, so there's nothing new to disclose in your privacy policy.
read-only, nightly
Data comes from your provider's reporting API with read-only credentials, once a night. FishLadder can't change anything in your analytics.
mapped paths only
Only the paths you've mapped to a project are requested, never your whole site.
daily totals only
What's stored is small daily totals per page: views and visitors. No sessions, no IPs, no identities, and no PII at all.

Credentials are verified against the provider before they're saved, stored encrypted, and never displayed again, to you or anyone else.

The bigger picture

Three answers to “was this worth building?”

The feedback widget already records which page each submission came from. Map that page to a project, and the three lines meet in one place.

What shipped?
Reports v2Shipped
Released Jun 12 · /app/reports*

The roadmap project: what was built, when it went out, and which pages it lives on.

How much is it used?
Daily page viewsGA4

Real usage from your analytics, charted on the project with the release date marked.

What did people say?
Feedback/app/reports

The new reports load so much faster — can we get CSV export too?

Widget submissions arrive tagged with the page they were sent from, and those are the same pages you mapped.

Nobody else can make this join. Analytics tools don't know what shipped, and project tools never see usage. FishLadder holds both ends, so you can release something and actually find out what it did.

Your next release
comes with a chart.

14-day free trial · No credit card required · ~90 days of history backfilled on connect

Start Free Trial → Read the docs