Google Analytics

Acquisition Reports in Google Analytics 4

Guideline: How to use Acquisition Reports in Google Analytics 4

Google Analytics displays the origin of your visitors and this is most frequently used and valued feature of it. Traffic acquisition reports are used to make decisions about future marketing campaigns. Despite the fact that Google Analytics GA4 can display this information, a few interface elements may be more difficult to understand than in Universal Analytics.  Because of that, I choose to write a blog post that will guide you about using these reports in GA4.  The importance of acquisition reports Here are some suggestions if someone is unsure what accomplishments an individual can make with these acquisition reports. Find the top performers: If you own an online business, the sources that provide the top sales or revenue and email subscribers will be the top performer. You may try to find out where the users are coming from and then extend that achievement to another marketing medium. Find the weak points: You can concentrate on the points where your marketing strategies are failing through this report and utilize the comparison feature for the worst and best performers. It might make it easier to spot problems that need to be rectified.  For instance, you can determine the traffic sources which receive more than 10,000 monthly visits yet have low conversion rates. Traffic sources with high traffic but low engagement rates are another case of a weak spot, it may be a sign that the landing website or page did not live up to the expectations of the visitors. Evaluate your targeted campaigns: This report will also indicate the performance of marketing campaigns and add specific parameters to marketing campaigns by using UTM parameters. The results are shown in these acquisition reports after GA4 gathers the information. For instance, which advertising strategy/ campaign brought the bulk of leads or visits for the company?  Acquisition Report Overview Reports are found by selecting Reports > Acquisition. There are three choices by default which include overview, user, and traffic acquisition. Overview shows the traffic to your website. It is a dashboard that displays site users and conversion rates and several links are available there that open more detailed reports. Additional cards will appear in the overview of your GA4 property connected to Google Ads. User Acquisition shows how many visitors visit the website, whereas Traffic Acquisition displays new and returning visitors.  How to Navigate Acquisition reports? Click on Traffic acquisition. A primary dimension can be modified and look for more detailed information. You can also click the Plus icon to add the secondary dimension, which allows you to see more information.  For instance, Traffic Acquisition reports show the top-performing campaigns. Let us assume that the top performer here refers to who “brings out the enormous conversions”. Choose “Session campaign” from a primary dimension’s drop-down table. To view how well each campaign performed and generate conversions, scroll horizontally now. You can choose a specific conversion event title for more precision.  You can modify the report if any metric is not helpful. Click on Session source/medium before selecting the Plus symbol if you desire to look at the source/medium as well as the campaign together, click on Session campaign from the menu.  And that is it! You can see all campaigns along with their performance now. At the top of a report table, there is a search function that you can use. It searches for matches or similar data in the top two columns. Here is an example of how to view all the referral campaigns, I simply typed email into the search field while Session source/medium encounter as the primary and session campaign as the secondary dimension. All rows containing the word “referral” were matched by this. Related :  Segment vs Google Tag Manager 7 Tag Managements Solutions You Should Consider Default channel grouping These are the rule-based classification of traffic sources and it identifies the right source. It has to do with the way Google classifies different sources of traffic into bigger groups. For instance, Google-recognized search engines’ traffic is included in organic search. Unassigned will be shown if you own any traffic sources which is not included in any groupings. The difference among User & Traffic Acquisition reports The first source that sent a visitor to a website is the main topic of the user acquisition report. The recent or latest traffic source which brings the visitor landed to a website is the main emphasis of the traffic acquisition report.   User acquisition employs first-click, and the traffic acquisition report utilizes last-click attribution if you are known to attribution modeling.   Because of this, you will see that User acquisition dimensions begin with the First user, whereas Traffic acquisition starts with a session when you look at the dimension names in those reports. Let us illustrate the differences between User and Traffic acquisition reports. Think about the visitor who visits the website via Google Search, signed up for the newsletter, and returned the following day via email campaign.  Image By: Analytics Mania There are 2 sessions of similar users in total and the reports will present various information. User acquisition will feature each session to the Google (As Google was the foremost source or medium used by the user) According to Session Acquisition, the first session will be credited to Google, whereas the second session to Email (As Traffic acquisition is concerned with the source of traffic of every session independently).   The traffic acquisition report is a similar thing in GA4 if an individual is seeking a substitute for the Universal Analytics Source report. Do not utilize Source, Medium, and Campaign There are three different types of traffic source dimensions in Google Analytics 4 which includes The one with the prefix “First user”   And the one that starts with “Session”   The other ones, such as Session, Medium, and Campaign, etc. If you have previously used GA3, this may be puzzling, and if you wish to see the sources, media, or any campaigns of “session” then you must utilize dimensions that begin with the term Sessions. Use of Source, Medium, Session, Campaign, or any other

Send Ecommerce data to GA4

Send Ecommerce Data to GA4

Sending and sharing Ecommerce data is a new and important feature of GA4. Setting up Google Analytics 4 for eCommerce might seem tricky, but it’s essential for valuable insights. Unlike an automatic data collector, you need to configure it for your reports. The benefits are significant. GA4 eCommerce data is a game-changer. It shows how customers engage with your products. It offers insights to enhance their shopping experience. It highlights what drives conversions and guides you for a better marketing strategy. Need a simple guide? This article’s got you covered. We’ll look through the steps to set up GA4 eCommerce and explore the perks of tracking eCommerce data for your business. Let’s get started! Enabling eCommerce tracking in Google Analytics 4 Follow the steps given below to enable eCommerce tracking in GA4. Make sure your website has features like product pages, checkout pages, shopping carts, and buttons for eCommerce data collection. Make sure you have both a Google Analytics account and a Google Analytics 4 account. If not, create a new one. Choose a method for eCommerce analytics data collection: either (gtag.js) Global Site Tag or (GTM) Google Tag Manager. These methods help set up tags to send eCommerce data from the app or website to your GA4 property. If you’re unsure, learn the differences between gtag.js and Google Tag Manager. GTM Vs. gtag.js Google Tag Manager (GTM) and Global Site Tag (gtag.js) are two methods for deploying tags in Google Analytics, each with its unique approach. Google Tag Manager is a user-friendly web-based system that simplifies updating Google and third-party tags in your apps or websites without extensive coding. It also offers collaboration features and version control. In contrast, Global Site Tag (gtag.js) is the JavaScript framework that allows you to directly add tags to your web pages or mobile apps. Unlike Google Tag Manager, gtag.js enables continuous use of JavaScript code to send data to Google Analytics. We’ll focus on using GA4 with Tag Manager as we consider it a better option. Tag Manager is compatible with various tracking tools, is user-friendly, and offers more functionalities. Set up GA4 eCommerce using GTM Since Tag Manager is user-friendly, efficient, and secure, it’s the preferred choice. Using GTM can minimize errors, enhance tag deployment, and unlock additional features through a simple web interface. Now, let’s look at the steps to set up GA4 with GTM: Installing GTM on your Web Pages or Apps To add Tag Manager to your website, insert a small code snippet on the web pages. This code lets your site interact with Google Analytics and Google Tag servers. The Google Analytics 4 configuration tag code manages GA4 tag settings, configures cookies, and transmits automatically collected & improved measurement events. Utilizing Tag Manager on your mobile apps lets you track user interactions with your eCommerce products and app. It also lets you make app adjustments without rebuilding and resubmitting codes to app stores. How to install a GTM container on the eCommerce site? To set up GTM containers on your eCommerce site, you’ll need access to your mobile code or website. Follow these steps: In GTM, go to the Workspace. Click on the container ID (formatted as GTM-XXXXXX) on the right side of the Workspace tab. Clicking on this ID will open the Install Tag Manager box. Follow the guidance in an Install Tag Manager box: Copy & paste the provided code snippets onto the web pages. Specifically, insert the copied <script> code into the <head> of the web page HTML, and place <noscript> code right after a <body> tag. Switching to GTM If you previously used Global Site Tags for eCommerce tracking and are shifting to GTM, it’s advisable to migrate the majority, if not all, of your existing tags to GTM. This ensures a seamless transition and enables efficient management of your tracking configurations within Google Tag Manager. Understanding the eCommerce interactions to track on the app or site Understanding eCommerce interactions on your website or app involves monitoring user actions related to your products or services. Key events to track include  Viewing products Selecting items Cart additions/removals Checkout initiation Promotions viewed  Promotion Applied Purchases Refund requests Google Analytics (GA4) defines events in two categories:  Automatically collected and manually set events. Manually set events comprise recommended (predefined by Google Analytics) and custom events (user-defined for specific analysis). Given that most eCommerce events are recommended, the focus shifts to collecting these using Google Tag Manager. This targeted approach ensures you track the essential actions that matter for insightful eCommerce analysis. Setting up GA4 eCommerce events with the GTM Once Google Tag Manager is installed on your website, configure Google Analytics 4 eCommerce events within the Tag Manager by adding the right triggers and tags. Recommended eCommerce events have predefined names and parameters. They enable detailed measurements of user interaction.  GTM represents services or products as an array of products within eCommerce events, They accommodate prescribed and around 27 custom parameters. Additionally, you can make collections of the item arrays, allowing around 200 elements for comprehensive eCommerce tracking. Related :  Segment vs Google Tag Manager 7 Tag Managements Solutions You Should Consider Steps for creating and configuring Google Analytics 4 eCommerce event tags To initiate Google Analytics 4 eCommerce events in GTM, start by configuring a GA4 Event tag. This tag empowers you to establish tailored rules for collecting precise data from your app or site. Create custom macros to allow GTM to dynamically extract data from the product pages, including prices and item names. Once set up, GTM containers on your website transmit this data to the Tag Manager. Here are the steps to create and configure a new GA4 eCommerce event tag in Google Tag Manager: In GTM, click on “Tags” in the side menu, then select “New.” Name your event in the New Tag box, e.g., “purchase.” Choose “Google Analytics: GA4 Event” as the tag type. Set up new eCommerce Data Layer variables. Navigate to “Variables,” click “New” under the User-Defined Variables, and

GA4-vs-GA4-360

Google Analytics 4 vs. Google Analytics 360 Explained

Two Different Versions of Google Analytics 4 GA4 is offered in two different versions: GA4 Standard & GA4 360. The GA4 360 & GA4 standard both have the same user interface. Image Source: Optimize Smart The free form of a GA4 property is referred to by a GA4 standard. However, The GA4 property’s paid version is referred to as 360. Pricing & Billing of GA4 360 One particular offering from the platform of Google Marketing is GA4 360, the subscription service for which an individual must pay a monthly charge. With the properties of GA4 360, the charges will be according to the chargeable hit volume, and that has a chargeable sum for other products of 360 you utilize. Through a Google Marketing account, you can control invoicing and keep track of chargeable hit volume. Prime Differences Among GA4 360 & GA4 Standard 1. Free versus Paid The standard or free variant of the Google Analytics 4 property is referred to as a GA4 standard. GA4 360, on the other hand, involves the paid/premium edition of the Google Analytics 4 property.  In short, It costs nothing to utilize GA4 Standard. In contrast, GA4 360 isn’t. 2. Accuracy & Data Processing Contrary to GA4 360, one cannot depend upon Google Analytics 4 standard property for high accuracy and a vast amount of data processing. This is due to the increased data limits for the data processing and collection that come with the GA4 360 subscription as compared to a GA4 standard.  In this case, if a website receives more than one million visitors per month, then GA4 360 is the better option for you. 3. Analytics at Enterprise-level In contrast to a GA4 standard, a GA4 360 is mainly intended for big enterprises. The subscription of GA4 360 offers enterprise standard technical assistance & service-level contract for data retention, data collection, data reporting, BigQuery export, and attribution. 4. Technical Support The GA4 360 membership includes a devoted account manager & support personnel that can assist you with any questions you may have about data reporting and data collection. But, if you utilize a GA4 standard, you must make use of the community forums or self-help centre. You are all by yourself. 5. Accessibility Every person or organization can immediately access and use a Google Analytics 4 standard property. Nevertheless, you must first speak with an enterprise sales spokesperson or contact a sales partner of Google to access and use a Google Analytics 4 360 property. Moreover, the estimated annual cost of GA4 360 is around $ 150k or higher. Thus, most people cannot afford a GA4 360 membership. Explore Our Latest Guides: How to set up Shopify Google Analytics tracking? What To Look For In A Google Analytics Agency? Want to learn more About Conversion Tracking? 6. Legal Requirements You would have to sign the GA4 property’s 360 contracts with the purpose to utilise GA4 360. You can upgrade the GA4 standard to a GA4 360 property once the contract has been signed. You can utilize the Google Analytics 4 standard property without signing any agreements. 7. Data limits In comparison to GA4 Standard, GA4 360 offers higher restrictions for data reporting collection, retention, and BigQuery export. One of the major advantages of using GA4 360 is data limits. 8. Data Freshness A GA4 360 offers better data freshness than a GA4 standard. By using GA4 360, you can access ongoing intraday data through the API and user interface. Usually, the data is available an hour after it was collected.  Data freshness determines the total time GA4 takes to gather and process the data of an event from a website or application & then allow event data accessible through the API or user interface. If the procedure is completed in 1 hour, then the data freshness is considered as 1 hour. As opposed to a GA4 standard, data freshness is ensured after the subscription of GA4 360. 9. Event Parameters This is a piece of additional information or data related to the GA4 event which is sent with the event. For instance, for the “page_view” GA4 event name, the few possible event parameters are given below; page_location Source page_title  Medium page_referrer You are allowed to send about 25 parameters for each event while using the Google Analytics 4 standard property. But, you may send around 100 parameters for each event, if you are utilizing the Google Analytics 4 360 property. As a result, using GA4 360 allows you to send event additional information 10. Event-Scoped Custom Dimensions The event parameter in terms of GA4 is the custom dimension.  Utilize the custom dimension if you wish to determine the user characteristic that is unmeasurable by any other default dimension. For instance, you could design your personal dimension to keep track of client IDs. Two types of custom dimensions exist: 1. Event-Scoped The event-scoped dimension is the custom dimension whose value is sent and calculated for every event. 2. User-scoped The term “event-scoped custom dimension” refers to the custom dimension which has the “event” scope. In the Google Analytics 4 standard property, you are allowed to create around 50 of these custom dimensions, Google Analytics 4 360 property allows you to create around 125 of these custom dimensions. Related :  Segment vs Google Tag Manager 7 Tag Managements Solutions You Should Consider 11. Event-Scoped Custom Metrics The event parameter in terms of GA4 is the custom metric.  Utilize the custom metric if you wish to determine the dimension characteristic that is unmeasurable by any other default metric. You could, for instance, develop your metrics to keep track of the total number of phone calls the traffic source generates. A custom metric’s value is computed and transmitted for every event in GA4. The custom metric, in other terms, has the “event” scope. Because of this, the GA4 custom metric is also known as the “event-scoped custom metric” In the Google Analytics 4 standard property, you are allowed to create around 50 of these

Client vs Server-Side Tracking

Client vs Server-Side Tracking: What Is & Its Difference

Although some data is available on the client-side only, but server side also has many benefits. The two methods for gathering and delivering data are client-side & server-side, although each method has its own advantages and disadvantages. The primary difference between client and server-side tracking is that a client-side sends requests to retrieve webpages or files, and the server responds to these requests. As a result, the client represents the browser, device, or web application user interface that is used for browsing (like Google Chrome browser on a personal computer or mobile device). The server side is the source from where the requested information was retrieved. What are Server-side and Client-side Tracking? Server-side Tracking (also known as Cloud Delivery) When the tag or pixel sends data to the web server (either another type of server), the web server transmits that data to the target system or server. This process is referred to as server-side events or data management, also known as cloud delivery. An analytics service, personalization tool, marketing automation platform, or another kind of execution system may use this data. The event gateway system is what you use when you combine many tags or pixels rather than using one pixel or tag per destination system. (It is also called API Hub) Here, all the data is gathered, and the central system subsequently transmits the data to third-party or outside vendors. By sending a single data stream to the cloud-based repository, this specific action simplifies the data collecting and delivery procedure before providing the information to vendors.  Client-side Tracking The most prevalent method for sending data from web pages to clients-side is using tags. This kind of tracking entails the browser of the user (client) for sending information and data directly to the server. Tag management is the gathering and sharing of data from a website with vendors from marketing technology. Explore Our Latest Guides: How to set up Shopify Google Analytics tracking? What To Look For In A Google Analytics Agency? Want to learn more About Conversion Tracking? Benefits of Server-side tracking   Reliability, Control, and Accuracy  Due to millions of scenarios and devices involved in client-side tracking, there is a higher chance that anything could happen that would affect data transmission. This tracking is typically more reliable as the data management scope is reduced & the organization can have more controlled transmission.  The server-side tracking is less likely to cause data problems because of client-side problems such as ad blockers or interrupted connections being installed. It is difficult to keep the metric consistent across platforms in client-side events.  Performance of the Device and Application  Server-side tracking has the benefit of taking away the processing load from the device of the client and moving it to the cloud. As a result, the client device has to do less work, which can improve the performance of the application and device. The faster application consumes low battery, improves the customer experience & can significantly improve the conversion rates. Related :  Segment vs Google Tag Manager 7 Tag Managements Solutions You Should Consider Benefits of Client-side Tracking The Contextual Data  The benefit of client-side tracking is that it occurs directly on the device of users, enabling access to user-specific information including cookies, user agents, URL parameters, IP addresses, and referrers. You can collect and track all the information about clients and use it for other actions. Cookies and other data are frequently utilized for ad targeting. Location data is ideal to use for personalization in many applications. Moreover, user agents and URL parameters are frequently used in consumer engagement and marketing campaign analysis. The Certona, Optimzely, or Google Publisher Tag are a few examples of specialized client-side tags that must run in a browser to collect the contextual data to provide visitors the display ads, personalized experiences, or dynamic content.    Easy Implementation, Knowledge/Expertise availability This tracking has another advantage. It is simple and easy to install. Many vendors offer a piece of code that can be implemented by simply copying & pasting. For many past years, Client-side tags have been standard practice in the industry, making it a routine task. Cheaper and Lower cost Data transmission expenses of client-side events are often cheaper and lower cost. The expenses of server-side transmission are higher because this transmission uses cloud resources from third-party cookies instead of the device of the target user. You may also like to read our latest post on: Setup GA4 on Shopify Data Layer Approach: Key for unlocking the advantages of Server/Client Tracking Optimization Tracking and providing data swiftly on the client side or server side is difficult. Without taking measures to establish the data foundation makes the data access and defining process easier. Establishing the modular & neutral vendor data foundation allows the maximum advantages of optimizing the data management balance of client-server. Involvz uses the data layer technique (coupled with a convenient management interface) for establishing the taxonomy of the data which can be retrieved from any area or location where customer engagement takes place. This makes using data much easier, whether it’s done on client-side or server-side.  What is the best and Right Solution? Every situation does not warrant or allow the server side (cloud delivery) for collecting and deliver data. Sometimes, the client-side tags seem to be the best solution. It is crucial to have capabilities that can accommodate emerging and traditional data management techniques on the same platform.  When the client-side tracking falls short, the server-side rescues and fills the gaps. Server-side tracking is a secure and reliable way to track events. This property makes server-side tracking an exceptional source to track sensitive data and revenues. Want us to do all this hassle. Schedule a Call with Expert at Involvz for a fruitful decision Read Our Latest Guides on GA4: How to Implement GTM Container on iframe Self Referral Google Analytics 4  Linking a Google Ads Account To Google Analytics?

Data Streams in GA4

Understanding Data Streams in Google Analytics 4 in 2023

Understanding Data Streams Setting Process & Benefits Understanding website traffic and user engagement has become easy with Google Analytics. It is an effective analytics tool offered by Google that allows businesses to track their website and app traffic, user engagement, and behavior across these mediums(website+app). Google Analytics 4 or GA4 is the new version of the popular analytics tool that provides businesses access to new and advanced features enabling them to understand and analyze user data in a better way.  GA4 is very different from Universal Analytics. One primary change in GA4 is the introduction of Data Streams which has replaced the previous feature of “views” in Universal Analytics. In order to get most of GA4, you need to familiarize yourself with all its new features and Data Streams is one of them. That is why we have come up with this comprehensive article to let you better understand Data Streams, how they work, and how a company can use data streams to gain useful insights into its website or app visitors. What Are Data Streams? In Google Analytics, a data stream is a collection of data that comes from a particular source, such as a website or mobile app. Each data stream is associated with a unique tracking ID, which allows businesses to keep track of the data coming from each source. Data streams can include information about user behavior, such as page views, clicks, and conversions, as well as information about the devices and browsers used to access the website or app. Data streams are a key component of GA4, and they replace the previous concept of “views” in Universal Analytics. In Universal Analytics, businesses created different views of their website data to help them analyze traffic from different sources or to apply different filters to the data. With GA4, businesses can still apply filters to their data, but they do so using data streams rather than views. How To Setup Data Streams In GA4? To create a data stream in GA4, you need to perform the following steps one by one: First, you need to create a property, which will be the top-level container for your website or app data. You can create multiple data streams within each property to track different data sources. For example, a company can create separate data streams for its website, mobile app, and social media channels. Once your stream is set up, you’ll need to add the tracking code to your website or app.  Note: A tracking code is a small piece of JavaScript that collects data from your browser or device and sends it to Google Analytics. Tracking codes are unique to each data stream, so companies should ensure they are using the correct code for each data source they track.             4. Installing a tracking code allows a company to collect data from its website or app. Note: GA4 tracks a wide range of user behavior such as page views, clicks, conversions, and demographic and geographic information about users. The company can use this data to understand how users interact with her website or app and identify areas for improvement.  May also like to read our latest post on Setup GA4 on Shopify What Do You Get By Setting Up Data Streams? Single Property For Data Tracking There are several benefits to using data streams in GA4. First and foremost, data streams allow businesses to track data from multiple sources in a single property. This means that businesses can get a more complete picture of how users are interacting with their brand across different channels, without having to switch between different views or properties. Easy Filter Application Data streams also make it easier for businesses to apply filters to their data. In Universal Analytics, businesses created different views to apply filters to their data, which could be time-consuming and complex. With data streams, businesses can apply filters directly to the data they want to analyze, without having to create separate views for each set of filters. User Behavior Tracking Another benefit of data streams is that they allow businesses to track user behavior across different devices and platforms. With more and more users accessing websites and apps from multiple devices, it’s important for businesses to be able to track user behavior across these different platforms. Data streams make it easy to do this, as businesses can track data from mobile apps, websites, and other sources all in one place. Related :  Segment vs Google Tag Manager 7 Tag Managements Solutions You Should Consider Enhanced Features In Data Streams One of the great things about Google Analytics 4 is that it’s simplified in some ways, and you have a few things automatically set up for you. For web data streams, Analytics has already set up tracking for a few key metrics within each stream’s enhanced measurements. This is great news because Google has pre-selected some key areas, and you don’t have to do anything to get Analytics to start tracking. For the web data stream you set up in a property, you’ll automatically track page views, scrolls, file downloads, video plays, site search, and outbound link clicks. Read also: How to Link BigQuery and Google Analytics 4 Tips for Using Data Streams Effectively To get the most out of data streams in GA4, businesses should follow some best practices.  Define the data streams Decide what information you want to gather and how you want to organize this information before implementing the data streams. This will enable you to produce a coherent and useful data stream. Use custom events To track particular actions that take place on your website or app, GA4 lets you create custom events. Track user actions by using custom events, for example, form submissions or purchases. Check Data Quality In GA4, data quality is very important. To make sure the data you’re collecting is accurate and dependable, implement data quality checks. This may involve user input verification and a gap or

Google-analytics-prohibited-data

What Data Does Google Analytics Prohibit Collecting?

Google Analytics has a strict policy against collecting personally identifiable information (PII). They prohibit the collection of any data that could be used to identify a specific individual. This includes details like email addresses, full names, home addresses, social security numbers, credit card information, and similar sensitive data. In the following sections, we’ll delve into several aspects: The significance of prohibiting personally identifiable information (PII) and why it’s more important now! Google’s definition of PII and what falls outside of this category! The consequences of collecting (PII) unintentionally! Strategies to prevent the collection of Personal Identifiable Information (PII)! Get help to avoid any issues related to PII! The importance of prohibiting personally identifiable information (PII) and why it’s more important now! Privacy regulations have reached a high level now. It not only impacts Google Analytics but various aspects of data collection and management. Laws like the GDPR in Europe or the Ecommerce directive need user consent for collecting data. Google had already established strict regulations in this matter. Using PII without permission can lead to legal trouble and harm your reputation. Users expect their data to be handled responsibly. By prioritizing PII protection, you not only comply with the law but also build trust with your audience. It’s about respecting privacy and ensuring data security, it is essential in this age of heightened data awareness. Google’s definition of PII and what falls outside of this category! Google identifies specific personal information categories as off-limits, like names, addresses, contact details, birth dates, fingerprints, social security numbers, passport numbers, and sensitive ID numbers. However, data meeting Google’s guidelines, such as pseudonymous cookies and ad IDs, might be accepted. While Google permits some data, it might clash with regulations like GDPR or CCPA. For instance, IP addresses, accepted by Google are considered PII under GDPR, showing differences in standards between Google Analytics and legal privacy regulations. The consequences of collecting (PII) unintentionally! Collecting personally identifiable information (PII) unintentionally can lead to serious consequences. It violates Google’s terms of service. Google has the authority to deactivate your Google Analytics account if it detects such prohibited data. This information might sneak into unexpected places, like URLs, where email addresses end up in your Google Analytics. It risks the deactivation of the account. Form submissions could also transfer personal data unintentionally, causing issues within your analytics. Before using Google Analytics, thorough checks and precautions are necessary to ensure a secure and compliant setup. Strategies to prevent the collection of Personal Identifiable Information (PII)! Here are strategies to prevent the collection of Personally Identifiable Information (PII): Data Limitation: Use tools like Google Tag Manager to set up filters that prevent the transmission of sensitive data to Google Analytics. Filter Setup in Google Analytics: Apply filters in your Google Analytics settings to exclude information that’s not allowed. It ensures compliance. User Deletion Option: As a last resort, use Google Analytics’ specific user identifier for deleting individuals to remove potential PII. However, be cautious and identify problematic users before doing so. Use of analytics.js Code: Use this code before data reaches Google Analytics to remove personally identifiable information automatically. It’s an easy process to protect against any personal data in URLs. Import the data: Importing data into Google Analytics requires strict adherence to guidelines. The data you import should be free of any Personally Identifiable Information (PII). Moreover, it’s essential to ensure that this data doesn’t include device identification, such as unique identifiers from mobile phones. Data Location: When dealing with data location, make sure it doesn’t contain GPS information, as Google Analytics considers this as potentially identifying. Avoid including “fine-grained location” details to comply with Google Analytics’ policies regarding location data. These strategies can significantly reduce the risk of inadvertently collecting PII and ensure compliance with privacy regulations. Get help to avoid any issues related to PII! Get help to avoid issues associated with Personally Identifiable Information (PII). Consulting with experts, like Involvz- data analytics professionals, can provide invaluable guidance to ensure compliance with data privacy regulations. Our expertise can help in setting up proper filters, implementing necessary measures, and tailoring solutions specific to your situation to prevent inadvertent collection of PII. Getting professional help is a proactive step toward avoiding complications and ensuring a smooth, compliant use of tools like Google Analytics. Final Words Protecting Personally Identifiable Information (PII) in data analytics is important in today’s privacy-conscious world. Google Analytics strictly prohibits the collection of PII, which includes a wide range of personal data. With privacy regulations like GDPR and CCPA, compliance is not only a legal requirement but also a trust-building measure with your audience. To avoid the accidental collection of PII, it’s crucial to understand what’s allowed and what’s not. Apply strategies like data limitation, proper filters, user deletion options, and code implementation. Importing data and handling location information

Link BigQuery with GA4

How to Link BigQuery and Google Analytics 4

Linking BigQuery and Google Analytics 4 (GA4) is like connecting two powerful tools to help you make sense of your website or app data. BigQuery is like a super-smart data storage and analysis tool, while GA4 is fantastic at tracking what’s happening on your website or app. When you link them together, it’s like giving GA4 the ability to send all the data it collects to BigQuery. So, you can easily analyze, play with, and learn from all that data using BigQuery’s magic. Imagine it as a teamwork between your data trackers and data analysts. GA4 collects the data, and BigQuery helps you dig deep to find valuable insights. This connection can be super handy for businesses, marketers, and anyone who wants to understand how people are using their online stuff.  So, let’s explore how you can make this teamwork happen! Advantages of Linking BigQuery and GA4: Enabling BigQuery linking for Google Analytics 4 (GA4) offers several benefits: Deeper Data Analysis: Access raw, granular data in BigQuery for more comprehensive and customized analysis. Advanced Queries: Perform complex SQL queries to extract specific insights and answer unique business questions. Data Integration: Combine GA4 data with other datasets, enabling holistic analysis and cross-channel insights. Real-time Data: Access near real-time GA4 data in BigQuery for timely decision-making. Custom Reporting: Access near real-time GA4 data in BigQuery for timely decision-making. Long-term Storage: Store GA4 data in BigQuery for extended periods, complying with data retention policies. Data Export Flexibility: Control what data gets exported to BigQuery, optimizing resource utilization. Cost Control: Manage costs more effectively by controlling the amount of data stored and processed. Historical Analysis: Analyze historical data beyond GA4’s data retention limits. Overall, enabling BigQuery linking enhances your ability to extract actionable insights and leverage data for strategic decision-making. Linking BigQuery and GA4: If you’re already using Google BigQuery for your data and you want to get data from Google Analytics 4, you can start sending that data to your BigQuery project. It’s a convenient way to combine and analyze your data in one place. 1. Prepare Your Google Cloud Project: Sign in to the Google Cloud Console. If you don’t have one, create a Google Cloud Project from the Google Cloud Console. 2. Enable BigQuery API: Go to the Google API Console project you made and click on “APIs & Services” in the menu on the side. After that, choose “Library.” In the search box, type “BigQuery API” and press Enter. Locate the “BigQuery API” in the search results and tap on it. Ensure that the BigQuery API is enabled, and then click on “Manage.” To add a service account to your Cloud project, tap on the “Create credentials” button located in the upper right corner. In the window that appears, choose “Application data” to create the Firebase service account. This account will be used for exporting GA4 data to BigQuery. Scroll down the screen, select “No, I’m not using them,” and then click “Next.” Enter “firebase-measurement@system.gserviceaccount.com” as the account name and click on “Create and continue.” Now, you can assign a role to this account. For example, you can give it the role of an “Editor.” In the third step, add the email addresses of the people who will use or manage this account, and then click “Done.” After that, you’ll see your new account in the list. Congratulations! You’ve successfully enabled and set up the BigQuery API. 3. Link BigQuery to the GA4 property Log in to your Google Analytics account. Make sure this account has owner access to your BigQuery project. Also, ensure it has edit access to your Google Analytics 4 property.  Now, head over to the “Admin” section. Choose the specific property you want to connect with BigQuery. Look in the “Property” column and click on “BigQuery Linking.“ Next, press the “Link” button Click Choose a BigQuery project to view the projects you have access to. To create a new BigQuery project, click Learn more. Now, choose the project you require, and then click “Confirm.” Pick a location. (If your project already sets up an Analytics dataset, you can’t change this.) Click “Next” and choose the data streams you want to send data from. If you want to include advertising data, mark the “Include advertising identifiers for mobile app streams” option. Decide if you want data to export “Daily,” “Streaming” (continuously), or both. Then, click “Submit.” That’s it! In about 24 hours, you’ll start seeing Google Analytics 4 data in your BigQuery project. Related :  Understanding Event Parameter in Google Analytics 4 Self Referral Google Analytics 4 Cost of Linking BigQuery and GA4 In Google Analytics Universal, linking with Google BigQuery was reserved for Google Analytics 360 enterprise users. However, in Google Analytics 4, data export is available for everyone at no cost. You only incur charges when you surpass the Google Cloud free tier limits, which are 1 TB of requests per month and 10 GB of data storage. Alternatively, you can utilize the BigQuery sandbox for free data export, but it comes with limitations. Data tables may expire after 60 days. If you decide to upgrade to a paid account before this expiration, be sure to adjust your table expiration settings to preserve your data. This way, you can manage costs effectively while enjoying the benefits of the integration. Final Words! We’ve explored the process of linking Google Analytics 4 (GA4) and Google BigQuery, a powerful integration that empowers businesses to harness the full potential of their data. By following the outlined steps, users can seamlessly connect GA4’s insightful data collection capabilities with BigQuery’s robust data warehousing and analysis tools. This integration offers numerous advantages, including the ability to conduct deeper data analysis, create customized reports, and perform cross-channel analytics. The cost aspect of this linkage is also clarified, emphasizing that data export from GA4 is free for all, with charges incurred only when surpassing Google Cloud’s free tier limits. In essence, the combination of GA4 and BigQuery enables data-driven decision-making, facilitates in-depth insights, and empowers organizations

Setting up Google Analytics 4 for Multiple Clients

Setting up Google Analytics 4 for Multiple Clients

Setting up Google Analytics 4 for multiple clients is a fundamental requirement for digital marketing agencies and web consultants seeking to provide comprehensive insights and data-driven strategies. This process allows you to effectively monitor and analyze website performance, tailor strategies, and make informed decisions for each client’s unique needs. In this guide, we will delve into the essential steps to efficiently set up Google Analytics 4 for multiple clients, ensuring data isolation, security, and the ability to extract meaningful insights for enhancing online presence and achieving business objectives. Whether you’re managing websites for diverse businesses or assisting multiple clients, this guide has you covered. Add Multiple GA Properties under a Single Account Managing multiple Google Analytics 4 (GA4) properties under one account can be a complex task, but it’s crucial for efficiently tracking and analyzing data for multiple websites or clients. 1. Add All Sites Under One Google Analytics 4 Account: Google allows you to add up to 50 properties to a single GA account. This approach simplifies account management, as you can access all your properties from a centralized location. Add the new property to your Google Analytics 4 accounts. 2. Create Various Views for Each Property: Once you’ve added multiple properties to your GA4 account, it’s essential to create separate views for each property. Views allow you to apply specific filters, goals, and settings tailored to the needs of each client or website. This ensures that data remains organized and relevant. 3. Add Every Website as a Unique Account: If you prefer more granular control over each website or client’s data, you can opt to create separate Google Analytics 4 accounts for each. However, this approach may lead to more complex account management, as you’ll need to switch between accounts to access data. 4. Set Up Rolling Reporting: Rolling reporting involves regularly exporting and storing GA data, ensuring that you have historical records accessible at any time. This is especially useful if you need to compare data across different time periods for various properties. 5. Add the Tracking Codes in Google Tag Manager: To simplify the process of adding tracking codes to websites, consider using Google Tag Manager (GTM). GTM allows you to manage all your tracking codes in one place, making it easier to deploy, modify, and maintain tags for multiple properties. 6. Use a Custom Dashboard: Custom dashboards in Google Analytics 4 provide a consolidated view of data from multiple properties. You can create custom widgets that display key metrics and insights for each client or website, enabling you to monitor performance at a glance. 7. Implement Cross-Domain Tracking: If your clients’ websites span multiple domains or subdomains, implementing cross-domain tracking is essential. This ensures that user interactions are accurately tracked across different domains, providing a holistic view of user behavior. 8. Block Known Bots Automatically: Google Analytics 4 can be susceptible to bot traffic, which can skew your data. To mitigate this, set up automated filters to exclude known bots from your reports. This ensures that your data remains accurate and relevant. Related :  Understanding Event Parameter in Google Analytics 4 Self Referral Google Analytics 4 Advantages of setting up Google Analytics 4 for Multiple Clients Here are some advantages of setting up Google Analytics 4 for multiple clients. Efficient Data Management: Managing multiple clients’ data in one Analytics account streamlines data collection and reporting, saving time and effort. Centralized Reporting: You can create custom dashboards and reports that provide an overview of all clients’ performance in one place, facilitating better insights. Cost Savings: Google Analytics 4 allows you to track up to 50 properties per account for free, reducing costs compared to maintaining separate accounts. Cross-Client Analysis: With a single account, it’s easier to identify trends and insights across multiple clients, helping you provide more valuable services. Consistency: You can apply standardized tracking configurations and goals, ensuring uniform data collection and meaningful comparisons. Enhanced Collaboration: Collaborate with clients more effectively by sharing insights and discussing strategies based on consolidated data. Data Integrity: Minimize the risk of data discrepancies and errors that can occur with multiple separate accounts. Scalability: As your client base grows, managing all of them from a single account becomes increasingly advantageous. Setting up Google Analytics 4 for multiple clients in a single account offers numerous advantages, ultimately leading to improved efficiency, cost-effectiveness, and better-informed decision-making. Disadvantages of setting up Google Analytics 4 for Multiple Clients Here are some disadvantages of setting up Google Analytics 4 for multiple clients. Data Segmentation Challenges: Managing data for multiple clients within a single Analytics account can be cumbersome. It becomes difficult to segment and isolate client-specific data effectively. Cross-Tracking Errors: Different client websites may use overlapping tracking codes, leading to inaccurate data and potential conflicts. Resource Intensiveness: Managing multiple clients’ accounts demands more time, resources, and expertise, potentially affecting efficiency. Performance Impact: Large volumes of data from multiple clients can impact Analytics account performance and slow down data processing. Client Conflicts: Competing interests and disputes among clients using a shared Analytics account can lead to conflicts and complications. Final Words! Managing multiple GA properties under one account requires careful planning and organization. While adding all sites to a single GA account is a common and efficient approach, creating separate views, using Google Tag Manager, and implementing custom dashboards can further enhance your ability to track and interpret data for each client or website. Regardless of the method you choose, maintaining a structured and well-documented approach is essential for successful multi-property management in Google Analytics 4. Related :  Segment vs Google Tag Manager 7 Tag Managements Solutions You Should Consider

GA4 via GTM Server Side Tracking

How to Setup GA4 via GTM Server Side Tracking Properly 2023

1. Understanding Server-Side Tracking: Setting up Google Analytics 4 (GA4) through Google Tag Manager (GTM) using server-side tracking offers enhanced data accuracy, privacy compliance, and flexibility. This method allows you to send data directly from your server to GA4, reducing reliance on client-side JavaScript tracking. Here’s a comprehensive guide on how to set up GA4 via GTM server-side tracking: Server-side tracking involves sending data directly from your server to GA4 servers, bypassing the need for client-side JavaScript. This enhances data accuracy and helps with privacy compliance, as sensitive data doesn’t leave the server. Requirements: A functioning Google Analytics 4 property. A Google Tag Manager account set up. Set Up a Server Container in GTM: Create a new container in GTM dedicated to server-side tracking. This container will hold tags, triggers, and variables specific to server-side tracking. 2. Configuring Server-side Google Tag Manager Container: Step 1: Go to the server-side container and find the ‘Tags’ section. Once there, click upon ‘New’. Step 2: Give tag a clear and descriptive name. After that, click upon ‘Tag configuration’. Step 3: On the right side, you’ll see an overlay. This overlay has the list of the tag templates.  We’ll pick ‘Google Analytics: GA4‘. Step 4: Time to add the GA measurement ID. You can locate this in your GA4 account by going to Admin, and then Data Stream. Step 5: Tap on ‘Triggering’. This is where we’ll create the trigger for the tag. Step 6: Tap the ‘+’ symbol to make the new trigger. Give your trigger a name that explains what it does. There are three trigger types available, We’ll be using the “Pageview” Step 7: Tap on ‘Trigger Type’. You can set up when the trigger happens by choosing ‘Some Pageviews’. Also You can create a ‘variable’, to describe when the trigger should happen. Or you can use variables that are already available. Step 8: For what we’re doing, we want to send data to GA4. So, we’ll choose a condition that says ‘Client name’ is the same as ‘GA4’. Step 9: Don’t forget to click ‘Save’. Now, let’s move on. Next, we’ll check and confirm if the server-side container is getting data from the client-side container & how it sends that data to Google Analytics. 3. Previewing and Debugging When setting up tracking in Google Tag Manager, it’s important to test things out before you go live. Preview and debugging help you ensure that your tags, triggers, and variables are working as expected. Previewing: Step 1: In your Google Tag Manager account, click on the “Preview” button. This lets you see how your tags work on your actual website without making them live. Step 2: A new window will appear with the blank summary. Step 3: Now, when you go to your website, you’ll see a special GTM panel that shows what tags are firing and what data is being sent. To check what exactly the tag did, go to the ‘Tags’ section in the preview. Find the tag named ‘GA4 – Server Side Tag’ (that’s what we called it). In the ‘Variables’ section, you’ll find a list of things being tracked and their values. The ‘Event Data’ part shows all the info collected and sent to the tool, like Google Analytics 4. This way, you can keep an eye on what’s being shared and how your tracking is working. Debugging: Step 1: In the GTM preview panel, you’ll be able to see which tags are triggering and what information they’re sending. Step 2: If things don’t seem right, you can use the debug panel to track down issues. Step 3: You can also check the browser’s console for any error messages related to your tags. Once you’re confident everything is working fine, you can publish your changes in GTM and start tracking data accurately. Real-Time Validation: When you’re setting up tracking using tools like Google Tag Manager and Google Analytics 4, it’s important to make sure everything is working correctly in real-time. This is called “real-time validation.” For it, go to your GA4 account tap on “Real-time” The page given below will appear. Setting up Google Analytics 4 events Here’s what you need to know before you start: You’ve already set up events for GA4 on your website using tags. Your website’s tags send data to a server-side container, not directly to GA4. Now, follow these steps to get your GA4 events by using a server-side container. Step 1: Go to the ‘Tags’ section in the server-side container and tap on ‘New’. Step 2: Name your tag so it makes sense and tap on ‘Tag Configuration’. Step 3: Now, choose the type of tag which is ‘Google Analytics: GA4’. Step 4: Put in your GA4 measurement ID and tap the ‘+’ sign next to the event name. From the options, choose the ‘Event Name’ variable. Tag configuration will appear like this. Step 6: Tap on the ‘Triggering’ button to make a trigger for our Google Analytics 4 events tag. Step 7:  Hit the ‘+’ sign to create a new trigger. Give the trigger a name that explains what it does. Step 8: Tap on ‘Some Events’, then pick ‘Event Name’ from the list that drops down. Step 9: From the second drop-down, select ‘Matches regex’. In the box where it says ‘Value’, type in “*”. Step 10: After setting everything up, save your settings and turn on the preview mode in the server-side tag manager. Now, go to your website and do some actions, like scrolling or submitting a form. In the picture below, you can see that the scroll and form submit events show up in the summary tag. And, right at the same time, the GA4 events tag is triggered too. Step 11: Click on the GA4 events tag and see what information it’s sending to GA4. Look, in the picture, the ‘GA4 Events’ tag got triggered, and it sent the ‘Event Name’ as ‘Form Submit’. Step 12: Next, go to your Google Analytics 4 console and click

UTM Tracking in WooCommerce

WooCommerce UTM Tracking – Step by Step Guide

WooCommerce is a widely used e-commerce platform that allows businesses to establish and oversee their online stores. To achieve efficient monitoring of marketing campaigns and gain insights into user behavior, incorporating UTM tracking becomes imperative. UTM (Urchin Tracking Module) parameters are special tags appended to URLs, offering valuable data on the source, medium, and campaign responsible for directing traffic to your website. In this comprehensive guide, we will take you through the step-by-step process of integrating UTM tracking into your WooCommerce store, enabling you to optimize marketing strategies and boost overall performance. Achieving this goal involves two primary components: Capturing UTM Parameters  Sending UTM tags within WooCommerce orders. Capturing UTM parameters  Capturing UTM parameters involves employing different approaches, such as using JavaScript code snippets on your website or leveraging tools like Google Tag Manager (GTM). GTM offers a convenient solution for capturing UTM parameters, particularly when you need to apply the same method across multiple websites without the ability to directly edit their code. By creating user-defined variables in GTM, you can efficiently gather and analyze UTM data, gaining valuable insights into your marketing efforts and obtaining a clearer understanding of your website traffic sources. GTM Variables To capture the UTM parameters effectively, we must set up specific user-defined variables in GTM. These variables should have the following exact names as provided. In cases where UTM parameters are not present, we’ll resort to utilizing the referrer, but only if it’s available and from an external website. The custom HTML tag will rely on these variables to function correctly, so it’s essential to maintain the specified names for seamless implementation. The following user-defined variables in Google Tag Manager serve specific purposes: “url – utm_source”: Capture the value of a utm_source parameter. “url – utm_medium”: Capture the value of a utm_medium parameter. “url – utm_campaign”: Capture the value of a utm_campaign parameter. “url – hostname”: Returns the website’s hostname and is employed to prevent sending the referrer information in cases of internal traffic(users navigating within your website).  “referrer – full”: Acts as a source when not even a single UTM parameter is available. Create a Custom HTML tag that Captures UTM Parameters. To track different marketing campaigns, create a unique HTML Tag with the UTM parameters.  We should develop a custom HTML tag that is responsible for capturing UTM parameters or a referrer (in case no UTM tags are present). Once captured, the data will be stored in the sessionStorage. Below, you’ll find the code snippet for implementation. <script> var source = sessionStorage.getItem(‘source’); if ({{url – utm_source}}) { source = {{url – utm_source}} + ‘ / ‘ + {{url – utm_medium}} + ‘ / ‘ + {{url – utm_campaign}}; sessionStorage.setItem(‘source’, source); } else if ((!source) || (source == ‘none’)) { if (({{referrer – full}}) && (!{{referrer – full}}.includes(‘{{url – hostname}}’))) { source = {{referrer – full}} + ‘ / referral’; sessionStorage.setItem(‘source’, source); } else { source = ‘none’; sessionStorage.setItem(‘source’, source); } } </script> For example, “cHTML – source to sessionStorage” is a customized tag but feel free to modify it as needed. Here’s how it should appear: The purpose of this GTM (Google Tag Manager) tag is to capture the UTM parameters and store them in the sessionStorage. Related : Segment VS Google Tag Manager If there are no UTM tags and no referrer, set the source as none. I set this default value to be able to tell apart cases when the code does not run correctly for some reason, in which case we expect the source to be empty (or undefined). The logic behind it is structured as follows: If UTM parameters are present, we will store the source using the values of utm_source/utm_medium/utm_campaign In the absence of UTM tags, and if a referrer is present there (indicating the visitor visits from the external website), we will save the source as “https://any-website.com/referring-page / referral”. If both UTM tags and referrer are not present, we will set source as “none.” This default value helps distinguish cases where the code doesn’t execute correctly, as we anticipate that the source will either be empty or undefined in such cases. Sending UTM Tags within WooCommerce Orders. With the UTM tags now saved in the session storage, the next step is to transfer this information to WooCommerce orders by creating a custom field. To achieve this, you’ll need to add a hidden field on the checkout page and populate it with the value of the UTM tags. By implementing this method, the UTM data will be captured in a hidden field during the customer checkout process. Once the order is completed, this information will be saved as a custom field linked to the specific order. As a result, you will be able to preserve the UTM details for each order, facilitating tracking and analysis purposes. Establish the Hidden field Within the WooCommerce Checkout Page For the purpose of adding a hidden field in a WooCommerce checkout page, use a code snippet instead of relying on plugins, as they might have been excessive for specific requirements. To implement the hidden field, simply insert the provided code snippet into your website. // Add a hidden field on the checkout page add_action(‘woocommerce_after_order_notes’, ‘checkout_source_field’); function checkout_source_field( $checkout ) { woocommerce_form_field( ‘my_source_field’, array( ‘type’ => ‘text’, ‘required’=> false, ‘placeholder’ => __(‘utm_source’), ), $checkout->get_value( ‘my_source_field’ )); } // Update the order meta with field value add_action(‘woocommerce_checkout_update_order_meta’, ‘checkout_source_field_update_order_meta’); function checkout_source_field_update_order_meta( $order_id ) { if ($_POST[‘my_source_field’]) update_post_meta( $order_id, ‘Source’, esc_attr($_POST[‘my_source_field’])); } If you choose to utilize the Code Snippets plugin, the process would appear like this: This will enable you to create a hidden field on the WooCommerce checkout page. Retrieve UTM Tags from WooCommerce Checkout field To proceed with GTM, you must create the tag that exclusively fires at the checkout page. This tag will be responsible for obtaining the UTM parameter values through session storage and subsequently setting them in a source field within the WooCommerce checkout page. Assuming your WordPress website’s checkout page web address is similar to this: “https://your-website.com/checkout/,” the

Scroll to Top