Blog

Samplation has often been a pain for Universal Analytics users. With the move to Google Analytics 4, the quotas for queries have been greatly increased. In GA4, the quota limit for event-level queries is 10 million events for standard Google Analytics properties and up to 1 billion events for Google Analytics 360 properties. This enables GA4 users to report on large timeframes and multiple dimensions without any sampling.

Roll-Up Property is a single property which aggregates data from multiple source properties. This might be useful for businesses that have multiple websites for different regions. In this case, they can safely track each of the regional sites into a separate Google Analytics property and also have a separate roll-up property to analyze a larger amount of data than you have in single-site properties.

Here is how the Google Analytics account structure would look like in case of using the roll-up property:

Goals and funnels reports are extremely useful for marketers. These reports help to evaluate traffic sources and campaigns, to analyze the user flow through the funnel before conversion, to find drop-off points and bottlenecks in the funnel. Google Analytics is tricky when it comes to funnel configuration.

Unlike many other analytics systems Google Analytics processes the goal and funnel data. It means that you cannot build a funnel report on historical data. you need to configure your goals and funnels first and only after this Google Analytics will start collecting data about funnel flow and conversions.

Google Analytics presents their data sampling technology is a way to present meaningful data on large data subsets (here is official documentation on this topic https://support.google.com/analytics/answer/2637192?hl=en). However most of the medium-sized online businesses worry a lot when they get a notification that the report is built on 70% of their data and not 100%.

And they worry not without reason especially in case they analyze some small segments of their audience.

Two most popular opportunities to get Google Analytics data in BigQuery for non-premium Google Analytics users.

Google Tag Manager is a great tool that has a lot of opportunities for event tracking. If you are not familiar with this tool and have not used it before start with reading this article about basic concepts of Google Tag Manager. In this article, I will explain how to configure event tracking using Google Tag Manager easily.

An event can be sent to Google Analytics with any trigger. The most common case for event tracking is a click on some button or link.

Discrepancy in data especially in the revenue and transaction number is often an issue for the ecommerce sites that use Shopify. Shopify has a document where they list some possible reasons of this discrepancy https://help.shopify.com/en/manual/reports-and-analytics/discrepancies. However these explanations are not very helpful because they do not contain any practical advice on how this can be fixed.

Video tracking for Youtube videos can easily be configured with build-in Google Tag Manager triggers. But other video players are not currently supported. Fortunatly most of the popular video players have JavaScript API which allows to create listeners and push data about video player events to dataLayer.

JWPlayer Tracking

JWPlayer has very detailed API reference here https://developer.jwplayer.com/jw-player/docs/developer-guide/api/javascript_api_introduction/