Google Analytics 4
The Google Analytics 4 connector extracts traffic and engagement metrics from your Google Analytics 4-enabled websites and apps and loads that data into your Qlik Sense or QlikView apps.
- Qlik Sense Desktop
- Qlik Sense Enterprise on Windows
This connector must be installed separately.
Ways to access your data
To access your data, follow these steps:
After installing Qlik Web Connectors, select the Google Analytics 4 connector from the Connectors list.
Select one of the available tables and click on Parameters.
Click on the Authenticate button. You will now be redirected to a Google login page where you authenticate by using your Google account credentials.
Once you have authenticated, copy the code to authenticate on Qlik Web Connectors
Loading data from tables
After you create the connection, use the tables to fetch your data. The table below outlines some of the use cases for some of the tables that are available.
|ListAccounts||Use this table to fetch all accounts accessible by the authenticated user.|
Use this table to fetch child properties for the specified parent. Get the account name from the ListAccounts table.
Use this table to fetch metadata for dimensions and metrics available in reporting methods. Get the property name from the ListProperties table.
Use this table to fetch a customized report of real-time event data for your property. Events appear in real-time reports seconds after they have been sent to Google Analytics. Real-time reports show events and usage data for the periods of time ranging from the present moment to 30 minutes ago (up to 60 minutes for Google Analytics 360 properties). Get the property name from the ListProperties table.
For more information, see Realtime Dimensions and Metrics.
Use this table to fetch a customized report of your Google Analytics event data. Reports contain statistics derived from data collected by the Google Analytics tracking code. The API returns the data as a table with columns for the requested dimensions and metrics. Metrics are individual measurements of user activity on your property, such as active users or event count. Dimensions break down metrics across some common criteria, such as country or event name. Get the property name from the ListProperties table.
For more information, see API Dimensions and Metrics.
Working with the Google API quota limits
For information about Google API quota limits, see Google Analytics 4 Quotas.
Reference - Google Analytics 4 developer documentation
Refer to the Google Analytics 4 developer documentation to learn more about the Google API.
You have exceeded the API limits that are imposed on the Qlik Web Connectors by the Google APIs.
To avoid API rate limit exhaustion, develop your app with the following in mind:
- Extract only the data you need.
- Reload one Google Analytics-based application at a time.
- Ensure that loops in your script that make API calls will not result in infinite loops.
You are receiving unexpected data or conflicting data
Differences in data can be due to a misinterpretation of the dimensions and metrics or due to the sampling used by Google Analytics.
Request data over smaller periods, for example, instead of requesting data for a month at a time, request data over a day or a week at a time.
Check that you also get the same numbers in the Google Query Explorer. The connector gets the data from the same system, so there should not be any differences.
Use the following procedures to identify and reconcile the differences:
Run exactly the same metrics in the connectors as on the platform.
Use the connector or the Query Explorer, and not your application, to check values by recreating the metric and looking at the data tab in QlikWeb Connectors.
Try to match the manual report to the connector, so if the connector gives you three columns of data, that is, date, pages visited and average time, then get the same report manually and compare the values.
Match the time scales. If the connector gives you each day's data for a month, but the manual report just gives you one figure for the whole month then values like averages will be affected.
Try a smaller time scale or data set as this will make it easier to identify where data is missing, so check numbers on a day by day basis.
Check the ranges coming back in the connector. If you select a date range, check that all those dates are in the data, that is, the first or last days are not missing.
If the values in the connector can be matched to the manual reports, but there is still a problem in the application, then you need to review your script, data model, expressions and objects, to check what you get in Qlik Web Connectors is the same as that fed into your application.