This one is likely a bit more obvious

mdh673558

To help address these issues, there are a few potential workarounds: Adjusting your reports so that you’re less likely to hit quota limits. Exporting to BigQuery first (which does have its own limitations), then connecting BigQuery to Looker Studio. Using a third-party tool that automates the export/import timing to manage quota limits. Being aware of Looker Studio’s specific limitations and how to recreate reports around those is a good starting point for avoiding confusion and frustration surrounding these reports. 6. Events, goals and historical data.

Still, depending on how they were initially set up and whether you migrated your UA account or events to GA4, you may or may not have events populating in your DB to Data reports. If your events weren’t migrated over, you’ll want to create new events and goals within GA4 (mainly if these were “hard coded” via UA). Similarly, while some UA accounts are still recording data, Google is sunsetting UA, and eventually, you’ll be missing data there. You won’t have GA4 data before it is installed on your site. All this may not occur immediately when you drill into a specific issue in a report.



And if you need to look at UA and GA4 data side by side, go back to the start of the article and keep in mind the differences in metrics and calculations. Opinions expressed in this article are those of the guest author and not necessarily Search Engine Land. Staff authors are listed here. So, how do we get UA-like findings out of Google Analytics 4 (GA4)? We asked Russell Ketchum, product director of Google Analytics, in the first of a three-part series of conversations with him.