Know which posts bring visits, with your Umami history

What upTake reads from Umami

upTake reads the number of visits per day and per source from your Umami site, twelve months back. This history is kept apart from the visits measured by upTake's own script: it is drawn as a dashed line on your chart, it is not counted in your numbers, and it is never used to attribute a payment.

How to connect Umami

You need an upTake project first; creating one takes about four minutes. Click Connect on the Integrations page; a small window asks for what Umami needs. Umami address: For Umami Cloud, enter api.umami.is. For your own server, enter its address, like stats.yourapp.com. API key: In Umami Cloud, open Settings → API keys and create a key. On your own server, use an API token. Website ID: In Umami, open Settings → Websites → Edit: the website ID is shown at the top. upTake checks it with Umami before saving it.

What you see afterwards

Your chart starts months before you installed upTake, so a new post can be compared with what was normal for your site, instead of with an empty chart.

What upTake never reads

No visitor-level data is imported: only totals per day and per source.

Whatever you connect, the IP addresses of your visitors are never stored, and the keys and accesses you give are stored encrypted and never sent back to your browser.

Good to know

You can disconnect Umami at any time from the Integrations page: upTake stops at once, and what was already imported stays in your project until you delete it. Your data is hosted in the European Union, and you can export all of it, or delete your account, from Settings.

Why connect it

Most analytics tools stop at where your visitors came from. upTake goes one step further: it ties each visit and each payment back to the thing you did, whether a post, a link you shared or a release you shipped, and tells you every week what to do more of. Umami is one more piece of that picture.