What Customer.io Webhooks does
Customer.io reporting webhooks send message activity events, such as sends, opens, clicks, bounces, conversions, and failures, as JSON in an HTTP POST to an endpoint you configure. They cover message metrics across email, push notifications, SMS, in-app messages, and other channels Customer.io supports. Requests time out after 4 seconds, and failed deliveries are retried with exponential backoff.
How to identify Customer.io Webhooks
Temso identifies Customer.io Webhookstraffic by matching the request's User-Agent header against this pattern. User-agent strings can be spoofed, so treat a match as an indication, not proof.
Customer\.io Web HooksCustomer.io Webhooks FAQ
What is Customer.io Webhooks?
It is Customer.io's reporting webhook service, which posts message activity events (sends, opens, clicks, bounces, and similar) as JSON to a URL configured in a Customer.io workspace.
Can I block Customer.io Webhooks with robots.txt?
No. These are webhook callbacks sent only to endpoints configured in a Customer.io workspace, not crawler requests, so robots.txt has no effect. To stop the traffic, remove the webhook configuration or block Customer.io's published region-specific IP addresses at your firewall.
About Operational Bots
Monitoring, security scanning, link previews, webhooks, and feed fetchers: the utility traffic that keeps integrations and shared links working.
Most of this traffic is service-critical or user-triggered. Webhooks and previews don't follow robots.txt, and blocking them tends to break things you rely on.
