I am facing unusual traffic on my site which only happens when I start a campaign for my site on google ads. For example 1 have 30k products and one product is having more then 20 traffic or more and others are at 2,3 and I am facing this issue from a long time.
What steps have you taken to resolve the issue?
Put site under attack mode,
Deployed OWASP
Enabled WAP
Disabled non-verified bots on my site
Was the site working with SSL prior to adding it to Cloudflare?
Yes
What is the current SSL/TLS setting?
Strict (SSL-Only Origin Pull)
What are the steps to reproduce the issue?
There are not proper steps just to post a campagin and it start, if I stoped the campaign it number also drops and again it starts back as soon as I click start on my campaign.
Honestly I’m not seeing anything too concerning in your traffic.
For instance, if we take that big spike yesterday and filter for 10 minutes, from 13:00 to 13:10 UTC, we can see that the traffic was well distributed, for instance, only 2 IPs did more than 15 requests, and these 2 IP addressees belong to Google bot, so it’s expected.
For the remaining traffic, we can see a very good distribution between browsers, OSes and paths, with the most hits on /index and /cart, as you would expect.
From what I can see, this is perfectly normal traffic, you started a campaign and are getting extra hits.
If your concern is the extra load at the origin, you should consider caching more. Checking your cache performance under “Caching” > “Overview”, we can see that most assets are not being cached and instead served directly from the origin. Now, while not caching cart.php is generally a good idea for obvious reasons, the same can’t be said for the product pages, that, as far as I’m aware are static, so you might want to consider a cache rule to cache /products/ for instance. In fact, I would probably do it the other way around by creating a cache rule to cache absolutely everything and then create a cache bypass on the assets that should not be cached, like the admin backofice, cart, and other private areas.
Do note that if you create a cache everything rule, whenever you change something at a product page, the change might only be reflected when the cache expires or when manually purged.
Also, be very careful with browser cache (if you consider using it) because unlike edge cache, it can’t be force deleted until the expiration date.
