SpyderBot Documentation
Integrations Overview
Integrations connect SpyderBot to approved website, analytics, infrastructure, CMS, and commerce sources. They primarily extend AI Traffic measurement and related audit workflows. They do not automatically change Brand Insights or Prompt Intelligence response results.
Choose an integration by goal
| Goal | Recommended integration | Important limitation |
|---|---|---|
| Measure AI Referral Sessions | GA4 or SpyderBot Browser Script | Requires attribution context; does not identify the exact prompt |
| Measure on-page engagement and configured goals | SpyderBot Browser Script or configured GA4 | Only configured or received events can be measured |
| Deploy supported measurement without direct code changes | Google Tag Manager | GTM deploys or configures measurement; it is not an independent analytics dataset |
| Observe request-level bot activity and status outcomes | Cloudflare or supported server-side collection | Availability and completeness depend on the connected source |
| Measure supported commerce outcomes | Shopify or configured commerce/analytics flow | Requires valid order or revenue events and supported deduplication |
| Connect CMS or site inventory | WordPress or Shopify | Inventory access is different from traffic measurement |
Integration states
- Not connected â no approved connection exists.
- Connecting â authorization or setup is in progress.
- Connected, no data â the connection exists, but qualifying data has not arrived.
- Connected and receiving â qualifying data is being received.
- Delayed â expected data is arriving later than normal or freshness is degraded.
- Error â the source requires attention and new calculations may be limited.
- Disabled â collection is intentionally inactive.
Connected does not always mean complete. Review Measurement Health before interpreting a zero, decline, or missing result.
Primary-source behavior
When more than one source can measure the same human journey, SpyderBot uses the selected primary source under the applicable product rules. Equivalent sessions or events must not be added together merely because multiple integrations are connected.
For measurement setup and product-specific limitations, see AI Traffic â Choose Measurement Setup.
Google Analytics 4 (install and configuration)
GA4 may provide human-session and configured event data used for AI Referral Traffic and outcomes when measurement is installed and events are configured correctly.
- Install or verify the GA4 measurement tag (or GTM container that deploys it) on the website.
- Confirm the property, stream, and consent settings match the site you measure in SpyderBot.
- Configure referral, engagement, goal, or ecommerce events you need before treating outcomes as complete.
- Validate with a test session and confirm SpyderBot shows connected and receiving.
This documentation describes install and configuration guidance. It does not claim an in-app OAuth "connect Google" flow. GA4 does not provide complete bot-request evidence, and referral attribution normally does not identify the exact AI prompt, response, or model.