I can extend the cookie duration for users who use iOS systems as the server becomes a first-party context. Reduction of the impact of ad-blockers which, not infrequently, also impact requests sent to and from Google Analytics. As usual, not all that glitters is gold and therefore, the pros are also followed by several cons .
The main disadvantages of this solution concern the know-how taiwan cellphone number in implementing the server instance on Google Cloud Platform or on AWS. Not everyone has this expertise and often the effort increases because it is necessary to refer to the IT department to which you have to explain the needs and reasons for implementing this solution.
There are server maintenance costs that vary depending on traffic volumes and the scalability of the service (we are talking about deltas that can go from €50 to €200/month but can also go higher. A cost guide can be found here ).
While it's true that I told you earlier that you reduce the exposure of user credentials on the browser by adopting a server-side tracking solution, the downside is that what happens on the server is less controllable and more opaque.
Spam risk and high bill : another risk is that the requests sent from the client to the server could be hacked, impacting the final costs (it is true that in GCP, in the Billing > Budget&Alerts section, it is possible to insert alerts for cost monitoring, but it is important to be aware of the problem).
If I have to summarize the main steps of the implementation, I can tell you that these are the main steps to follow: