Know which posts bring Kit visits and customers
Your sent broadcasts with their recipients, opens and clicks.
What upTake reads from Kit
upTake reads your own posts on Kit with the public counters Kit gives for them, going back up to 90 days on the first sync. Each post becomes an entry in your log of actions. When a post contains one of your tagged links (yoursite.com/?ut=kit), the visits, signups and payments that link brought are attached to that post.
How to connect Kit
You need an upTake project first; creating one takes about four minutes. Click Connect on the Integrations page; a small window asks for what Kit needs. API key: In Kit, open Settings → Developer → API keys and create a V4 key. upTake checks it with Kit before saving it.
What you see afterwards
Your posts sit in the Posts & actions log with the visits, signups and revenue each one brought, and as markers on your traffic chart. The weekly report ranks them, says which ones only brought attention, and suggests what to post next.
What upTake never reads
upTake never posts, likes or replies for you on Kit, and it does not read your private messages or the list of people who follow you.
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 Kit 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. Kit is one more piece of that picture.