RevenueUI documentation

Learn how to install RevenueUI, collect first-party activity, connect revenue, and read your analytics.

What RevenueUI does

RevenueUI connects first-party website activity with supported payment outcomes. It helps SaaS teams understand which sessions, pages, and acquisition sources are associated with trials and collected revenue.

Traffic and revenue are kept as separate data sources. Installing the tracking script starts traffic collection; connecting a payment provider adds subscription and payment data.

How the setup fits together

Add a website with its production domain and reporting timezone.
Install the generated tracking script in the website's <head>.
Connect a payment provider when you want revenue and subscription analytics.

Start with the quickstart for the complete setup path.

What you can analyze

Visitors, pageviews, bounce rate, and session duration.
Entry, exit, and popular pages.
Referrers, links, and campaign parameters.
Collected revenue, expected trial value, and revenue per visitor.
Paying visitor journeys when a verified visitor or session identifier is attached to a payment.

RevenueUI keeps currencies separate. Select a currency in analytics instead of assuming totals can be safely combined through an estimated exchange rate.

Before you begin

You need access to your website's <head> markup or tag-management setup. Revenue tracking also requires access to the supported payment provider account and, for visitor-level attribution, the backend code that creates the checkout or subscription.

Your organization remains responsible for its consent flow, privacy notice, and lawful basis for collection. See consent and cookies before choosing the embed mode.