Hello There!

Lorem ipsum dolor sit amet, consectetur adipiscing elit,

 About Ravi Pathak

Ravi is the co-founder of Tatvic and expert at managing different web analytics tools. Ravi actively works on conversion optimization projects to improve conversion rate and test newer hypothesis with e-commerce companies.

How to Customize Google Analytics Campaign Timeout For Affiliates

As a marketer, we all should have used the feature in Google Analytics to set the Campaign Timeout period. By default, campaign timeout settings in Google Analytics are set to 6 months. What it means is, GA will stop giving attribution to a specific campaign after 6 months. We also have the option to change this setting to customize the campaign timeout period ranging from 1 minute to 24 months depending on the business need.

                                       Image: Campaign Timeout Settings in Google Analytics

The idea behind customizing the campaign timeout period is to adjust it according to the campaign duration. Or, the duration for which we think the campaign could be relevant or should get the attribution.

For example, brand campaigns run for user acquisition tend to be relevant for months. Whereas, micro-campaigns like one-day offers have an impact on users for a few days.

Problem:

Here, we may start having a problem with setting up a campaign timeout period. As the setting is applied at the GA property level, the same configuration will be applicable to all the GA views and thus to all the campaigns.

Many times, we are running many campaigns with different goals - user acquisition, user retention, etc.

We may want to set up a different campaign timeout period. Going by the default settings in Google Analytics, all the campaigns will keep getting attribution for six months.

Businesses that acquire users from affiliates face a bigger challenge. If we are getting users from certain affiliates for only two weeks, we would not want to pay that affiliate after the contract is over. Hence, another possible problem is the fact that relationships with different affiliates vary a lot.

Possible Solution:

Looking at the severity of the problem, Tatvic came up with workarounds. The solution allows us to set up different campaign timeout periods for different affiliates or campaigns.

There are constraints in GA configurations. To overcome it, we create a new Google Analytics property for the affiliate with a new campaign timeout period.

For sending the user behavior data in both the GA properties without impacting current reporting, we make some modifications from Google Tag Manager. This way, we are able to track affiliate traffic as per the specific need and also make sure that rest of the reporting is intact.

Conclusion:

Now that we are able to customize the campaign timeout period for affiliates, we have a clear picture of which campaigns are performing better and can compare affiliate performances.

To make the reporting simple across different GA properties, we use another fantastic product from Google - Looker Studio. Google Data Studio allows us to easily build reporting dashboards from many data sources.

This way, we get all the numbers related to Affiliate traffic in one place.

What’s Next:

The affiliate marketing industry is expected to reach $6.8 billion by 2020. If you are already working with affiliates or planning to do so in the future make sure you customize the campaign timeouts appropriately.

We hope the blog proved to be insightful to you and helped you in understanding the importance and know-how of customizing campaign timeouts for affiliates. If you have any doubts or are looking for clarifications, please drop in comments and we will surely get back to you.

Firebase Analytics tips to Control Mobile Application Limitations


Introduction
Firebase is one of the popular products from the Google Analytics 360 product family that has rapidly gained an affinity as a go-to tool for App development & analytics. Firebase SDK provides a bagful of features to make the end-to-end process of mobile app development run as smoothly as a hot knife through butter. After its acquisition by Google Analytics, Firebase is now a wholesome platform for your app development & app data analytics requirements. Today we are going to focus on Firebase Analytics and the limitations we face while using the tool for data analysis & insights. In this blog, we will also look at workarounds for each of the major limitations & discover how swiftly we can overcome them.

Why we love Firebase Analytics

  • No additional cost for analytics data collection - yes it is totally free of cost.
  • Unlimited data collection - can collect up to 500 unique events.
  • Crucial events’ data collection is done automatically. This includes events like App installs, App uninstalls, In-app purchases, App updates, etc.

There are quite a few other bundled-up features of Firebase Analytics such as Crash Reports, Notifications Setup that targets the Audience generated by Analytics, and diverse sets of events.

Firebase Analytics Limitations: Our wishlist for Firebase Analytics & a few basic workarounds to overcome the limitations and achieve better reporting

  1. Restricted Reporting :
    • Firebase reporting console barely offers any course of action to view data in diverse ways. We have the one and only “Events” Report to view all the tracked events at once. Elaborating further, the Events Report provides no major cardinality on reporting apart from the option to apply a basic filter on either “Event Name” or “User Property”.
    • Another major limitation of the Event Report worth highlighting is the inability to view the extra parameters tracked with one single event in the said report. Note: Firebase Analytics can report data only on 10 text parameters and 40 numeric parameters in the Event Report.

      Image 1 : Setting Up Parameter - Limitation.

    • Firebase also falls short of API support so as to access the collected analytical data.

    Workaround: Your best bet to access the raw analytics data is to link your Firebase Analytics data with BigQuery.  And when it comes to BigQuery, performing analysis on massive datasets is simply more straightforward. This will solve a major issue of limited data access, and, at the same time, we also gain the liberty to perform analysis on diverse datasets in a single pane.

    Note: Linking to BigQuery will cost us a few pence!

  2. Event Limitations :
    • Despite the fact that Firebase offers unlimited event collection for each event type for your App, it has confined us to the range of the said event types. This means we can only have 500 unique events for an individual app in the Firebase project. To begin with, this limit does not seem much of a hurdle, but if we revamp our app tracking or if we keep updating the event tracking process, without a doubt we are going to meet the dead end of the reporting platform.

    Thus, precautionary steps to manage the event limitations are:

    • To wisely design the event names before they are implemented.
    • To define a standard structure, identify the events and the required parameters for event tracking in an app.

    For Example:

    • Navigation Event: This event is templatized for all the navigations that a user can perform within an app.
      navigation_<from_to>” - here “from” and “to” are navigation sections defined in-app.
      Parameter1 - intermediate of navigations to be tracked in this parameter.
      Eg. navigation_home_help, navigation_home_mens-shirt.
    • Product Interactions: This event is templatized for user interaction with the product.
      product_<interaction>” - various product actions(i.e. View, click, addtocart) can be tracked.
      Parameter1: “Category”
      Parameter2: “product name”
      Eg. product_view, product_detailed.
    • For Articles:  This event is templatized for tracking articles.
      article_<action>” - various article actions (i.e.  viewed, click, read_began, read_incomplete) can be tracked.    Eg. article_clicked, article_read_began,article_read_complete.
  3. Campaign Attribution :
    • The attribution of Install referrers in Firebase is controlled by Firebase SDK itself. Currently, Firebase tracks attribution for a limited number of Advertisers which are defined in this link. For any other platform or source/medium attribution, other than the listed Advertisers, the default attribution of source/medium will be done to direct.

    Workaround: Knowing the fact that we are missing out on a major custom campaign attribution, we need a quick fix on it. For this, we have worked out a solution which I shall share with you as a separate blog post.  Our custom solution includes tracking both; install referrers and custom campaign data. Below is a glimpse of the Attribution Report for Custom Attributions.

      Image 2: Attribution Report with custom “source” value.

Conclusion
Here, we have discussed how data can be analyzed in a better way by linking BigQuery as compared to normal reporting. Also, for reporting it is necessary that we collect meaningful data and as mentioned in point 2 above, do not reach the limitation of the event type that is getting tracked. We have already seen a few examples of how to structure and design the events in this blog, and we hope you find them resourceful.

Quick Tip: If using Firebase Analytics, do plan out the tracking approach and efficiently design the events for the same. This will yield absolute data in reports and help you analyze it.

The limitations discussed above cover a large ground of Firebase Analytics. However,  if we have missed out on any titbits on the same, do comment in the below section and we will be happy to acknowledge it!

4-Steps Tip to Detect Facebook in App Browse

Identify FaceBook In-App Browser

 

Google Analytics offer a dynamic platform to track and analyze your website traffic in various ways. Talk about the hidden gem of Google Analytics, talk about Acquisition Report. This blog explores the Acquisition Report to understand the diverse channels that identifies the source of origin from where users lands on to your website.

Since it is crucial to know the source of your website visitors, the Acquisition Report helps in comprehending the right channel, referral, and source performances.

However, the challenge in Google Analytics is to track a web page that is displayed in Facebook in-app browser. The implausible result can be any of the following:

  • Difficulty in identifying the actual origin of traffic.
  • Inadequate estimation of the ad campaign(s) that are active on social networking sites.

To bridge the above gap in Google Analytics, we will here understand how to track a web page that is rendered in a Facebook in-app browser.

Following are the prerequisites to track the actual in-App browser in Google Analytics:

  1. A Google Analytics Custom Dimension (named - browserType) preferable of Session Scope.
  2. Google Tag Manager(GTM) implemented on web page.

We will now move to the implementation steps :

  1. Create one Data Layer variable “browserType” in GTM

     2. Create a Custom HTML tag in GTM and add the following code within it

NOTE : Make sure that the Custom HTML tag triggers before or along with the the pageview in GTM implementation.

3. Set the browserType in a Page view Tag

NOTE : The index number set in custom dimensions is equal to the index number of the custom dimension in which you desire to view the data

    4. You can also track the browser type with an event. Below is the Event Tag configuration:

 

That’s that! You are now all set to track the Facebook in-app browser.

Below image is just a glimpse of the report you would see post atoning to the above-mentioned changes.

Leave your comments to further offshoot the In-App Browser Tracking and we will be glad to assist you further.  

How to setup Google Analytics site tagging & tracking with gtag.js?

Since the last few weeks, you must have heard and read quite a lot about gtag. Have you been wondering about analytics.js? Do you think it’s a game-changing method for implementing Google Analytics across your websites?

In this blog, I have curated and laid out some general information about gtag.js and as a cherry on the cake, we have a few tips for you so that you can use gtag.js optimally.

Google Analytics has released a new implementation method, called the Global Site Tag (gtag.js) and it is yet in beta.

First of all, let’s address a rumor that’s been going around and get it out of the way. I have come across quite a few comments and questions where there seems to be a misconception that gtag.js is a newer version of GTM. But as a matter of fact, that is not true. gtag.js is not a newer version of GTM but rather, a newer version for analytics.js

gtag.js global tracking snippet

 

Why gtag.js?

The ga.js was developed mainly for measuring websites way back in June 2006 with ga.js & dc.js. After some time, Google Analytics came up with a new tracking library analytics.js in 2013, which measures the website but is much more user-centric. Hence, with this update, we can track the user’s journey throughout multiple devices using User Id and so on.

Now, here we are at the end of the year 2017. Analytics.js is more than 4 years old. Google Analytics has come up with another update in the tracking library. This time around, the main reason for making this change is to achieve clean tagging and unification across Google’s site measurement, conversion tracking, and remarketing products.

Setting up gtag.js:

To find the gtag.js code snippet follow these steps:

Step 1: Sign in to your Google Analytics account

Step 2: Click on Admin

Step 3: Select an account from the menu in the ACCOUNT column.

Step 4: Select a property from the menu in the PROPERTY column.

Step 5: Under Property, Click Tracking Info > Tracking code

gtag.js

Note: Put gtag.js tracking code snippet right after opening <head> tag on every page.

Tracking Pageviews:

You just need to put the following line for pageview.

Tracking Events:

Note:

This event will send to the default configured UA id in gtag(‘config’,’<UA ID>’).

Cross-domain tracking in gtag.js:

If you have an eCommerce website or such a website from where your user can travel from one domain to another (not subdomain), you need to set up cross-domain tracking in gtag.js

What is cross-domain?

If you have a website set up as www.source.com and you also own www.destination.com - this kind of setup is called cross-domain. If this is the case then you need to set up the said cross-domain tracking.

Note: www.website.com is the main domain, shop.website.com is the sub-domain and hence for this you don’t need to set up cross-domain tracking.

Setup cross-domain tracking in gtag.js:

If your is able to travel to destination.com from source.com and return to source.com from destination.com, place the following snippets on respective domains as mentioned.

The following snippet needs to be put on source.com

The following snippet needs to be put on destination.com

Tips for Using gtag.js Optimally:-

1. For configuring Google Optimize using gtag.js:

To load an optimized container using gtag.js, one just needs to put the following line With valid GA_Tracking_id and optimize_container_id for configuring Google Optimize.

For more detailed instructions:

Google support link for deploying google optimize using gtag.js

2)  Firing website conversion tracking tag:

Note:

  • For conversion tracking, you need to add your AdWords id in gtag(‘config’,’Adwords Id’)
  • If there is already gtag snippet exists on your page then put gtag(‘config’,’Adwords Id’) after gtag(‘config’,’GA_Tracking_Id’)

gtag tracking

Event Snippet:

3) Client Id Implementation:

In analytics.js, one who wants to send a client id in a custom dimension has to follow some steps instead of that gtag.js gives one step solution.

Concluding Thoughts:

As of now, gtag.js is in beta and it will be rolled out in the near future, complete with all features which are yet not available. Even though, it provides many features, sending data to multiple UA Tracking IDs is one of my favorites.

Using gtag.js is simple as well as beneficial since it lets us use the latest tracking features. Have you had the chance to know gtag.js yet? If yes, we would love to know your opinion on it, and in case of any queries too, please leave a comment and tell us about it.

How Tracking Internet Speed with Google Analytics Can Enable You to Improve Your Website’s User Experience

Tracking Internet Speed


Tracking Internet Speed

Internet connection speeds are on the rise globally. According to reports from Akamai, world’s leading cloud service provider, global average internet speed increased by 15% year on year to 7.2 Mbps1. South Korea continues to have the highest average internet speed 28.6Mbps, followed by Norway and Sweden. A major shift in internet ecosystem is also observed in Indian markets with 4G revolution recently.

We have observed a tremendous change in the way content delivery happens due to the availability of better internet speed. This has also paved a path for user interaction happening in a more in-depth manner than ever before.

According to studies1, the digital video audience is expected to grow at 8.2% in 2017. User experience has improved dramatically for the new age apps. The inherent restrictions caused by slow internet speeds is no more a roadblock. Businesses need to update their content (website/app) to match to the latest technology trends since the market has moved on from static websites to instant personalized content to users based on their past behavior.

With better infrastructure, fast internet and increasing user base, diverse markets like India have a huge potential for telecom companies. While making the changes, we also need to keep in mind that 40% of mobile internet subscribers are still using 2G network. Though the number of 2G internet users is declining in the country, we have to make sure content is accessible on 2G network as well.

To make the decisions based on users network types, it is imperative to track internet speed for every user we have.

Internet Speed Tracking solution developed by Tatvic team is pretty handy here.

It helps us understand the following:

  • True download speed at specific time
  • Network Type - 2G, 3G, 4G

These reports will be available in Google Analytics for every individual user along with acquisition and behavior data. One can create reports like Correlation between Internet connection speeds and content consumption rates by geography, network type across time.

User Experience
Use Cases:

Content Optimization:

If we observe that most of the users (let’s say more than 60%) are coming from 4G network, we can focus on better designs, adding animations to improve user experience. To increase the user engagement, we can also consider adding more video content as well. But on the other hand, if more users are from slower connections like 2G, the focus would naturally be on content optimization. Less content and fewer user interactions would be key to drive more conversions in such a scenario. In such cases, it’s better to store content on users devices and thus achieve faster content delivery, for which, Progressive Web Apps is the perfect solution.

Personalization:

In today’s dynamic world, ‘one size fits all’ doesn’t work anymore. We cannot have same strategy/design for both slow connection and fast connection users. Personalization tools enable us to serve different user experience to different segments. In above analysis, if we are having users coming from different network types and correlation in conversion rates and app designs by network type is higher, we should consider personalizing content by network type.

What’s Next:

If you are looking to personalize user experience based on network type being used, Google Optimize can be helpful. Its one of the best tools for running AB tests and personalization solutions. It natively integrates with Analytics. So we can use integrations with other Google products like AdWords, BigQuery, DoubleClick For Publishers, etc. to deeply analyze the metrics. Tatvic has posted an informative webinar on Personalization using Google Optimize.

We hope the blog was insightful for you and helped you in understanding the benefits, as well as the use cases of tracking internet speed and network types for your website/app. If you have any doubts or are looking for clarifications, please drop in comments and we shall be sure to get back to you.

Tracking Push Notifications in (UA3) Google Analytics to Interact Users with Brands

push notifications tracking

Most businesses nowadays are leveraging technology to make it easier for their customers to interact with them. Technological strides such as the launch of Mobile Apps, Accelerated Mobile Pages, and Progressive Web Apps have been key in facilitating a stronger connection between these 2 entities.

There are over 2.8 Million apps in the Play Store and 2.2 Million apps in the App Store, it is highly likely that a customer is using mobile apps from competing businesses. So, can there be ways to drive customers to use your app over others, once the customer has been acquired? How do you change the status of a user from an active user to a daily or weekly active user?

The answer lies in the glorious solution of Push Notifications. I am sure you are already aware of what a push notification is. As a refresher, let’s go through the definition once again.

A push notification is a pop-up message that looks like an SMS text message or a mobile alert. The app publishers can send push notifications to the user once the user has installed the app. The user need not have the app open to receive the notifications.

How can push notifications help increase user engagement?

An app publisher can send notifications to users at different times. Below are a few examples of when you can send notifications to drive engagements:

  • Notifying users about the sale that the publishers would be hosting in the coming few days. A user is less likely to miss push notifications as compared to emails and SMS text messages.
  • Retargeting users based on their recent activities. For example: Suppose a user has recently booked a flight to New York using your app. Later, you can send notifications to this user with details on hotels in New York during the user’s visit
  • Nudging users drive them to complete a purchase funnel. For example, if you are an E-commerce business and one of your users has added a few items to cart and exited. You send notifications to remind this user to complete a purchase for the products.
  • Sending regularly timed daily/weekly/monthly notifications to users to keep them updated on the new releases on your app.

There can be many such similar use cases where you can leverage push notifications to drive more engagement from the users.

Tracking Push Notifications:

While push notifications can help increase user engagement,  tracking the performance of different types of notifications helps in determining how your users are reacting or interacting with your push notifications.

Analytics Best Practices for Tracking Push Notifications

For gaining insights from push notifications, it is recommended to track the following events:

  • Push Received:

“Push Received” event should be fired whenever a user receives a push notification. But, this event does not indicate that the user has interacted with the notification

  • Push Clicked:

The “Push Clicked” event should be fired whenever the push notification has been clicked by the user. This indicates that the user has interacted with the notification and is interested in the information provided

  • Push Discarded:

The “Push Discarded” event should be fired whenever the user discards the notification sent. This indicates that the user has interacted with the notification. However, the information provided under the notification has not been useful to the user.

The occurrence of events - Push Received and Push Discarded does not indicate that the app has been opened by the user. These two events should be configured as non-interactive events in Google Analytics. The event Push Clicked should be marked as an interactive event as it indicates that the user has shown interest in the information sent.

The events would be displayed as shown below in Google Analytics reports -

Events tracking insights in Google AnalyticsImage 1: Push Notification Tracking Events Report

Insights from Tracking Push Notifications with Google Analytics:

  • The behavior of Returning Visitors:

You can build a mechanism to understand the behavior of your returning visitors. You could also use it to ascertain the app’s usability. A high ratio of Push Discarded to Push Clicked events for all types of push notifications sent could indicate problems in App’s usability.

  • Engaging Push Notifications:

Tracking the aforementioned 3 events for all types of Push Notifications will give you insights as to which notification types perform better.

  • Uninstall Tracking:

If users receive too many notifications from an app, they are more likely to uninstall that app. An indication of the same would be a high number of Push Discarded events. In such a scenario, you can cite the high number of push notifications as a probable reason for the uninstall.

  • The audience for Adwords Remarketing:

Push notifications can help you create an audience for remarketing. Users with a higher number of Push Clicked events tend to engage more with the app. They also have a higher probability of transacting. With this data, you can create segments for this cohort of users and re-market effectively.

Concluding Thoughts:

We all accept that push notifications can drive greater user engagement. But tracking these engagements actually helps businesses to allot resources towards the right type of push notifications. It also gives us an optimal frequency at which notifications are to be sent. Following this practice keeps any negative impact on your user experience at bay.

Have more insights for push notification tracking? Tell us about it in the comment section below and also feel free to leave your feedback for us. We would love to hear from you.

10-Google Analytics Advanced Custom Segments for Marketers to Measure

Google Analytics Advanced Segments

Google Analytics Advanced Segments

Google Analytics Advanced Segments are one the most valuable tools in Google Analytics for someone looking to understand their business performance in a better manner. It is a way to quickly segment the traffic in Google Analytics.

Using Google Analytics Advanced Segments is much like mining for gold. It allows isolating specific types of traffic in your reporting.

Do you want to see reports for visitors only from a particular city? Or do you want to see how visitors from organic search behave compared to visitors from paid search? Advanced Segments can do these for you and so many other things. In this blog, I shall demonstrate 10 must-have Advanced Segments to up your analytics game.

1. Mobile Traffic (Excluding Tablet)

It’s useful to know how many people are visiting your website from their mobile phones and how many are using tablets.

This helps you ascertain how important it is to have mobile-friendly sites and understand how their performance and conversions differ across devices.

Google Analytics has a pre-defined Advanced Segment for mobile traffic, but this includes tablet traffic too. Since mobile and tablets can be very different, it makes sense to look at it individually.

Google Analytics groups iPhone and iPad traffic into one group: Operating System = iOS. You can exclude screen resolutions of iPad from this segment, meaning it should only show you mobile traffic, excluding tablets.

Mobile Traffic (Excluding Tablet)

Mobile Traffic (Excluding Tablet)

2. Traffic Source with Conversions

For every business with an online presence, it is imperative to know where the conversions are coming from. Below are some advanced segments that you should look at, to know the converting visits from specific traffic sources:

  • Organic Visits with Conversions
  • Social Visits with Conversions

For this social media traffic segment, you can use the following regex to capture the majority of social sites.

3. Not Provided Segment

Missing keyword data (Not Provided) is a big hassle for marketers and this segment can tell you exactly how much of a pain it is. To see the impact of missing data, I would recommend using these two segments:

  • Not Provided Data
  • Excludes Not Provided Data

Compare these two segments with each other to see whether they contain keywords that are actually valuable to your business. Analyse content report, conversion report to understand the difference between these two types of users.

4. Keyword Length 

Knowing what type of keywords are bringing most traffic, most interactions and most conversations on your site are really insightful in terms of getting to know what searches are bringing the most users to your website.

I use the following segments to analyze the important terms that are driving traffic to the site. I’ve also provided the regex that I use to create these Google Analytics Advanced Segments

  • 1 Word Keywords -  Regex ^s*[^s]+(s+[^s]+){0}s*$)
  • 2 or 3 Words Keywords - Regex ^s*[^s]+(s+[^s]+){1,2}s*$
  • 4+ Words Keywords - Regex ^s*[^s]+(s+[^s]+){3,}s*$

Keyword Length

Keyword Length

5. Cart Abandoners by Traffic Source

If you are an eCommerce site, then there are quite a few scenarios when you probably wonder why people abandon your cart without checking out. The answer tends to vary largely, often by source. Explore the differences in cart abandonment by creating a segment by traffic source.

Cart Abandoners by Traffic Source

Cart Abandoners by Traffic Source

In the above example screenshot, this segment gives you data on the cart abandoners visiting from Facebook. The same can be replicated for any other traffic source.

6. Business Hours vs. Off Hours

Does the conversion rate of your website change between working and non-working hours? This segment compares traffic received during and after business hours. Adjust this segment to align with your business hours and then apply this to reports to investigate differences in site performance both before and after work hours.

7. Depth of Visits

This segment is a good way to understand how engaged your visitors are on your website. Use this segment to see the number of visitors viewing three or more pages on your site. You can also enhance this segment to understand which traffic source keeps your visitors most engaged.

Bonus Advanced Segments

Here are some more Google Analytics Advanced Segments you might want to consider, depending on what makes a difference on your website.

  • Segmentation by demographics.
  • Segmentation by a Technology platform.
  • Segmentation by Geography.
  • Segmentation by Visitor type. (New vs Returning, Registered vs Non-registered)
  • Segmentation by Landing Page.

Concluding.

The list of Advanced Segments you could create is endless. You will have to decide what is most valuable to you. It is very important to use the data wisely, try and compare data to other segments, and make informed decisions.

Moreover, if you are a Google Analytics 360 user, you can create these advanced segments and export them to DoubleClick For Publishers in order to target a customized audience to achieve a greater conversion rate. Read this blog and learn how to create an advanced segment and export it to DFP.

If there are other advanced segments that you use and you absolutely think are a must-have, please tell us about them in the comments section below. We would love to know!

Pay Attention to Your Users’ Actions by Tracking Client ID in Google Analytics and Stay at the Top of Your Game

Google Analytics is a ginormous platform that lets you track the user actions and behavior in the digital era of merchandising and provides insights based on those user actions, in various ways. There are many root node of Google Analytics which hold hands together in providing insights, such as customizable reports, real time visitors views, automated data collection, easy integrity with other platforms, etc. But to make these specified features significant, in the core of Google Analytics tracking lies the Client ID. After we go through the benefits of Client ID, we will grease the wheels on how to track Client ID from iOS device.

What is Client ID ?

Client ID can be described as a unique identifier for any user, limiting the user’s sphere to a specific devices or a browser. It can be considered as a pivot point for the data relative to a unique user. It also contributes majority in the Audience report in Google Analytics to provide measurement of user count with a cardinality of New Users and Returning Users. To sum up, Google Analytics is totally dependent on Client ID to measure the audience of your application, and using Client ID Google Analytics also provides brief detail on the Active Users for a specific time span.

Let us now capture the essence of Client ID and understand how it can be used in visualizing data in an eloquent way. We will walk through two different use-cases that utilize Client ID in visualizing the data.

  1. Mapping of events at user level :
    Assume we are a lead generation marketer and we have successfully implemented event tracking for various actions of the users. The manager now demands the count of those users who have performed some combinatorial action on a day or some specific day.
    In this case, Client ID will be a root node and behave as a unique identifier for each user. It will return the events performed by a particular user, fulfilling the combination requirement.
  2. Targeting a set of audience :
    Implementation of Client ID will give a facility to make a segment based on their activity and can be targeted as an audience to lead conversion. For every business, it is very important to know about the users, their activity and conversion. For example - There are 100 users who have visited your website. They take a set of actions and then exit. Client ID as a dimension will help businesses to find the user journey and these users can be targeted to see through a transaction or lead generation.

A list of ClientID can also be exported to Adwords and various remarketing activity such as personalized recommendation or showing products depending upon their past behaviour.

Looking on the other side of the coin, with the advantages of Client ID, we must also be aware of the limitations that it has. Client ID is a standard dimension of Google Analytics and unfortunately, we cannot use the Client ID in Custom Reports that we use to visualize data according to our requirements. But guess what, we can track the Client ID in a custom dimension and use it in Custom Reports to analyze the data.

Client ID Tracking Implementation

Moving further, lets take a look on how to track Client ID from iOS device’s either in a custom dimension or in an event through Google Tag Manager using the dataLayer method. Follow the below steps :

  1. To send Client ID in GA using dataLayer your app should have GA SDK as well as GTM SDK installed. Follow below mentioned links to install and initialize GA SDK and GTM SDK in your iOS project.
  2. Once SDKs are initialized, one instance will be created of GA Tracker which will be used to get the Client ID. After getting a Client ID a dataLayer instance will be created to push Client ID into a dataLayer.
    Below mentioned code snippet will get Client ID and push it into a dataLayer. This mechanism should be implemented inside the first screen of your application. Write below code in the viewDidLoad method of your ViewController.

                                          OR
    Add the variable clientId in the openScreen DataLayer as mentioned in this blog

    google analytics

    DataLayer push code snippet holding Client ID

  3. Since we are using Google Tag Manager it is necessary to configure a Tag in GTM which holds the setting to track the Client ID in Custom Dimension.iOS

    Tag configuration with setting Client ID in Custom Dimension.

    NOTE:
    The custom dimension for Client ID should be User level scope in Google Analytics. This will help you analyze and understand actions of the user.

With this step, we are now through with implementation of Client ID tracking. Once Client ID starts getting tracked in Custom Dimension, you can generate custom reports and visualize the data as per your requirements.

For any assistance in Google Tag Manager setup or Tag Configuration you can visit our blog  How to Implement Google Tag Manager in iOS Swift - Part 1 of 2 or feel free to leave a comment in the section below.

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

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.

Bot Icon
Bot Icon

Tatvic Bot

Explore About Tatvic and Services