New integration — Kinsta managed WordPress
Sites hosted on Kinsta can now connect to LogLens with just a Kinsta API key — we pull your access logs every 15 minutes through the official Kinsta API, no agents and no CDN changes required.
Kinsta's managed WordPress platform doesn't allow agents on its servers, and its built-in edge means CDN-level integrations can't see your traffic either. Until now that left Kinsta-hosted sites with manual log uploads only.
Today LogLens gains a native Kinsta integration:
- One-key setup. Create an API key in MyKinsta (Company settings → API
Keys), paste it together with your site's environment ID, and you're done. We verify the credentials against the Kinsta API live during setup — if something's wrong, you find out immediately, not silently later.
- Continuous ingestion. We pull your access log through the official
Kinsta API every 15 minutes, de-duplicate overlapping fetches automatically, and feed the same analytics pipeline as every other integration — bot verification, SEO analysis, alerting, the lot.
- Works with delegated setup. Send your developer a setup link and they
can connect the site without needing access to your LogLens account.
- Honest about gaps. Kinsta retains only ~4 days of logs and our pulls
read the recent tail; if a traffic spike ever outruns the polling window, we flag the gap on the site record rather than pretending coverage was complete.
You'll find Kinsta as a setup option when adding a new website, alongside Cloudflare, CloudFront, Vercel, and Apache/Nginx.