clicks.page icon

clicks.page

clicks.page is cookieless website analytics with source, conversion, and revenue attribution for founders and indie hackers. It supports realtime reporting, payment-provider connections, a REST API, and an MCP server for AI-assisted setup and analysis.

clicks.page

Website analytics with revenue attribution

clicks.page is a cookieless website analytics product for tracking visitors, acquisition sources, conversions, and revenue. It combines standard traffic reporting with payment attribution, allowing a site owner to see which sources brought visitors and which sources generated paying customers.

The product is designed to work with AI-assisted setup and analysis. An agent can create or connect an account, add a site, install the tracking script, and connect to the MCP server or REST API. For implementation, the tracker supports custom events, while the reporting API provides realtime data, time series, breakdowns, funnels, goals, and conversion metrics.

Core features

Revenue attribution

Shows visitors, sources, revenue, revenue per visitor, and renewals credited to the customer's first source. Revenue can be connected to supported payment providers through read-only keys and webhooks.

Realtime traffic

Provides a live visitor count, world map, and activity feed so teams can monitor traffic as it arrives rather than waiting for a reporting period to finish.

Detailed reporting

Offers summary statistics, time series, top pages and sources, and breakdowns by source, referrer, UTM fields, location, device, browser, operating system, entry, exit, page, and event.

Events, funnels, and goals

The tracker supports custom events through clicks.track(name, props) or data-clicks-event attributes. The API also supports funnels, goals, conversion reporting, and server-side revenue events.

Privacy-focused traffic quality

Filters bots, headless browsers, datacenter traffic, and referrer spam. It also supports cookieless measurement, stores no raw IP addresses, and honors Global Privacy Control and Do Not Track.

Agent and developer access

Includes a REST API, an MCP server, and an agent-oriented signup and installation flow. AI coding agents can install the script, check installation status, and answer questions from connected analytics data.

Practical use cases

  • Measure marketing channel revenue

    Connect acquisition sources to payment data to compare which channels produce revenue, revenue per visitor, and renewals rather than evaluating campaigns only by traffic volume.

  • Monitor launches in real time

    Use the realtime count, world map, and activity feed to watch a launch, campaign, or product announcement as visitors arrive and identify incoming sources while activity is happening.

  • Analyze conversion paths

    Add signup or other custom events, define a conversion goal, and use funnels to examine the path from a page visit to an action such as signup or payment.

  • Run analytics through an AI agent

    Install the script and connect the MCP server so an AI coding agent can set up tracking, verify deployment, and answer questions about sources, visitors, conversions, and revenue.

  • Diagnose traffic quality

    Use source, UTM, country, city, device, browser, page, and event breakdowns to investigate traffic quality and distinguish useful visitors from bot, datacenter, or referrer-spam activity.

Pros and Cons

Pros

  • Connects traffic sources with revenue and paying visitors instead of reporting visits alone.
  • Provides agent-accessible setup and querying through an MCP server, REST API, and documented installation workflow.
  • Supports multiple payment providers and can import past payments as well as receive webhook updates.
  • Uses a cookieless tracker that does not store raw IP addresses and filters several categories of low-quality traffic.
  • Offers realtime monitoring, event tracking, funnels, goals, conversion reporting, and granular traffic breakdowns.

Cons

  • The documented installation requires adding a script to every page and, for server-created checkouts, passing the clicks.page session ID into payment metadata for reliable visit attribution.
  • Revenue attribution depends on connecting a supported payment provider or implementing the relevant webhook, checkout, or server-side flow.
  • The Free forever option includes a visible clicks.page badge; removing the badge requires the documented Pro trial or subscription path.

FAQ

How is clicks.page installed?

The setup guide describes an agent-assisted workflow: sign up through the agent API, add the site, choose Free forever or Pro, place the tracking script in the document head of every page, deploy, and verify installation through the site status endpoint. An MCP connection can then be added for analytics questions.

Does clicks.page use cookies or store IP addresses?

Yes. The documented tracker does not use cookies or localStorage, does not store raw IP addresses, and honors Global Privacy Control and Do Not Track. The site presents this as a cookieless, privacy-friendly analytics approach.

Which payment providers can be connected for revenue attribution?

Revenue connections are documented for Stripe, Paddle, Polar, Lemon Squeezy, Dodo Payments, and Creem. A read-only provider key can import past payments and periodic updates, while webhooks can provide faster payment notifications. Both methods can be used together, with provider IDs used to avoid counting a payment twice.

Can analytics be accessed programmatically or through an AI agent?

The product provides a REST API at https://clicks.page/api/v1 and an MCP server at https://clicks.page/mcp. The API covers site statistics, breakdowns, time series, realtime data, funnels, goals, conversions, revenue, and installation status; the MCP server is intended for querying analytics through an AI agent.

What plans are documented?

The documented Free forever option supports up to 10,000 pageviews per month and includes the product badge, with no card required. The Pro option has a seven-day free trial, removes the badge, requires a card, and is offered in 10k, 100k, and 1M monthly pageview sizes with monthly or yearly billing.

Quick Facts

Category
Web analytics and revenue attribution
Primary users
Founders and indie hackers
Tracking model
Cookieless; no localStorage or raw IP storage
Developer access
REST API and MCP server
Payment integrations
Stripe, Paddle, Polar, Lemon Squeezy, Dodo Payments, and Creem
Documented plans
Free forever with badge; Pro with a 7-day free trial