Hello There!

Lorem ipsum dolor sit amet, consectetur adipiscing elit,

Implementation User ID Google Analytics [Free User Guide]

user id implementation

user id implementation

In today’s world, people can interact with your business through multiple touch points, thanks to a large number of devices. This means their behavioral data is split into silos. 

Analytics is all about how your users behave. Do you ever think of how people use your website across devices? Are they starting a task using their computer but complete it using their mobile phone? Implementing User ID Google Analytics, you can answer questions like these with Google Analytics. Using User ID feature, one can accurately measure the behavior of users as they span across different devices. User ID enables a holistic approach to measuring user interactions such as attributing an interaction with a marketing campaign on one device to a conversion that is completed on another device.

De-Duplicate Your Users

User ID as a feature allows websites to use their own identifier in Google Analytics (an account sign in). When the data is processed in Google Analytics, it uses User ID to identify unique users across all platforms and de-duplicates users from multiple devices that have the same User ID. This result is a more accurate measurement of the actual number of users that engage with your business regardless of the platform they use to interact.

Multiple Touchpoints

Multiple Devices

Generate Better Insights

Google Analytics provides a separate view for User ID feature with special cross-device reports which are not available in other views. There are three types cross device reports:

  1. Device Overlap Report
  2. Device Paths Report
  3. Acquisition Device Report
1. Device Overlap Report

This report enables you to determine the combination of devices like desktop, mobile or tablet used by users to engage with your business.

Segment users by device type and compare important metrics like revenue and user transaction rate.

Implementing User ID Google Analytics

Device Overlap Report

2. Device Paths Report

This report is used to determine the order in which users used multiple devices to interact with your business and then convert.

This report is similar to ‘Conversion Paths’ in multi-channel funnel reports.

Measure users with user id

Devices Path Report

3. Acquisition Device Report

This report is used to determine whether or not a user converted from the acquisition device. Acquisition device is a device (desktop, mobile or tablet) through which a user was acquired for the first time. Using this report you can attribute an interaction with a marketing campaign on one device to a conversion completed on another device.

User ID Implementation

Acquisition Device Report

Other Significant Benefits of Implementing User ID Google Analytics:
  • Unify user sessions across devices without asking for login.
  • Compare segments of logged in users vs not logged in users and discover how different these two engage with your content.
  • Import User information from other sources into Google Analytics.
  • Find relation between acquisition, engagement and conversions.
Concluding Thoughts

Implementing User ID Google Analytics feature mitigates issues like cross-device usage and session unification. Although, tracking still relies on cookies and Javascript. These are susceptible to issues like deletion of cookies, disabling Javascript, using public devices etc. As with the data, you should focus on analyzing trends, changes, and patterns, rather than absolute numbers.

I hope this post will help you understand why User ID feature is such a popular thing and worth implementing it. In case of any queries or feedback, please feel free to leave a comment in the section below and we shall get back to you.

Also Read: Customize Google Analytics Campaign Timeout For Affiliates

Measure Multi-Channel Funnel Effectiveness with Funnel Reports

Measure Channel Effectiveness

Google AnalyticsDo you have an online presence for your business? Are you using digital marketing to generate business for you? If yes, then I am sure, what I will now share, would be of great value to your business. It is imperative for you to know the performance of each channel.

In Google Analytics, a channel means a group of different traffic sources with the same medium like organic, direct, paid search, social, etc.

Before we start getting insights from channel data, let me cover some prerequisites for proper tracking.

Prerequisites:

  1. All the campaigns are tagged with appropriate sources & medium
  2. The conversion metric that you are going to consider is accurately captured.
  3. All the payment gateways are excluded using Referral Exclusion List.
Multi-Channel Funnel (MCF) Reports from Google Analytics
1. Assisted Conversions:

Assisted Conversions: On one hand, for example, display channels play a dominant role in assisting conversions. Whereas, channels like direct or organic play a role in driving final conversions.

Channel Effectiveness for Marketing

Assisted Conversions Report

Assisting and Final Conversion role of a particular column can be obtained from the final column which is Assisted/Last Click ratio. Also, we can consider total Assisted Conversions for individual channels and look at the weightage for individual channels. This will give a broader picture of overall channel importance.

If,

Ratio > 1 à Channel is good in assisting
Ratio < 1 à Channel is good in driving final conversions
Ratio = 1 à Channel has an equal number of assisted and direct conversions

Here, the conversion number and conversion value should also be taken into consideration. We can see that DoubleClick Bid Manager (DBM) plays an extraordinary role in assisting. But, the conversion value is less compared to the other channels. Thus, even though DBM has a very high Assisted/Last Click ratio, its overall importance is not that high. The total number of assisted conversions is lower compared to other assisting channels.

2. Multi-Channel Funnel Overview

This report will help in understanding the relationship between particular channels. The derivation from the multi-channel report can be connected with the Assisted Conversion Report.

Multi Channel Funnel Reports

Multi-Channel Funnel Overview Report

Suppose, from the Assisted Conversions Report you find that Display Channel plays a vital role in driving assisted conversions. From this report, you should check with which channel it is highly linked.

So if from this report you come to know that Display and Direct are highly linked then we can conclude that the final conversions from the Direct channel are assisted through the Display channel.

3. Top Conversion Path:

If you want to find which path brings the highest conversions, then this report will become your go-to.

Multi Channel Funnel Reports

Top Conversion Paths Report

With the use of advanced filters, one can know a particular relationship between two unique channels. Say you want to know the count of only those conversions assisted through DCM, that finally converted through Direct. You can use filters like “include channel” which begins with DCM and ends with Direct.

4. Model Comparison Tool

You can know the consolidated media performance. Also, it enables you to compare different attribution models and find the effectiveness of any particular channel for different attribution models.

Channel Effectiveness for Marketing

Model Comparison Tool Report

You can also use Data-Driven Attribution Model if you have opted for Google Analytics 360. Data-Driven Attribution Model is based on Model Comparison Tool Report, through which each channel gets attribution on the conversion paths and their probabilities to get the conversion. It is considered a better attribution model than any other model.

Google Analytics

Various Date Range Comparison

You can also compare the conversions for two date ranges according to a particular attribution model to check the contribution of various channels in driving conversions over the period of time.

Best Practices for Accurate Results:
  • Use un-sampled report: For multi-channel funnel reports, the sampling limit is one million conversions. So using an un-sampled report is advisable here.
  • Advanced filters: Knowledge of advanced filters can save a lot of time. It makes the report look eye-pleasing since you can exclude  unnecessary channels
  • Date range: Taking into consideration appropriate date ranges can actually bring meaningful insights
  • Data accuracy: The conversion metric you select (transactions or a goal) should be capturing accurate data. If not, the entire analysis can give a misleading picture.

As a result, investing in different channels according to their performance will yield a greater ROI. This way you can avoid investing hefty amounts on the wrong channels with false hopes.

Looking for more information or need help measuring your channel effectiveness? Drop your details in the comment section below and our experts will be glad to assist you!

3 Personalization Challenges That You Can Solve with Google Optimize 360

Google Optimize 360 Blog for conversion rate optimization

 

The webinar on website personalization with Google Optimize 360 covered use cases for domains like eCommerce, Digital Publishers and Lead Generation. The response was overwhelming and we received many queries from our users. All those queries were in and around related to the executing personalization experiments. The problem seems to be the perception of website personalization as a big challenge. Things have now changed for the better. Personalization and content experimentation is not as difficult anymore. With the right solution, you can start personalizing your website with fewer challenges. In this blog post, I have covered 3 most common challenges in executing website personalization. We will also see how Google Optimize 360 is the perfect solution to address all such challenges.

Delivering to Different Customer Personas

Website Personalization

Showing relevant content to relevant user segments is what personalization is all about. You can identify your user segments from user behavior and actions on the website.  It is definitely challenging to cater to different user types at the same time. Discrepancy reflects when your analytics data and personalization delivery system are not integrated. This is where  Google Optimize 360 feature ‘Targeting GA Audiences’ comes into play. Thanks to this feature, all you have to do is, link your Analytics and Optimize account. Once that’s done, you can identify different customer personas with information from GA. Now, you are all set to create Audiences out of the same. This enables you to target many customer personas on your website at any given time. Not only this! Your Google Optimize 360 account links with your AdWords account. This enables delivery of personalized landing pages based on keywords, ad groups, or campaigns associated with an ad. All this can be done without messing up with the query parameters in destination URLs. Such unique integrations with personalization delivery tool gives competitive advantage for your website.

Measuring the Impact of Personalization

Conversion Rate Optimization

Testing personalization hypothesis is one of the best practices. While experimenting, one may derive many reports and come up with various insights. But we often face difficulty in determining the success of a personalization experiment. This confusion arises from the unclear scenario from the given data. In such cases, advanced statistical approach of determination can help. Optimize 360 uses the Bayesian statistical method to model the performance of experiment. This delivers clear and action-oriented results. The reporting in Optimize is based on Analytics. It means, you can segment your personalization experiment audience into your Analytics. Using these segments you can analyze the impact of personalization hypothesis. Whether it is on new visitors or users from a specific channel, you can get a deeper understanding of the impact on your business.

Efficient Project Management

Personalization Challenges

Managing personalization experiments in an organized way seems to be a commonly faced challenge. This specific challenge arises because of increased interdependency between two different operational teams. The marketing team has to rely on IT and development team for help to put in place some personalization tactics. The visual editor feature in Google Optimize 360 comes to rescue in such a scenario. It enables a non-tech professional to create personalized variants for users eliminating dependency. It also keeps a track of changes in variants in chronological order. Additionally, this tool enables the project manager to give role-based access and control the process of implementation. This allows an efficient management of all the personalization experiments. Moreover, these features also help create and maintain standardized processes for content experiments.

Concluding Thoughts

Things have now changed and personalization being a business challenge is only a perception. Google Optimize 360 is truly the powerhouse of website personalization. With this next-gen tool, you can test personalization strategies with minimal efforts. In case of any questions on Google Optimize 360, feel free to leave comments below and I will be happy to answer.

Tatvic does offer solutions for Google Optimize 360.

Track Your Android Webview as Screenview in Google Analytics and Get a Perfect Flow of User Journey

webview

webview

Are you struggling with tracking Webview data as normal Screen view in Google Analytics? In this blog post, I am going to take you through the process of achieving that step-by-step.

Why track Webview as Screenview in Google Analytics?

Your company has its business on an App as well as a Website with satisfactory Google Analytics(GA) tracking implemented using Google Tag Manager. You are rendering some of the pages like Terms & Conditions, Policies, etc in the webview within an App.

For the purpose of understanding, let me show you how you might have muddled up your GA Data in both App and Web Property:

  1. Web Property of GA :
    1. Page tracked in a web GA Property, even though it is opened in the App
    2. Sessions created in a web GA Property with only a single Pageview
    3. Unnecessary user and session created in a web GA property
    4. Redundant user created in a web GA Property leading to false insights  
  2. App Property of GA :
    1. No Screen view tracked for web page rendered in the App
    2. Loss of screen view data, for the pages that are actually rendered in webview

I would sigh in despair encountering the above problems, thus to deduce the above-muddled data we will here try to unite the tracking data of both the app and webview in the most savvy manner.

The implementation includes two steps :

  1. Track the page rendered in webview as a screenview in an app GA Property
  2. Restrict the same page from being tracked as pageview in a web GA Property
1.) Track the page rendered in webview as a screenview

To track a screen view for the webview page we will utilize the readily available function of webview onPageFinished().

Every time when a page loads in webview, the above function is called implicitly, hence we add the code snippet of tracking screen view within this function. This code will identify which URL is opened and using this we will track the screenview for the opened webpage.

Android Webview

DataLayer push to track screenview

NOTE :

A Screenview Tag must be configured in the Google Tag Manager console, with the trigger event.

In the above scenario, the triggering event for Screenview Tag is “OpenScreen”.

Chances are that there may be more than one page being rendered in webview one after another and we need to track all the pages rendered in webview.

Well we don’t need to worry much as the above-mentioned function will be called every time when a web page is loaded in the webview, either it is the same page or a new one. You just need to fetch the URL of the opened web page, identify which page is opened, and accordingly apply a condition to send Screenview hit by defining the appropriate screen name for each different page opened in webview.

2.) Restrict the same page from being tracked as a pageview

As above we have tracked a web page as Screenview in App Property of Google Analytics, it is necessary that we restrict the same page from being tracked as Pageview in Web Property of Google Analytics at that particular instance.

To do so we will set a unique identifier for App Webview, by altering the UserAgent of it. This will help us identify whether the web page is being rendered in the webview of your Application.

Also, this will be the key point for us to restrict the firing of pageview hit in the Google Tag Manager configuration.

The below code in the native App alters the UserAgent of the webview.

Android Screenview

Altering the Useragent

Once we have set up the tracking code in the native app, it’s now time to plunge into the Google Tag Manager configuration. Please Note that, as we need to restrict the Pageview firing we are here referring to the Web Google Tag Manager Setup.

The Google Tag Manager configuration involves two steps :

  • Configure Custom HTML Variable in Google Tag Manager of Web, which identifies whether the web page is opened in Webview or not.
    Configure the Custom variable with the below code snippet, that fetches the UserAgent of the current application where the web page is loaded. The code will either return true if the page is rendered in webview of our App, or it will return false otherwise.Google Analytics                                                                                                   Script to identify webview
  • Use the Above variable in Pageview Trigger to restrict the firing of Pageview Tag when the page is opened in Webview.User Journey

Trigger setting for pageview tag

After working our fingers to the bones we have finally accomplished collecting the Webview data in the correct Google Analytics Property. You can now explore your Google Analytics reports to substantiate your implementation.

Hopefully, by now, we have aptly tracked the webview data as screenview in the correct Google Analytics Property of App. At the very same time, we have also restricted the pageview firing for it. Thus we have now apprehended the perfect flow of user journey in our Google Analytics Report.

If you have any queries with regarding the process described above, I invite you to come back here and tell us about the before-and-after. I bet you’ll have something to say! Moreover, check out our recent most webinar on Deep Dive in App Analytics where we have covered this as a use case.

Google Analytics Tracking to Boost Conversion Rate Optimization

progressive web apps

 

According to Google, Progressive Web Apps are experiences that combine the best of both worlds - the web and mobile apps. They are useful to users from the very first visit in a browser tab, no install required. As the user progressively builds a relationship with the app over time, it becomes more and more powerful. It loads quickly, even on flaky networks, sends relevant push notifications, has an icon on the home screen, and loads as a top-level, full-screen experience.

Importance of Progressive Web Apps Tracking:

PWA is much more than a hot buzzword right now. It can resolve all your issues right from delivering a faster loading mobile website, decrease your page load time on it and also give you insights as to how much time it takes for a customer to book something from your mobile site. But, do you ever find yourself asking “What about Google Analytics implementation? How will that work in such dynamic sites? What about pageviews, sessions, source/medium? Well, we have all the answers on how to implement Google Analytics for PWA for you right here in this blog, read on to find out.

In this blog post, we are going to focus on achieving tangible benefits to your critical business KPIs through PWA.

Progressive Web Apps, in simple terms, is bringing an app into a mobile web in a revolutionary format. It can run on a reliable or even low internet connections, which will enable users to have quick access and will also help your business grow when compared to your native site.

Standard vs PWA pages

In today’s fast speed 4G times, every user is on the lookout to have quick access to the information or product he’s in search for. A survey by SplitMetrics suggests that an average of merely 26.4% of users that visit your app store page will install your app and other 73.6% of users are simply lost.

Many times users bounce immediately if a page takes a long time to load. By using PWA, there are many benefits across different verticals in terms of their user engagement and conversion rate.

Here’s how implementing and tracking PWA helps different verticals:

  • Digital Publisher: If you are implementing PWA, you can definitely improve the effectiveness in terms of increasing the average time spent on page and the number of pageviews. This would also translate into a significant decrease in terms of bounce rate and page load time.
  • E-commerce: PWA can enable eCommerce businesses to increase the effectiveness in terms of a better conversion rate that translates into an increase in sales.
  • Lead Generation: Optimize the effectiveness in terms of page load time and increase in leads
progressive web app tracking

Image2: Difference between PWA and Native M-Web

Use Cases:
1) Increase in the Time Spent on Page:

One of our clients is a digital publisher. They were experiencing a majority of incoming traffic on their mobile site but the engagement metrics were way less than that on Desktop. We identified that the reasons behind these were the high bounce rates and very short session durations. Contributing to these was the high average page load time when compared to other devices.

Once we understood their problem, our team suggested that the better approach to reducing page load time is to implement PWA. Tatvic provided complete support in the tracking and implementation process. It was then rolled out to 10% of the traffic so as to verify the user engagement metrics. The outcome was much more than our set expectations. We observed a sudden rise in user engagement which resulted in less page load time and users are spending more time.

2) The decrease in Bounce Rates:

With a strong decrease in desktop growth, one of our lead generation clients gets over 85% of their traffic from mobile devices and still in increasing trend. Most of their visitors come in from their native app and the rest all via their mobile website. However, their mobile site bounce rate kept getting higher day by day.

We analyzed the mobile site behavior and realized that their UI experience was too slow on Mobile. However, we observed that client is focused on acquiring quality users and growing their user engagement on the mobile web through Google Analytics data. We then looked into PWA as an alternative solution which provides a faster-loading and a similar experience like an App.

Client focused to re-engage for mobile site users, instead of acquiring new traffic. As a best practice, we suggested them to shift to PWA site altogether and also helped them with their tracking requirements. With just these two updates, their user engagement increased by double as opposed to the native mobile site which in turn increased their leads as well.

3) Optimization of Revenue and Conversation rate:

A popular eCommerce business was facing the challenge of a low conversion rate. They generally experience incoming traffic largely from their mobile website. Our team identified the pain point with the help of Google Analytics 360. The insights drawn from the analysis was that users with low internet speed experience a high page load time. This resulted in a low conversion rate.

However, thanks to our long-standing relationship with the client, we suggested our client implement PWA rather than working towards optimizing their mobile website. They shifted to a Progressive Web Apps site for 5% of users. Gradually, they experienced a dramatic change of 50% increase in their conversion rate.

Concluding Thoughts:

To conclude, PWA has shown all the traits that it has the potential power of becoming the future of Mobile websites. Ensure your users are better engaged and the journey isn’t broken prematurely. With the real life use cases shared in this blog, we aim to give you a better sense of how implementing Google Analytics for PWA has great impacts on your business.

Check out our webinar on Progressive Web Apps (PWA) Analytics Tracking with Google Analytics. Register today to ensure you don’t miss out on an awesome session.

If you’ve any queries, doubts or you need any help, please leave a comment below, we’d love to hear from you!

Bot Icon
Bot Icon

Tatvic Bot

Explore About Tatvic and Services