Bot intelligence record
Omnisend
Usually allowUse the Omnisend identifier to separate Omnisend commerce, ad, checkout, or payment-related traffic from normal visitor requests in server logs.
- Operator
- Omnisend
- Family
- Omnisend
- Type
- Ecommerce
- Source type
- Verified Directory
- Last checked
- 2026-05-20
User-Agent Pattern
OmnisendOmnisend
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: Omnisend Disallow: /Click the snippet to copy it, or highlight the text manually.
Handling Guidance
NoThis bot is usually safe to allow when the request source is verified and the traffic matches your site policy.
Commerce, checkout, product, advertising, or payment-related verification requests.
Record Details
Structured data- Operator
- Omnisend
- Family
- Omnisend
- Type
- Ecommerce
- Purpose
- Ecommerce
- Identity type
- Verified Bot
- Confidence
- Medium
- Last verified
- 2026-04-01
- Last checked
- 2026-05-20
- Source type
- Verified Directory
- Verification
- Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
- Spoofing risk
- User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.
Notes
Omnisend is listed in the Botcrawl directory as a commerce-related fetcher from Omnisend. The primary identifier for log review is Omnisend.
Identification
- User-agent pattern:
Omnisend - Family: Omnisend
- Type: Ecommerce
- Kind: Fetcher
Common use
Commerce, checkout, product, advertising, or payment-related verification requests.
Verification and handling
Confirm the user-agent against server logs and use published operator documentation, IP ranges, reverse DNS, or other trust signals when available.
Directory guidance marks the risk level as Safe and the blocking decision as No. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.
Robots.txt handling: No.
Evidence and Source
- Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
- Match `Omnisend` as a case-insensitive substring in HTTP user-agent logs. Use bot_http_agent for full user-agent examples when the client sends a longer browser-like string. Do not treat a user-agent match alone as proof of identity for allow-listing.
- Commerce, checkout, product, advertising, or payment-related verification requests.
- User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.