First of all, it is natural to avoid cross-domain. Usually third-party monitoring platforms are not in the same domain as the website; secondly, using blank gif or 1x1 px img is a common method for Internet advertising or website monitoring. It is simple and safe. This kind of request is used in many places, such as browsing, clicks, hotspots, heartbeats, ID issuance, etc.
Check if there are any parameters on the url? It should be used for burying questions, such as recording what buttons you clicked, what operations you performed, etc.
I don’t know if you are looking at some statistical scripts, such as google-analytics.js
These are scripts embedded in third parties to collect some front-end statistical information and save them on the third-party server. Then you can log in to their management backend to view the statistics.
So this must be cross-domain, so we are indeed avoiding cross-domain
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Mostly for site statistics
First of all, it is natural to avoid cross-domain. Usually third-party monitoring platforms are not in the same domain as the website; secondly, using blank gif or 1x1 px img is a common method for Internet advertising or website monitoring. It is simple and safe. This kind of request is used in many places, such as browsing, clicks, hotspots, heartbeats, ID issuance, etc.
I have done this before, haha.
Check if there are any parameters on the url? It should be used for burying questions, such as recording what buttons you clicked, what operations you performed, etc.
I don’t know if you are looking at some statistical scripts, such as google-analytics.js
These are scripts embedded in third parties to collect some front-end statistical information and save them on the third-party server. Then you can log in to their management backend to view the statistics.
So this must be cross-domain, so we are indeed avoiding cross-domain