> 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/latest-news/improved-bot-click-filtering-human-only-ctrs-are-here.md). # Improved Bot Click Filtering: Human-Only CTRs Are Here Explains how Recart now filters bot clicks from SMS link data so click-through and revenue numbers reflect real subscribers. At Recart, we’re always working behind the scenes to improve data accuracy and performance tracking for our merchants. That’s why we’re excited to share an update that makes your click-through rates (CTRs) more reliable than ever before. ### What Happened? Since mid-September, we began noticing **unusual spikes in CTRs** on both campaign and automated SMS messages. These jumps were tied to **increased bot activity**, (mainly in AI/LLM crawler bots) part of a broader trend as bots evolve and mimic human behavior more closely. We experience anomalies across most ecosystems: Shopify Analytics, GA4, Hubspot tracking systems all struggle with the new swarm of bot activity. ### The Fix Over the weekend, we rolled out a **powerful new bot filtering solution** using **Cloudflare’s active detection system**. Unlike static detection methods, this upgrade identifies and filters out bots in real time — with **99.9% accuracy**. CTR levels returned to expected benchmarks as of **October 6**. ### Why This Matters * **Accurate Click Reporting:** Your CTRs reflect actual human engagement again, excluding all bot traffic. * **Better Alignment with Shopify & GA4:** Recart’s click figures are now even closer to your everyday analytics. * **Smarter Bot Defense:** While bots continue to evolve, the active detection will keep your click statistics clean. ### What to Expect You may notice CTRs are now **10-20% lower** than what you saw in the past couple of weeks. That’s expected and a good sign. It means the data you’re seeing is now **bot-free and more trustworthy than ever**. **Your marketing decisions should be based on real insights — not inflated numbers.** As always, reach out to if you have any questions. *Last updated: October 2025* --- # 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/latest-news/improved-bot-click-filtering-human-only-ctrs-are-here.md?ask=&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.