SpyderBot Documentation
Choose the measurement needed for your AI Traffic question
You want to understand AI traffic, but the available integrations measure different activities. Start with the question you need to answer, then connect the source that can support it.
Your outcome: the required measurement source is connected and its relevant coverage is verified, or the missing capability is clearly identified.
1. Match the question to the evidence
| Your question | Required evidence | Relevant source type |
|---|---|---|
| Are AI-related bots requesting our pages? | Request-level activity and requester evidence | Supported server or edge integration |
| Are requests failing or being blocked? | HTTP/access events for the relevant requester and URL | Supported server or edge integration |
| Are human visitors arriving from AI platforms? | Human referral sessions with attribution | Supported Script or GA4 measurement |
| Do those visitors take the next step? | Human sessions and configured goals | The primary supported human measurement source |
| Do those visits lead to purchases? | Supported commerce events and attribution | A compatible configured commerce measurement setup |
GTM can deploy tracking; it is not a separate audience to add to Script or GA4. A platform plugin can simplify installation, but the installed measurement's actual capabilities determine what you can conclude.
2. Configure the supported integration
Use the integration instructions for the source available in your account. Involve the website or analytics owner when installation requires access you do not have. Keep one designated human source for the comparison; connecting two does not justify adding their session totals.
Check the measured site, environments, time range, and goal configuration. A connection label alone does not establish that useful data is arriving.
3. Verify the measurement you plan to use
Confirm a relevant recorded event using the source's supported verification procedure. Check that it belongs to the intended page and environment. A direct test visit can help verify collection but does not prove AI-referral attribution; do not relabel it as AI traffic. For bot analysis, inspect actual request evidence rather than a browser page view.
If no relevant event is available yet, distinguish a working connection from an established observation. Use Measurement health and integration diagnostics to resolve collection problems.
You are done when the source and its evidence support the intended analysis. Continue to Fix issues affecting important pages for access problems or Find AI referral pages worth improving or expanding for human outcomes.