How Nixon Cut Bot Traffic by ~90% Within Hours of Deploying Nostra Edge Protect

For most of April and the first week of May, Nixon's storefront was absorbing repeated bursts of bot traffic. The peaks were dramatic. On more than one day, automated traffic spiked to four or five times the brand's normal sessions. Steady surges across days, brief pull-backs, then another wave climbing back up.

The cost showed up in two places at once. The first was the conversion rate dashboard. As bots flooded the session counter, Nixon's measured CVR collapsed to a fraction of its real value. At the worst point, it was sitting at less than a quarter of what the team had seen the week before, even though real shoppers were still shopping and real orders were still flowing through. The denominator had been quietly replaced by traffic that would never convert, and the result was a metric that looked like a five-alarm fire while the underlying business was unchanged.

The second was every channel that depended on those dashboards. Inflated session counts were feeding fake users into retargeting audiences and lookalikes. Geographic reporting drifted out of sync with reality. Bandwidth was being consumed by visitors that would never spend a dollar. Every dashboard the team relied on was running on a polluted baseline, and the pollution was getting worse, not better.

Nixon brought Nostra Edge Protect online on May 8. The change in the chart is sharp enough that you can pick the date out without a label. The scraping infrastructure didn't stop pointing at Nixon's URLs. It just stopped getting through to them. Edge Protect filters bot traffic at the edge of the network, before requests can fire a session event, reach Shopify, or enter the audience pools that pipe into Meta, Google, and Klaviyo.

Within hours, daily bot sessions dropped by roughly 90%. The same day, the measured conversion rate snapped back. It wasn't a behavioral change in Nixon's customers. It was a measurement change. The denominator had been cleaned up, and the real CVR became visible again for the first time in days. Within twenty-four hours of deployment, the conversion rate dashboard was reflecting what was actually happening on the site, not what bot traffic had been masking.

The story didn't end at restoration. As Edge Protect continued filtering residual bot traffic over the following week, Nixon's daily sessions kept trending down toward true human-only volume. The measured conversion rate climbed in step, and by mid-May had reached roughly ten times its low point during the attack. Higher than pre-attack baseline. Higher than the team had probably seen in months. Same shoppers, same products, same campaigns, all that changed was the accuracy of the denominator.

The point of Edge Protect isn't to eliminate every bot request. It's to remove the ones that hurt the business and let the ones that help it through. The residual bot traffic Nixon sees today is mostly Googlebot, Bingbot, ChatGPT, Claude, SEMrush, Ahrefs, and the other crawlers that keep the site indexed, ranked, cited in AI answers, and surfaced in third-party tools. Killing those would mean killing discoverability. Edge Protect is built to be surgical by design.

The deeper story is what the Nixon team can now do that they couldn't reliably do before. Conversion rate dashboards reflect real customer behavior. Retargeting audiences are clean. Ad spend is feeding back signal from humans, not from scrapers and scalpers. Every business decision rolling off those dashboards is now running on a baseline the team can trust. One commercial detail worth flagging, because it's unusual in this category. Nixon brought Edge Protect on with no financial risk. Nostra doesn't get paid unless we're protecting real revenue. The bot reduction, the conversion rate recovery, and the cleaner baseline since, all sit on top of a pricing model that only invoices when the math works.