-
This issue does seem a bit complicated, but it’s not unresolvable. One of the key problems is Safari’s Intelligent Tracking Prevention (ITP) feature which aims to prevent third-party trackers from capturing information about users’ web activity. It’s stricter with third-party cookies, the ones that are used when your Google Analytics runs in an iframe.
So here’s a possible workaround: you may want to store and pass GA (Google Analytics) data via a server, going around the third-party cookie restrictions. What this entails is creating a new, “first-party” endpoint in your back-end that can collect data from within the iframe, then pass that up to the parent page – your main site. You can then utilize this data to communicate with Google Analytics.
This server-side approach can require more time and technical expertise. Unfortunately as of now, given Safari’s stringent policies, this could be one of the few relatively reliable solutions. You should consider reaching out to a web developer or a team familiar with your web systems, if you haven’t done so already. They probably will be able to provide you a concrete plan to set up this server-side communication for Google Analytics.
