Skip to main content
Can AI see it

Know what AI sees. Measure what it's worth.

← Back to bot catalogue

What is FullStory?

Direct Answer: FullStory is your digital experience analytics platform for on-the-fly funnels, pixel-perfect replay, custom events, heat maps, advanced search, Dev Tools, and more. FullStoryBot’s fetches and stores assets required to rebuild sites when viewing recorded sessions.

Operator: Full Story Type: Monitoring Bot Purpose: Website monitoring

User-Agent Identification

The following user-agent strings identify FullStory in your live traffic data:

  • FullStoryBot/1.0

robots.txt Rules for FullStory

Respects robots.txt: No

This bot does not commit to following robots.txt

FullStory does not officially follow robots.txt directives. The only reliable way to control access is through server-side blocking (IP filtering, user-agent rules in your web server config) combined with log monitoring to verify effectiveness.

Need continuous verification across 500+ bots? Can AI See It automates this.

Crawl Activity Index

Relative crawl activity for FullStory over the past 28 days. Higher values indicate increased crawling intensity compared to the period baseline.

View recent activity data (last 7 days)
Date Activity Index
May 25, 2026 63.6
May 26, 2026 80.8
May 27, 2026 75.8
May 28, 2026 90.4
May 29, 2026 94.7
May 30, 2026 57.9
May 31, 2026 57.4

Source: Cloudflare Radar

Why track FullStory traffic?

Distinguish monitoring traffic from real crawler activity. FullStory checks your site availability at regular intervals. Without proper identification, these requests can inflate your bot traffic metrics and distort crawl analysis.

Validate monitoring coverage. Track which pages FullStory checks and how frequently, so your monitoring setup matches your infrastructure requirements.

Log Verification

To verify FullStory traffic in your live traffic data:

  1. Search access logs for the user-agent strings listed above
  2. Check if the IP addresses match documented ranges (if provided by Full Story)
  3. Verify the crawl pattern matches documented behavior
  4. Use reverse DNS lookup for additional verification if available

Note: Observed behavior in production environments may differ from official documentation. Live traffic monitoring provides the only reliable verification of actual bot behavior.

Official Documentation

View Official FullStory Documentation →

Information sourced from official documentation. Content generated with AI assistance.