close this to read article
Bot and crawler visits do not consume your Monthly Tracked Users (MTU) or Monthly Active Users (MAU) quota when Wingify successfully identifies them as non-human traffic.
Wingify uses the following layered approach to detect and drop bot traffic before it is counted:
-
User-agent Keyword Matching
Wingify scans the visitor's user-agent string for known indicators such as bot or crawler. If a match is found, the visit is excluded from your campaigns and does not count toward your MTU or MAU quota. -
Known Bot IP addresses
Wingify also checks incoming visits against a pre-defined database of known bot IP addresses. This server-side check automatically blocks bot traffic before it is tracked, preventing it from appearing in your campaign data. -
Wingify BotList
Wingify maintains a proprietary BotList built by combining data from multiple third-party bot-detection aggregators. The list contains several thousand entries and is updated automatically every month.
When an incoming visitor's user-agent matches an entry in the BotList, Wingify discards that traffic at the point of collection. The visit is discarded and does not consume MTU or MAU. -
Manual Exclusion: You can further reduce bot traffic on top of Wingify’s automatic detection in two ways:
- Segmentation conditions: Set up user-agent based or IP-based segmentation conditions on your campaigns to manually exclude specific bot traffic you've identified, before it enters that campaign. For more information, see Configure Custom Segmentation in Wingify.
- Account-wide IP exclusion: Add known bot or unwanted IP addresses to your IP exclusion list in Settings > Privacy Center. For more information, see Exclude IP Addresses from Wingify Tracking to exclude that traffic across your entire account.
Note: New bot detections take some time to be categorized and added to the BotList. When a new bot's traffic pattern first appears, Wingify's systems, like other bot detection systems across the industry, require an observation period to confirm the pattern is bot traffic before it can be added to the BotList. As a result, visits from the bot that occurred before it was added to the BotList would not have been excluded, as the matching criteria didn't yet exist. This is a standard limitation across the industry, and is not specific to Wingify.