> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/compliance-protections/built-in-protections/bot-filtering.md).

# Bot Filtering

How Recart keeps bots out of your SMS marketing: bot clicks on your message links and bot sign-ups on your popups.

Bots show up in two places in SMS marketing. They open the links in your messages, and they enter phone numbers into your popups. Recart filters both automatically, so your numbers reflect real people and you don't pay for texts that bots trigger. There's nothing to set up.

### Bot clicks on your messages

When you send an SMS campaign, not every click on your links comes from a real person. Recart automatically filters out non-human clicks, so the click rates and revenue numbers you see in your dashboard reflect actual subscribers.

#### Where bot clicks come from

Before a text message reaches a phone, it often passes through automated systems that open every link in it:

* **Carrier security scanners** — mobile carriers scan links in messages to check for phishing and spam.
* **Device and app link previews** — some phones and messaging apps fetch a link to generate a preview.
* **Security software** — corporate and antivirus tools open links to inspect them.
* **Crawlers and AI bots** — automated tools that browse the web, including AI crawlers, also follow links, and they're getting better at behaving like people.

Each of these opens your link exactly like a click. Without filtering, they get counted as engagement — inflating your click rate and making your conversion rate look worse than it really is.

#### How the filtering works

Recart checks every click at the moment it happens, using two independent layers:

1. **Bot signature detection** — a continuously updated database of known bots, crawlers, and scanners.
2. **Behavioral bot scoring** — powered by Cloudflare, the network that sits in front of roughly one in five of all websites on the internet. Because Cloudflare sees traffic at that scale, its bot detection recognizes automated visitors by how they behave, not just by what they call themselves — including scanners that disguise themselves as regular phones. Rather than building a bot filter in-house, we plugged Recart into one of the most widely deployed bot-detection systems in existence — the same protection used by some of the largest sites on the web.

If either layer identifies the visitor as a bot, the click is excluded from your analytics. The link itself still works normally — filtering never blocks or slows down anyone, it only decides what gets counted.

#### What this means for your numbers

* **Click rates in Recart may look lower than on other platforms.** If your previous SMS tool counted bot clicks, its click rates were inflated. Lower-but-real numbers are the ones you can plan against.
* **Closer to your other analytics.** Because bot clicks are left out, Recart's click numbers line up more closely with what you see in Shopify Analytics and Google Analytics.
* **Your conversion rate and revenue-per-click are more accurate.** Because the denominator only contains real people, you can trust these numbers when deciding what to send next.
* **No setup needed.** Filtering is always on, for every message, on every plan.

### Bot sign-ups on your popups

Some bots enter phone numbers into signup forms just to trigger texts, like a one-time code or a confirmation text. This is known as SMS pumping. Those texts are sent and charged like any other message, so without protection you'd pay for texts nobody asked for.

Recart protects your popups in three ways:

* **Automated sign-ups are blocked.** Sign-up requests that look automated are stopped before any text is sent
* **A limit per phone number.** The same phone number can only request a limited number of opt-in texts on your site each day
* **A daily limit per site.** Each site has a daily limit on opt-in texts, like one-time codes and confirmation texts. It's set well above your normal traffic, so your real shoppers don't notice it

This applies to popups that send a text to finish the sign-up: [In-Popup Confirmation](https://help.recart.com/list-growth/popups/opt-in-tools-in-popup-confirmation.md) (one-time code) and [Reply in SMS as Consent](https://help.recart.com/sms/subscribers-and-lists/sms-opt-in-types.md#reply-in-sms-as-consent).

#### If your site reaches its daily limit

Your popup still shows, but shoppers who sign up don't get a code or a confirmation text. They see an error instead. Sign-ups work again as soon as the limit resets the next day, or as soon as your limit is raised.

{% hint style="info" %}
**Expecting a big rise in sign-ups?** For example a product launch, Black Friday or a large campaign that sends traffic to your popups. [Contact the Recart Support team](https://help.recart.com/contact-recart-support.md) or your Customer Success Manager beforehand, and we'll raise your limit.
{% endhint %}

### Frequently asked questions

**Does click filtering ever block a real subscriber?**

No. Every visitor is redirected to your store regardless of classification. Filtering only affects whether the click appears in your analytics.

**Can I see the filtered clicks somewhere?**

No — bot clicks are excluded before they reach your reports, so there is no separate bot report.

**Why does my link show a click before the message could have been read?**

That's typically a carrier scanner opening the link right after sending. This is exactly the traffic Recart filters out of your stats.

**Will the daily sign-up limit affect my real shoppers?**

Not in normal use. The limit is set well above your usual daily sign-ups. If you're planning something that could bring in far more sign-ups than usual, contact us beforehand so we can raise it.

**Am I charged for blocked sign-ups?**

No. When a sign-up is blocked, no text is sent, so there's nothing to charge.

If you have any questions, do not hesitate to [contact the Recart Support team.](https://help.recart.com/contact-recart-support.md) We'd be happy to help!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.recart.com/compliance-protections/built-in-protections/bot-filtering.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
