Know which GitHub releases bring customers

What upTake reads from GitHub

On the repositories you choose, upTake reads your GitHub releases, tags and merged pull requests: their titles and their notes. It sorts each change into a feature, an improvement, a fix or an internal change, and it writes announcement drafts for the first two, so that what you ship does not stay unannounced.

How to connect GitHub

You need an upTake project first; creating one takes about four minutes. Click Connect on the Integrations page: a GitHub window opens, you sign in there and approve the access. upTake never sees your GitHub password.

What you see afterwards

Every release shows up as a marker on your traffic chart, so you can see what shipping did to your visits and your revenue. The Releases page lists what you shipped, with drafts ready to post, each with its own tagged link so the announcement itself is measured.

What upTake never reads

Your code is never read or stored: no files, no diffs, no commit contents.

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 GitHub 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. GitHub is one more piece of that picture.