Server Side Analytics: Spike in Requests
You've set up an account with TAGGRS and initiated Server Side Tracking. After configuring everything, the requests start flowing in. However, after some time, you notice a spike in your request metrics within the TAGGRS dashboard.
In this article, we will explore the most common reasons for spikes in your TAGGRS dashboard's request graph. These reasons are ranked from most to least common.
Let's walk through the possible causes step by step and how to effectively address them.
Let’s get started..
1: Bots accessing subdomain
One of the primary reasons for this spike could be bots accessing the subdomain. These could be various bots or indexes, or even instances where you have accessed the subdomain yourself. Unfortunately, there isn't much you can do to completely prevent this from happening.
2: Cookiebot
Are you using Cookiebot as your CMP? It might be that the spike in requests is due to the Cookiebot scanner crawling your website. More info can be found on cookieinfo.
What can be done to prevent this spike in traffic?
There is no way to prevent these scans, but you can exclude this traffic from your regular website statistics by either excluding the provider 'Microsoft Corporation' or by excluding the IP addresses we scan from:
13.74.44.241
23.100.63.22
34.107.102.47
34.111.104.227
34.111.239.10
34.141.10.24
34.149.178.113
34.159.86.126
34.159.168.195
34.159.247.222
35.198.78.207
35.198.137.6
35.198.160.49
35.246.143.2
35.246.191.14
40.91.211.73
40.118.23.197
52.232.29.198
52.232.29.198
It is crucial to exclude these before they reach the server container; otherwise, they still be counted as requests in TAGGRS. The process of excluding these IP addresses is detailed in our ip addresses exclude / anonymize blog.
Note: Excluding these IP addresses may impact certain reporting functions since Cookiebot bots will be excluded. If these reports are not essential for you, this exclusion method can be used. Example reporting Cookiebot.
Wrapping up
These are the primary reasons for spikes in request metrics within the TAGGRS dashboard. If the cause of your situation is not listed here, please submit a support ticket.