Skip to main content

Overview

Project integrations live under Settings → Integrations. Only project owners and admins can connect providers or run imports. Google Search Console and Google Analytics use separate OAuth consent screens (different scopes and redirect URIs), so connecting one does not grant the other. Plausible history uses a ZIP upload, and DataFast, Umami, Fathom, and Matomo history each use an API key or token from that tool — no OAuth for any of them. Payment providers (Polar, Stripe, Shopify, RevenueCat, and others) are documented under Revenue integrations.

Google Search Console

Connect Search Console to see which Google searches bring visitors to your site — clicks, impressions, CTR, and average position — on the analytics Keywords card. Pick the property that matches your project domain after connecting.

Google Analytics import

Connect a GA4 property to import roughly the last 90 days of screenPageViews and activeUsers into OpenRevenue as synthetic pageview rows. That fills your dashboard charts with historical context while the live tracker collects new traffic.
  1. Open Settings → Integrations and connect Google Analytics.
  2. Select the GA4 property that matches your site.
  3. Click Import last 90 days. Re-import replaces the previous GA import for that project.
Imports do not count toward your plan’s event usage. Owners and admins can run up to three imports per hour.

Plausible ZIP import

Upload a Plausible full-site export ZIP to import daily pageviews and visitors (and optional page breakdown) as synthetic OpenRevenue pageviews. Files upload to private object storage, then you preview before confirming.
  1. In Plausible, open Settings → Imports & Exports and export site data.
  2. In OpenRevenue, open Settings → Integrations → Plausible, choose the ZIP (uploads privately), then click Preview ZIP.
  3. Confirm with Import history. Re-import replaces the previous Plausible import. Use Remove Plausible import to roll back.
The ZIP must include imported_visitors_*.csv (date, visitors, pageviews). imported_pages_*.csv is optional and improves path mix. Max file size is 25 MB. Uploads are private (not publicly readable), scoped to your account and project, and deleted after a successful import. Imports do not count toward event usage.

DataFast import

Switching from DataFast? Import up to three years of history straight from DataFast’s API. OpenRevenue reads your daily visitors, sessions, and pageviews, plus pages, sources, countries, devices, browsers, operating systems, goals, and payments, and rebuilds them as synthetic OpenRevenue events so past date ranges show up in your dashboard.
  1. In DataFast, open Website settings → API and create a website API key. It starts with df_. Account tokens (dft_) are not accepted.
  2. In OpenRevenue, open Settings → Integrations → DataFast, paste the key, and pick a history range (3 months to 3 years).
  3. Click Preview import to check the DataFast site and totals, then confirm with Import history. Longer ranges can take a minute or two — keep the tab open.
  4. Re-import replaces the previous DataFast import. Use Remove DataFast import to roll back.
Your API key is sent to DataFast for that one import and is never stored or logged by OpenRevenue — paste it again to re-import, and revoke it in DataFast whenever you like. Imports do not count toward event usage. Owners and admins can run up to three imports per hour.

What is imported

  • Daily visitors, sessions, and pageviews — taken from DataFast’s daily totals, by UTC day.
  • Pages, sources, countries, devices, browsers, and operating systems — DataFast reports these per date range, not per day, so OpenRevenue samples the range in up to six slices and applies each slice’s mix to its days.
  • Goals — imported as custom events with the same goal name, spread across each slice in proportion to daily visitors.
  • Payments — each day’s revenue is imported as transaction events named DataFast payment in your DataFast currency, split evenly across that day’s payment count.

What is not imported

  • Individual visitors, visitor profiles, and real session journeys (DataFast’s API is aggregate-only here).
  • UTM campaigns, ref/via parameters, regions, cities, and hostnames.
  • Goal parameters, funnels, bounce rate, session duration, and new vs. returning splits.
  • Individual payment amounts, customers, refunds, and revenue attribution to a specific page or source. For accurate revenue, connect your payment provider under Revenue integrations.
  • Today’s partial day, pages beyond the top 1,000 per slice, and days DataFast reports with no pageviews.
An import can create at most 500,000 events (pageviews, goal completions, and payments combined). If your site is larger, choose a shorter range. Named sources that OpenRevenue cannot match to a domain are imported as direct traffic and listed after the import.

Umami import

Switching from Umami? Import up to three years of history straight from Umami’s API, from Umami Cloud or your own self-hosted instance. OpenRevenue reads your daily visitors, visits, and pageviews, plus pages, sources, countries, devices, browsers, operating systems, and custom events, and rebuilds them as synthetic OpenRevenue events so past date ranges show up in your dashboard.
  1. In Umami, open Settings → API keys and create a key.
  2. In OpenRevenue, open Settings → Integrations → Umami and paste the key. If you self-host Umami, also enter its address (for example https://analytics.example.com); leave it empty for Umami Cloud.
  3. Pick a history range (3 months to 3 years) and click Preview import. If the key can read several websites, OpenRevenue selects the one that matches your project domain, or asks you to choose.
  4. Check the totals, then confirm with Import history. Longer ranges can take a minute or two — keep the tab open.
  5. Re-import replaces the previous Umami import. Use Remove Umami import to roll back.
Your API key is sent to Umami for that one import and is never stored or logged by OpenRevenue — paste it again to re-import, and delete it in Umami whenever you like. OpenRevenue never asks for your Umami password. Imports do not count toward event usage. Owners and admins can run up to three imports per hour.

Self-hosted Umami

A self-hosted instance must be reachable from the internet over HTTPS on the default port, with a public hostname. Instances that are only reachable on a private network, by IP address, or over plain HTTP cannot be imported. Your Umami version must support API keys (Settings → API keys).

What is imported

  • Daily visitors and pageviews — taken from Umami’s daily series, by UTC day.
  • Visits (sessions) — Umami reports these per date range, so each slice’s visits are spread across its days in proportion to daily visitors.
  • Pages, sources, countries, devices, browsers, and operating systems — Umami reports these per date range, not per day, so OpenRevenue samples the range in up to six slices and applies each slice’s mix to its days.
  • Custom events — imported as custom events with the same name, spread across each slice in proportion to daily visitors.

What is not imported

  • Individual visitors, sessions, and real session journeys.
  • Event data (properties), UTM campaigns, regions, cities, languages, screen sizes, and hostnames.
  • Revenue, funnels, goals, bounce rate, and visit duration.
  • Today’s partial day, values beyond the top 500 per slice, and days Umami reports with no pageviews.
An import can create at most 500,000 events (pageviews and custom events combined). If your site is larger, choose a shorter range.

Fathom import

Switching from Fathom Analytics? Import up to three years of history straight from Fathom’s API. OpenRevenue reads your daily visitors, visits, and pageviews, plus pages, sources, countries, devices, browsers, operating systems, and events, and rebuilds them as synthetic OpenRevenue events.
  1. In Fathom, open Settings → API and create a token that can read your site.
  2. In OpenRevenue, open Settings → Integrations → Fathom and paste the token.
  3. Pick a history range (3 months to 3 years) and click Preview import. If the token can read several sites, OpenRevenue selects the one whose name matches your project domain, or asks you to choose.
  4. Check the totals, then confirm with Import history. Re-import replaces the previous Fathom import. Use Remove Fathom import to roll back.
Your token is sent to Fathom for that one import and is never stored or logged by OpenRevenue. Fathom counts each API request toward your monthly pageviews; an import makes at most about 100 requests.
  • Daily visitors, visits, and pageviews — exact, from Fathom’s daily totals (UTC days).
  • Pages, sources, countries, devices, browsers, and operating systems — sampled in up to six slices of the range.
  • Events — up to 40 events, with exact daily completion counts summed per slice.
  • Not imported — event values (revenue), UTM campaigns, regions and cities, bounce rate, and visit duration.

Matomo import

Switching from Matomo? Import up to three years of history from your own Matomo instance or Matomo Cloud through Matomo’s Reporting API.
  1. In Matomo, open Personal → Security → Auth tokens and create a token for a user with view access to the website.
  2. In OpenRevenue, open Settings → Integrations → Matomo, enter your Matomo address (for example https://matomo.example.com or https://your-name.matomo.cloud), and paste the token.
  3. Pick a history range and click Preview import. If the token can read several websites, OpenRevenue selects the one whose URL matches your project domain, or asks you to choose.
  4. Check the totals, then confirm with Import history. Re-import replaces the previous Matomo import. Use Remove Matomo import to roll back.
Your token is sent to your Matomo instance in the request body (never in a URL) for that one import and is never stored or logged by OpenRevenue. Your Matomo instance must be reachable from the internet over HTTPS on the default port, with a public hostname.
  • Daily visitors, visits, and pageviews — exact, from Matomo’s daily reports, in your Matomo website’s timezone.
  • Pages, sources, countries, devices, browsers, and operating systems — read from Matomo’s monthly reports, so each calendar month’s mix is applied to its days. Sources include direct entries, websites, search engines, and social networks.
  • Events — event actions, as custom events with the same name (requires Matomo’s Events plugin).
  • Not imported — campaigns, goals and ecommerce, site search, regions and cities, bounce rate, and visit duration.

Import limitations

Imported history is approximate. Visitor counts come from the source tool’s visitor/active-user totals (not true OpenRevenue visitor IDs), and bounce rate and session journeys will not match source fidelity. Device, geo, and referrer dimensions are empty on Google Analytics and Plausible imports; DataFast, Umami, Fathom, and Matomo imports fill them from sampled breakdowns, so they are right in aggregate but not tied to real visitors. Use imports for trend context, then rely on the live tracker for accurate ongoing analytics.