Import from Umami

Already on Umami Cloud? Connect a site with your own API key and your existing history appears in Pulse right away, no tracking change needed. Importing is free on every plan, including the trial.

Connect a site#

Create an API key in Umami
In Umami Cloud open Settings, API keys and create a key.
Start the import in Pulse
When you add a site, choose Already on Umami? Import it, and paste the key. Pulse lists the websites that key can read.
Pick the website
Choose the one to connect, and optionally a second Umami website for your Mac or mobile app, so its events appear next to the site's. Confirm the time zone and finish.

What “import” means#

Pulse does not copy your Umami data. It reads it live, through Umami's API with your own key, whenever you open the dashboard (results are cached for about a minute). So:

Your history is there on day one and stays in Umami.
If you revoke the key, or delete the Umami website, that site goes empty in Pulse.
Only Umami Cloud (api.umami.is) is supported. Self-hosted Umami installs are not.
The key is stored encrypted and used only by Pulse's server. You can revoke it in Umami at any time.

What Pulse reads with your key#

The list of your websites (to let you pick one).
For the connected website: visitor, pageview, visit, bounce and time totals; pageview and event series; breakdowns by channel, referrer, campaign, page, entry, exit, country, region, city, browser, OS, device and event; sessions and their activity; the weekly heatmap; funnel, journey and retention reports; and the live feed.
For the optional app website: event counts and event properties.

Pulse only reads. It never writes to your Umami account.

What works for imported sites#

Feature	Imported from Umami	Tracked by the Pulse script
Analytics, charts, filters, compare	Yes	Yes
Channels, sources, pages, locations, devices	Yes (Umami's definitions)	Yes
Realtime	Yes	Yes
Likely to buy	Partly: pages, time on site and buy clicks; no return visits or channel	Yes, every signal
Funnels and journeys	Yes, computed by Umami	Yes, computed by Pulse
Visitors list, heatmap, retention	Yes, from Umami	Yes
Revenue totals and recent sales	Yes, from your payment provider	Yes
Revenue by source, page, device, campaign	Source and country only, and only if the checkout carried a source	Yes, all of them
Share links, notes, API, MCP, mentions	Yes	Yes
Tracking snippet	Nothing to install	One script tag

Revenue on an imported site#

Connect Stripe, Lemon Squeezy, Polar or Paddle to an imported site exactly as for any other. Sales, revenue totals and recent sales work immediately. Attribution needs to know which visit a sale came from, and an imported site has no Pulse events to join against. Two ways to get a source anyway:

Tag your checkout links yourself with a source value in custom data, for example ?checkout[custom][source]=threads on a Lemon Squeezy link, or metadata.source on Stripe, Polar and Paddle checkouts. Pulse uses it as the sale's source (and the payment's country as its location).
Add the Pulse script next to Umami (advanced). Both can run on the same pages. Read the site id from GET /api/v1/sites and use it as data-site; the domain must be a real domain that matches your pages. The script then tags checkout links with the visitor id, and Pulse can join sales to its own events. The dashboard's traffic numbers for that site keep coming from Umami.

Common issues#

“Umami didn’t accept that key”: Create a key in Umami Cloud, Settings, API keys. Keys from self-hosted Umami do not work, because Pulse talks to Umami Cloud only.
“That Umami key can’t read this website”: The key belongs to another Umami account or team than the website. Create the key under the account that owns the site.
A site shows zeros after it worked: Pulse could not reach Umami, or the key was revoked. Open Settings and check the site, or re-import with a new key.
I want the Pulse script on an imported site but Settings says nothing to install: For imported sites Pulse does not show a snippet. See the advanced option above, or add a new Pulse site.