Plausible integration
Plausible Analytics with Stripe revenue by page
Plausible shows visitors without cookies. Joinsight adds the missing column: how much revenue those pages and sources bring.
No card required. The trial clock starts when your first revenue source connects.
What Joinsight answers with Plausible
- Traffic and revenue per page in one table
- Which sources send visitors who pay, not just visitors
What it reads
- Visitors and pageviews by page and source through the Stats API
- Self-hosted Plausible instances as well as plausible.io
Good to know
- Plausible data is aggregate, so attribution still comes from the snippet and identify().
Setup
- Create a Stats API key in Plausible and copy your site ID.
- Paste both in Joinsight, with your host if you self-host.
Questions
Does Joinsight replace Plausible?
No. Joinsight's snippet records one first touch per session for attribution. Plausible stays your traffic analytics.
Works well with
- Stripe
Connect Stripe with a read-only restricted key and see which landing pages, Search Console queries and channels brought your paying customers, next to accurate MRR and movements.
- RevenueCat
Connect RevenueCat to see mobile and web MRR as one number, deduplicated against Stripe, and tie App Store and Google Play revenue to the content and campaigns that drove it.
- Google Search Console
Join Google Search Console with Stripe and RevenueCat to see revenue per landing page and modeled revenue per query, plus keyword opportunities ranked by what they could earn.
See what makes you money.
Connect Stripe or RevenueCat and Search Console, and you see combined MRR and 16 months of search history on day one. Page and keyword revenue follow as the snippet collects first touches.
No card required. The trial clock starts when your first revenue source connects.