Skip to main content
Project Home presents measurement by capability, while Integrations exposes the sensors that provide it. This page explains which sensors you need and where the alternatives are genuinely interchangeable.

​
Capabilities and their sensors

The crawler providers are alternatives, so DevTune never requires both for the same hostname. The tracking snippet and GA4 are also alternatives for referral coverage, although they provide different measurement: the snippet records first-party referral page views, while GA4 supplies the referral-session views across AI Demand. Search Console and GA4 are complementary for Search performance: each adds different Google ground truth, so connecting only one reports Partial.

​
What to connect, in order

  1. One crawler sensor per hostname. Cloudflare pull suits hostnames already proxied through Cloudflare, including docs and static hosts. Edge middleware suits Vercel, Next.js, and other app hosts where request middleware can run. Compare the two.
  2. Connect GA4. Attribution, conversions, and engagement come only from here. Select the key events you count, or conversions stay unmeasured rather than reading as zero.
  3. Optionally add the snippet for first-party referral visits - a record you own end to end, reportable over the API and independent of GA4. Generate the snippet key first if you plan to install the edge middleware: the middleware’s ingest key only becomes available once your project has one.
The minimum viable setup is one crawler sensor plus GA4. Together they cover both halves of AI Demand - what machines fetch, and what people do afterwards. The snippet is an addition to that pair, not a replacement for either.

​
Where each number comes from

The Conversions view reads GA4 on both sides: AI-referred sessions and the key events they convert into come from the same GA4 property, matched on landing page and the session source DevTune classifies as an AI engine. That keeps both halves of a conversion rate on the same measurement basis. It links AI referrals to outcomes directionally; it does not follow individual visitors. Where a sensor is not connected, the number reads as no data and links you to Project settings → Integrations. You only ever see a zero where the sensor was watching for the whole period, so an empty stretch is reported as no data rather than as none.

​
Keep each site on one crawler sensor

Pick one crawler sensor per site and stay with it. Nothing stops you from switching both on, but you gain nothing by doing it: where Cloudflare already covers a hostname, its data wins for bot traffic there, and the duplicate events from the other sensor are discarded so the same request is never counted twice. Those discarded events still count against your monthly event allowance. So if you find both active on the same hostname, remove or pause the one you do not want. Edge middleware is switched on for a whole project rather than for a single hostname, so on a project running both, Cloudflare wins on every hostname it covers.

​
How current each sensor stays

A sensor reports as Active while data from it has arrived recently. How recently depends on the sensor: The windows differ because the sources deliver differently: crawler and snippet events reach DevTune as they happen, while GA4 and Search Console are collected on a schedule and fill in history afterwards. Do not read a quiet site as a broken one - a hostname that goes an hour without an AI crawler hit still reports as Active.

​
Next steps