Do you make use of the Salesforce Marketing Cloud & Google Analytics integration? Verify if everything still works. Google depreciated analytics.js, a library that the default integration depends on. More details in the post of our colleague Dimitri Dries.
On July 1st, Google completed the full deprecation of Universal Analytics. We recently discovered a significant additional change that Google did not mention at all. With the introduction of the gtag library as the new version of the analytics.js library back in 2017, Google ensured that gtag still loaded analytics.js to maintain setups leveraging this library. A popular use case for leveraging this was the integration between Google Analytics and Salesforce where Google, in its own documentation, recommends the use of the “ga” object, which is a part of analytics.js. https://lnkd.in/eRFmfMgt (documentation that, to this day, still has not been updated for GA4). What we are seeing today is that Google’s gtag library stopped loading the analytics.js library, breaking any setup that was leveraging certain parts of this library. A reason for still leveraging the analytics.js library is that not all information available in analytics.js is as easily accessible in gtag. Some examples are: - Cross-domain linker parameters - The client ID - The user ID - The measurement ID Due to the lack of communication and documentation from Google, we had to discover and solve this ourselves. Anyone still using certain parts of analytics.js, be warned! Let me know in the comments if you’re facing similar issues. #Measure #GoogleAnalytics #DigitalAnalytics #gtag