Known-crawler protection
See crawler activity on your website and choose how Tyton handles it.
Choose a mode for each website
Open Sites & Pixels, choose the website, then use Bot protection → Edit.
| Mode | What Tyton does |
|---|---|
| Off | Turns off crawler checks and activity counts for this website. |
| Observing | Checks for known crawlers while letting events through as usual. New websites start here. |
| Shield | Filters recognized crawler events before Tyton sends them to the Pixel or Conversions API. Your website stays open to everyone. |
Existing websites remain Off until their owner makes a choice. Choose Shield only after reviewing the analysis. The setting can take up to 60 seconds to reach the gateway cache.
What Tyton recognizes
The initial detector is intentionally narrow: Googlebot (including Googlebot-Image, Googlebot-Video, and Googlebot-News), bingbot, facebookexternalhit, and meta-externalagent.
Tyton filters only the recognized crawlers listed above. Events with missing, oversized or unclear browser information pass through as usual.
Read the counts carefully
The counts summarize browser events across the past 24 UTC hourly buckets. One visitor can generate several events. In Observing mode, Tyton may show a notice after repeated crawler activity across several hours. You decide whether to turn on Shield. Dismissing the notice hides it for seven days and keeps your current mode.
What Shield covers
Shield covers the listed crawlers when events use Tyton’s current browser SDK and Tyton-managed Pixel. Other crawlers, independently installed Pixels and older SDKs remain outside that coverage. Events sent with server keys and confirmed backend purchases continue through their existing delivery flow. Your consent settings, approved tracking plan, website access and Meta’s matching rules stay the same.
If a network problem prevents a crawler check, Tyton lets the Pixel continue sending. The activity counts reflect checks Tyton completed, so some traffic may be missing from them.
For an unexpected result, keep the original event ID and review event delivery alongside the order or submission in your app.