How is Meiro Events different from Google Analytics & Google Tag Manager
There are many tools today that can be used to track data and events. We want to track data and events because we want to understand our users better so that we can help cater to them better.
Google Analytics & Google Tag Manager
Google Analytics is the most popular website analytics tool: tracking data, storing it, and generating reports. It is free to use, but it does collect users' data to utilize it further.
Google Tag Manager is a free software by Google that allows you to manage various types of code (tags) deployed to your website.
Google Analytics has both front and back end features while Google Tag Manager is a tool that helps to manage & measure the performance of tags from Google Ads, Google Analytics, Floodlight, and 3rd parties. Google Tag Manager does not have any reporting or data storage capabilities. It is mostly useful with multiple trackers.
Learn more: about Google Analytics and Google Tag Manager.
Meiro Events
Meiro Events is the first layer of the Meiro CDP stack in reaction to the recent privacy changes. It is simply a JavaScript library used for collecting customer events from a website’s visitors.
Learn more: about the Meiro Events.
Google Analytics vs Meiro Events
So how different are they from each other and how do they work to track data on your website?
1. Types of data collected
Meiro Events |
Google Analytics |
Meiro Events is very specific and customizable to the client’s use case. In Meiro Events, it is possible to track
All the events sent by SDK may be enriched by additional data on the ME backend server:
Learn more: about which events you can track here. Example: You can collect data from any form with the Learn more: full list or |
Google Analytics tracks
Google Analytics collects events that
Reports available through Google Analytics contain mostly website traffic, devices used, etc.
Due to
Learn more: full list of Google Analytics |
2. Cookies
Meiro Events |
Google Analytics |
Meiro Events offers flexible, customizable deployment models. It is possible to deploy Meiro Events with user id as the 1st party cookie (either on the client's server or domain where the owner sets DNS). In addition, the expiration of the cookie is also longer, up to 2 years. (refer to the different browsers: here). |
Google Analytics assigns Google Client ID. Google Analytics collects events in the main Google domain. For this reason, Google Analytics ID is often set as a 3rd party cookie. Therefore, browsers can easily block any tracking events and the cookie expiration can be short (like 7 days for Safari), depending on the browser. Because data is sent to a different domain (Google) than the website, Google Analytics can be easily blocked. The script is fetched from Google public domain, so everyone knows its location hence it can be blocked easily. Google Analytics can also be set as a 1st party cookie, but via document.cookie on javascript. With document.cookie command, you can include any content and domain (can be on meiro.io fetching 3rd party data javascript, can be fetching data from Google Analytics via Google domain). This shows that with document.cookie, anyone can set a 1st party cookie on any website. But even though it is possible, javascript cookies are not as trustworthy compared to http cookies (used by Meiro) that are set by the server where the domain is configured and it is easy to determine if the server domain matches the website domain. That's why document.cookie expires after a few days on some browsers. |
3. Domains, Meiro Events vs Google Analytics
Meiro Events |
Google Analytics |
If you deploy Meiro Events on the client owned domain(same as tracked application - 1st party data):
|
Google Analytics can be blocked if added to the privacy blocker blocklist. If blockers are enabled, this will not allow Google Analytics to use tracking codes. |
4. The ID of the user and identity stitching in Meiro Events vs Google Analytics
|
|
|
|
5. Sessions and identity stitching in Meiro Events vs Google Analytics
Meiro Events |
Google Analytics |
The session is set with some initial event and it lasts for 30 minutes. Every user that visits a website receives a Session ID, every event sent to Meiro Events from the same users within the next 30 minutes has the same session ID. If there is an event that comes after 30 minutes, a new Session ID is generated. Through an identity stitching algorithm, Meiro may be able to assign two different sessions to one customer profile. |
A session expires 30 minutes (pageview, event, or transaction). Afterward, it will be considered as a new session. A session in Google Analytics is a group of interactions recorded when a user visits your website within a given period. Google Analytics session begins when a user visits a page on your site and ends after 30 minutes of inactivity or when the user leaves. So any activity after 30 minutes will be counted as a new session, assigned to a new user. |
6.5. Data sampling
Meiro Events |
Google Analytics |
Meiro Events does not sample data, so you get a complete picture of your data. |
The free version of Google Analytics begins sampling data for non-default reports that exceed 500,000 sessions; Google Analytics 360 for reports that exceed 100 million sessions. This means that analyzed is only a sample of your data, which does not say about the whole database. |
7.6. Real-time data
Meiro Events |
Google Analytics |
Meiro Events processes data almost in near real-time. |
For the free version of Google Analytics to get data, it takes up to a few hours to more than 1 day. For Google Analytics 360 (paid version) it can be approximately 4 hours. |