Know which posts bring Dev.to visits and customers
Your published articles with their views, reactions and comments.
What upTake reads from Dev.to
upTake reads your own posts on Dev.to with the public counters Dev.to 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=devto), the visits, signups and payments that link brought are attached to that post.
How to connect Dev.to
You need an upTake project first; creating one takes about four minutes. Click Connect on the Integrations page; a small window asks for what Dev.to needs. API key: In Dev.to, open Settings → Extensions, scroll to “DEV Community API Keys” and generate a key. upTake checks it with Dev.to 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 Dev.to, 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 Dev.to 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. Dev.to is one more piece of that picture.