Connect the request data your website already produces.
Stream first-party request logs from the CDN, hosting platform or web server you already run. Salience verifies who every client really was, finds the crawl waste, errors and automated abuse hiding in the traffic, and tells you when something changes, without you building a pipeline, a dashboard or a classifier.
Connect in minutes with no code changes on most platforms. The free tier needs no card, and several platforms sit in one account.
Which integration should I use?
- Cloudflare
Your site is proxied through Cloudflare, or could be
Cloudflare: a Worker on your zone, any plan including Free
- Vercel
A Next.js or other project deployed on Vercel
Vercel: a Drain streaming requests as they happen, on Pro or Enterprise
An AWS site or application delivered through CloudFront
AWS CloudFront: real-time logs through Kinesis and Firehose
WordPress hosted at Kinsta
Kinsta: an official API pull, with nothing installed on the site
- Shopify
A Shopify store on your own domain
Shopify: your own Cloudflare zone, via Orange-to-Orange
- Apache or Nginx
A server you manage, running Apache or Nginx
The Vector agent, tailing the access log you already write
- Netlify
A site deployed on Netlify
A Netlify log drain, configured from the app in a few minutes
- Google Search Console
You want Google's index status alongside all of it
Google Search Console: read-only, a Google sign-in to connect
- Google Analytics
You want GA4 sessions, key events and revenue next to the requests
Google Analytics: read-only, a Google sign-in to connect
Every integration compared
- Method
- Cloudflare Worker
- Cadence
- Streaming
- Freshness
- Within seconds
- Setup
- Worker on your zone, ~10 min
- Historical import
- Via origin-log file import
- Key limitation
- Sees only requests reaching the Worker stage on proxied records
- Method
- Vercel Drain
- Cadence
- Streaming
- Freshness
- Within seconds
- Setup
- Drain in team settings, ~10 min
- Historical import
- No, starts at connection
- Key limitation
- Drains are not available on the Hobby plan; no backfill
- Method
- Kinesis + Firehose real-time logs
- Cadence
- Streaming
- Freshness
- Seconds to minutes
- Setup
- Kinesis + Firehose in AWS, 30–60 min
- Historical import
- Yes, standard log files
- Key limitation
- Sampling below 100% delivers a sample, not every request
- Method
- Kinsta API log pull
- Cadence
- Scheduled pull
- Freshness
- Every 15 minutes
- Setup
- API key + environment ID, ~5 min
- Historical import
- Up to ~4 days (Kinsta's retention)
- Key limitation
- Scheduled pull, not streaming; access log only
- Method
- Cloudflare O2O Worker
- Cadence
- Streaming
- Freshness
- Within seconds
- Setup
- Cloudflare O2O + Worker, 30–60 min
- Historical import
- No, Shopify exposes none
- Key limitation
- /checkout cannot be observed (Workers disabled there)
- Method
- Vector agent
- Cadence
- Streaming
- Freshness
- Within seconds
- Setup
- Vector agent, ~10 min
- Historical import
- Yes, rotated/archived files
- Key limitation
- Access logs only; timing needs a %D-style field
- Method
- Vector agent
- Cadence
- Streaming
- Freshness
- Within seconds
- Setup
- Vector agent, ~10 min
- Historical import
- Yes, rotated/archived files
- Key limitation
- Access logs only; real client IP needs care behind proxies
Data connections
These add context to the request stream you already have, so what a search engine decided sits next to what your server did.
Google Search Console
Read-only access through the official Search Console API. Google's index status, shown beside the response your server gave each Googlebot request.
Connect Google Search ConsoleGoogle Analytics
Read-only access through the official Google Analytics Data API. Sessions, engagement, key events and revenue per landing page, next to the requests your server served, and the share of human traffic GA never recorded.
Connect Google AnalyticsEvery source ends up in the same dashboard
However the data arrives (Worker, Drain, Firehose, API pull or agent), every event normalises into the same request model, and from there every integration gets identical treatment: classification against a registry of 200+ crawlers, verification against published provider ranges, section grouping, baselining, the same sixteen detectors and the same written triage on every alert.
Trust & data protection
Privacy and data protectionYou are the controller
We process only on your instructions. GDPR Art. 28 DPA on every account, nothing to sign.
UK data residency
AWS eu-west-2 (London). Encrypted in transit (TLS 1.2+) and at rest (AES-256).
Server-side collection
No browser tracking script and no client-side pixel.
No sale, no pooling
Your logs are never sold, never used for advertising, never shared between customers. DPA, sub-processor list and security overview available.
Crawler intelligence from $19/mo.
Priced on requests, not seats. Unlimited users on every plan except Solo. Start on the free tier and upgrade when your traffic does. Free trial, no card needed.
- 500K requests/mo
- 1 site
- 30 days history
- Unlimited users
- Real-time analytics, bot and AI detection
- 20M requests/mo
- 5 sites (+5)
- 1 year history
- Unlimited users
- Real-time analytics with bot and AI-crawler verification
- 100M requests/mo
- 15 sites (+15)
- 2 years history
- Unlimited users
- AI allowance: ~600 answers or ~60 reports a month
- 500M requests/mo
- 50 sites, no ceiling
- 4 years history
- Unlimited users
- AI allowance: ~3,000 answers or ~300 reports a month
- 1B requests/mo
- Unlimited sites
- Custom history
- Unlimited users
- SSO / SAML and audit log
Common questions
Can I connect more than one platform to the same account?
Yes, and most organisations do. Each site connects its own source and appears separately in one organisation, with the same dashboards, the same alert catalogue and the same API. Because everything normalises to one request model, reports read identically whatever produced the data.
How long does setup take?
Between a few minutes and an hour depending on the platform. Search Console, Kinsta and Netlify are the fastest; Cloudflare, Vercel, Apache and Nginx are around ten minutes; Shopify and AWS CloudFront take longer because there is more to configure at their end. Each page states its own figure.
Do I need a developer?
For most platforms, no, but you do need access. A Cloudflare Worker needs someone who can deploy one; a Vector agent needs root on the server. Where that is not you, setup can be delegated from inside Salience without sharing your account.
What if my platform isn't listed?
Almost certainly not. Putting a free Cloudflare zone in front of your site works for practically any host (GitHub Pages, IIS, managed WordPress and the rest; Netlify has its own log drain), and the Cloudflare integration then applies. The setup guide walks through it in about fifteen minutes.
Can I import log files I already have?
Yes. Apache, Nginx and CloudFront access logs and exports from other log analysers upload with automatic format detection, deduplicate against anything already streaming, and never count against your monthly request quota.
How is this different from Google Analytics?
GA4 measures what its tag collects in a browser, and filters known bots out by design. Salience reads server and CDN request data, so it sees every request that reached your site, including the bots, crawlers, AI agents and scrapers that never execute a tag. Use GA4 for human behaviour and conversion; use Salience for the request stream.
What happens to our data, and where is it stored?
You are the controller; Salience processes only on your instructions under a GDPR Art. 28 DPA that applies to every account. Data is stored encrypted in AWS eu-west-2 (London), never sold, never used for advertising and never pooled between customers.
Can I disconnect later?
Yes, from your side, on every integration: remove the Worker, delete the Drain, stop the agent, revoke the key. Collection stops immediately and nothing is left behind on your platform to unwind.
Your logs already show what Google and the AI crawlers are doing.
Connect in minutes with no code changes on most platforms. The free tier needs no card, and several platforms sit in one account.