Hello There!

Lorem ipsum dolor sit amet, consectetur adipiscing elit,

 About Jitendra Verma

Jitendra Verma is working as campaign manager in Tatvic. He has been running successful digital marketing campaigns for the top e-commerce giants.

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!

How to Implement Google Tag Manager in iOS Swift - Part 2 of 2

iOS with Swift

In the previous blog post, we saw how to create a GTM container, configure a tag and publish it. In this post, we are going to tackle the specifics of creating an iOS app and integrating it with GTM.

We won’t get into the details of how to create an iOS project in Xcode.Although if you have any queries or you’re facing a difficulty in doing so, please write to us and we’ll be able to help you out. Moving on, let us check out how to integrate Google Tag Manager pod in your project.

Adding GTM to Xcode Project

Close Xcode project, open terminal, navigate to your root directory of your project and write below command. This will create a podfile in your project.

Google Tag Manager

Open podfile and include Google Tag Manager pod in it.

iOS with Swift

Close podfile, and in terminal write below command to install the pod in your project.

mplement google tag manager in iOS

Great! Google Tag Manager is installed in your project. Now open your project in Xcode using xcworkspace file.

Adding a Bridging Header File

Create a bridging header file in your project. In Xcode, go to File -> New -> File, select Header File and create it within your target to keep it associated with your project files.

tag manager for iOS apps

Open the file in editor and import below mentioned headers in it.

app analytics

Add Objective-C bridging header to Build Settings. Go to Build Settings, select All and Combined and search for the bridging header. In the value field of key containing Objective-C Bridging Header, enter header filename Bridging-Header.h.

app analytics

Adding a Default GTM Container

Go to the directory where you downloaded GTM container, drag downloaded container and drop it into your Xcode project. One window will pop up, select ‘copy items if needed’ checkbox and add container to your project’s main target.

Google Tag Manager

Initializing GTM in Xcode Project

Open AppDelegate file and following changes in it.

Confirm to TAGContainerOpenerNotifier protocol.

iOS with Swift

Implement containerAvailable method.

iOS with Swift

In didFinishLaunchingWithOptions method, add below code.

implement google tag manager in iOS

GTM is initialized in your app now. Let’s fire a screen view datalayer.

Tracking a Screen Open Event

Go to your main screen’s view controller file, from viewDidAppear method fire a dataLayer to push a screen view as shown below.

tag manager for iOS apps

Viewing The Logs in Debug Area

In Xcode, go to Product -> Run to build and run your project. Once the build runs on iOS device or simulator, you will see openScreen event being pushed in Debug Area as shown below.

app analytics

Best Practices for Flawless Tracking
  • Create one constant for UA ID in GTM and use it as tracking ID for all Universal Analytics Tags instead of hardcoding UA ID value in each Tag.
  • It is best to push a screen view when screen actually appears to user hence push a screen view datalayer from viewDidAppear method.
  • Google Analytics is case sensitive. If any letter case changes while pushing values to datalayer, Google Analytics will consider it as a different value and in reports it will appear in a different row. So it is best to keep all values in any pre-defined cases and use those same to push into datalayer every time.
Concluding Thoughts

Installing GTM library in Xcode project and initializing it with adding a default container is all you need to ensure track screen views, events and other tracking available through GTM. While adding a GTM pod in Xcode project, it is preferred to add a library of version  ‘3.15.0’ to utilize datalayer functionality. If you have made any changes in the container, published it through GTM dashboard, then those changes will be reflected in the app within 12 hours of publishing that new container. It is not mandatory to include a container in app every time you publish a new version of it through GTM dashboard.

If you have any queries, comments or feedback for the post, please leave us a comment in the section below. Our team shall be sure to get back to you.

How to Implement Google Tag Manager in iOS Swift - Part 1 of 2

iOS with Swift

iOS with SwiftIn today’s era of mobile analytics, the implementation of the analytics with your mobile apps is extremely vital. From the analytics implementation survey carried out amongst a few enterprises, it is clear that they feel it’s very complicated to integrate analytics into their mobile app. Well, to make things simpler, Google has blessed us with their awesome tool that we all know as the Google Tag Manager. It’s a really compelling addition for the developers to integrate Google Analytics on any platform.

I am going publish a series of 2 blogs that will help you to integrate Google Tag Manager in iOS with Swift and get your data flowing in Google Analytics. In this blog post, we shall cover the basics for getting our tags ready and publishing container with Google Tag Manager.

Creating GTM Container

Create a Tag Manager account from tagmanger.google.com or use existing if you have created one already.

Under that account, create an iOS legacy container. Select container type iOS, SDK version Legacy iOS, give an appropriate name to the container and hit create button.

 

Google Tag ManagerYour container is now created! You can create tags, triggers and variables.

Let’s create a Screen View tag in the container - which should fire when any screen of the app opens.

Creating a ScreenView Tag

Go to Workspace -> Tags, and click New button.

mplement google tag manager in iOS

 

Now you will see two cards on your dashboard, Tag Configuration and Triggering. In Tag Configuration card you should set-up everything that is related to the tag that you are creating. Whereas for Triggering, you will create a triggering event on the occurrence of which above created tag will fire.

Select Tag Configuration card and select Universal Analytics tag type. Configure a tag as shown below.

tag manager for iOS apps

 

Select App View as track type since you are creating a screen view tag. Under Tracking ID field, set Google Analytics property ID. Click More Settings -> Fields to Set -> Add Field to add one key-value pair in the tag, a key will be the built-in variable called screenName and value will be {{screenName}} which is the datalayer variable that we shall cover as we move forward in this post.

Creating a Trigger

Now select the Triggering card and click ‘+’ icon from top right side of the layout and create a trigger as shown below.

 

app analyticsSelect Custom trigger type and configure this trigger to fire on some events when event name matches ‘openScreen’. Give appropriate name to trigger and save it. The “Trigger” is now added to your tag, give an appropriate name to tag and save it. This tag will fire from the app when datalayer event name matches ‘openScreen’.

Now create a datalayer variable, screenName, which you are using in your tag.

Creating a Variable

Go to Variables and select New under user defined variables section. You will see Variable Configuration card, select it and choose Data Layer Variable and configure variable as shown below.

 

Google Tag ManagerSpecify datalayer variable name as screenName using which this variable will be referred to. Check Set Default Value checkbox and set Default Value as NA so whenever this variable is used and its value is not defined then the default value will be pushed into the datalayer. Give appropriate name to this variable and save it.

The Screen View tag is configured perfectly, you can publish the container now.

Publishing the Container

Hit Submit button from the top right corner of the screen, a new layout will pop up. From submission configuration card, select Publish and Create Version and give a descriptive name to the version as shown below.

 

iOS with SwiftHit Publish button. That’s it! Your container is created.

Download the Container

You need to download a container as you shall be required to include it in your app as a default container. Go to Versions tab and click on Actions button for the container version which is Live and select Download option.

 

tag manager for iOS appsYour container published is with one Screen View tag and you have downloaded it now. You can include this container in your app as a default container.

Concluding Thoughts

Configuring an event or any other type of tags are also simple just like the process we described above. As a part of my closing thoughts, whenever you add, modify or delete something from the container, make sure you don’t forget to publish it, otherwise, the changes you have made will not reflect in your users’ app. As opposed to a website, in the case of an app, GTM takes a maximum of 12 hours to update the container in the app after publishing it. If your app is in the development stage, you can preview the container, or download and include it to update in your app. Before talking about updating the container, I shall take you through the process of integrating GTM SDK in the iOS app, in my upcoming blog post. Check out the second part of this blog series for getting started with Datalayer.

Key Parameters to Understand in Google AdWords Analytics

Google Adwords

Google Adwords
Google AdWords has been one of the most established channels for Digital marketers to drive traffic to their websites.

But a lot of the time, the poor configuration of Google AdWords with Google Analytics, leads to discrepancies in the measurement of your Google AdWord campaigns in Google Analytics.

With this blog, we aim to provide solutions that will prove to be beneficial in improving the accuracy of your data collection.

  • Reduction of discrepancy in Clicks vs Sessions metric in Google Analytics reports
  • Minimizing (not set) value in Google Analytics landing page report
  • Avoiding exclusion of important AdWords Data in Google Analytics

The below list showcases a checklist that a Digital Marketer should refer to so as to avert the problems of inaccurate campaign data.

Ensure your Google AdWords account is linked correctly to Your Google Analytics Property

Being one of the most basic issues that digital marketers face while running paid campaigns, the discrepancy is observed when you are unable to view the correct AdWords Campaign report in Google Analytics. The reason behind the inaccurate report could be a URL that is not tagged with UTM parameters or an incorrect integration of AdWords with Google Analytics. Below image shows which AdWord accounts are mapped to your Google Analytics view. The list that you see highlighted in the screenshot, shows whether or not the right Google AdWords account is linked to your Analytics profile view.

Below image shows which AdWord accounts are mapped to your Google Analytics view. The list that you see highlighted in the screenshot, shows whether or not the right Google AdWords account is linked to your Analytics profile view. Be sure to verify that the

Be sure to verify that the AdWords customer ID that is on the top-right screen matches the ones available here in GA below.

AdWords Campaign

Check for the GCLID parameter: It should not be dropped

GCLID (Google Click ID) is used by Google to pass information back and forth between Google AdWords and Google Analytics. Look out for the following list of precautions to be taken in order to avoid the dropping of the GCLID parameter:

  • URL is not redirected from one page to another page
  • Destination URLs are case-sensitive. Hence, make sure that you’ve entered the exact page URLs during configuration.
  • The length of the GCLID parameter should be less than 100 characters.
  • Check if the analytics tracking code is set up properly on your web page
Confirm the Auto-tagging function is proper

To check if auto-tagging is enabled, follow these steps:

  • Sign in to your Google AdWords account
  • Click the gear icon and select Account settings
  • Make sure you’re on the Preferences tab and click Edit in the Tracking section

Check whether the Auto-tagging checkbox is (enable) or clear (disable) as per the below image.

auto tagging

When auto-tagging should be disabled?

If you are running a campaign by adding custom parameters to your destination URLs manually and would like to have control over these parameter names, you should, by all means, disable auto-tagging. However, one of the constraints is the limited number of custom parameters that we are allowed to set.

For Example:

How can you differentiate 2 campaigns like a product campaign and a brand campaign?

We need to use custom parameters that can differentiate the content and enable us to decide which one is a better campaign. In the current marketing scenario, any digital marketer would find it ideal to implement custom parameters. Unfortunately, auto-tagging doesn’t allow to add of custom parameters hence, tagging manually is a more efficient approach to ensure that you have the correct picture of your campaign performance.

Track all your landing pages of your campaign Ads

Even though you might already be running campaign Ads, it is still observed that incorrect tracking is a common mistake that Digital Marketers tend to make. This eventually leads to (not set) in the Google Analytics report.

To make sure that you are tracking all landing pages for your campaign, tag all the destination URLs in your Ads correctly. Moreover, confirm that your landing page URLs are not being redirected to any other page.

Review Filters That Might be Eliminating AdWords Data

Check if there are any filters that you might have configured in Google Analytics. Some of these might lead to exclusion of AdWords data in GA which in fact needs tracking.

All you have to do is sign-in to your Google Analytics account, and check for view level filters. Review filters that excludes traffic from either a landing page or from a host name. These should ideally should be part of your Google Analytics data while running Adwords campaigns.

To Conclude:

Take help of this checklist to achieve the right linkages and proper configurations between AdWords and Google Analytics. Once this is correctly done, you shall be able to utilize these benefits to their fullest potential from Google Analytics reports like campaigns and cost analysis of AdWords all at one place.

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

How to make Email Re-marketing more effective using Google Analytics data

Google Analytics data for email ca

 

Email marketing campaigns are run by thousands of businesses of all sizes across the globe. Email forms a stable foundation for digital marketing. It’s a channel that drives results for businesses.

But, do you know you could use Google Analytics data for email re-marketing?

Let’s take a use case where we can send out emails to either converters or non-converters using GA segments. For converters, up selling or cross selling can be the objectives, whereas for non-converters, the objective could be to prompt them for completing the transactions or generating awareness.

Now let’s see how it’s done.

Step 1:

Make Email Marketing campaigns effective
We need to make sure that we are capturing Client IDs for non-converters and converters in Google Analytics as well as back-end. This is important because we match the Google Analytics Client IDs with back-end Client IDs and send emails to users whose email IDs are recorded in the back-end. Here, the Client IDs serve as a key to connect Google Analytics and email IDs which are stored in the back-end.

Step 2:

Email remarketing using Google Analytics data
Now, we’ll create segments for converters or non-converters or both. For converters, we can apply a condition like “include users who have visited the Thank You page”. For non-converters, we can apply a condition like “exclude users who have visited the Thank You page”. (More on creating a re-marketing audience by integrating Google Analytics with CRM here)

Step 3:

Google Analytics remarketing
After creating segments, we need to create a custom report where we can extract Client IDs after applying the particular segment. Once the Client IDs are there for a particular segment, we can match them with the back-end Client IDs, against which we will get the email IDs.

Step 4:

email remarketing with Google Analytics data

Now, we just need an access to a platform through which emails can be sent. Here, we need to emphasize on the content and subject line. The subject line should be attractive which drives the attention of the users. The content should be applicable to the segment which we are targeting. Basically, we should not send up-selling content non-converters as they did not transact earlier for a lower amount as well.

Here is how we can make our email campaigns more effective:

  • Use of segments:

    We should always try to segment the Google Analytics data for Email Targeting. Create segments of converters, non-converters or users who completed a specific journey on the website or App (e.g. users who just viewed home page, users who viewed product page, users who actually added product to the cart, etc.). The selection of segment should be based on your marketing objective. If the objective is to drive awareness about your brand, then the segment of users who viewed homepage will be valuable. If the objective is to show discount benefits, then the segment of users who added products to the cart will be relevant.Make Email Marketing campaigns effective

Image Source: Zapier
  • Content Customization:

    Personalization is key. We tend to appreciate emails more if they’re personalized and of our interest. If the Email creative is customized, then there are high chances of better Email Click Rate. Suppose, if a brand has been endorsed by a particular celebrity and if his image is present in the promotional email, it can create an impact on the campaign’s performance. The names, email IDs and phone numbers stored in the CRM data can be used to develop content as well.

  • Subject-Line Selection:

    Studies show that subject lines fewer than 10 characters long have an open rate of 58%. Thus, having a concise subject line makes sense. In order to craft a personalized subject line to obtain a high Email Open Rate, parameters like name, phone number, name of the product which they added to cart, etc. can be used in the subject line. This information will already be available in the CRM data.

Email remarketing using Google Analytics data

  • Best Time for Emails:

    While many a quality email may be built during business hours, the ones with the best open rates aren’t being sent from 9 to 5. The top email strategy is to send at night.
    Experian Marketing Services found that the time of day that received the best open rate was 8:00 p.m. to midnight. This block not only performed better for open rate (a respectable 22 percent) but also for click through and sales.

  • Send Emails On Weekends:

    While not as overwhelming a winner as the 8:00 p.m. to midnight time of day, Saturday and Sunday did outperform their weekday counterparts in Experian’s study of day-of-week performance.

Conclusion:

A little smart work in terms of maintaining client IDs as the primary key in Google Analytics and CRM data will help in fetching e-mail IDs of the segments that we want to target. Targeting the segments with appropriate content will help in achieving more reach, which, will eventually help your organization increase its revenue. Have any ingenious email remarketing tips? Drop a comment below! For help in launching and monitoring your email campaigns, contact us here.

Google Analytics Training Concepts Simplified

GA

As a Google Analytics 360 reseller, our job entails visiting a considerable number of companies that include e-commerce, media & lead generation websites. We also train Google Analytics users i.e. Marketing, Product & Analytics teams, and a majority of these mostly do not have formal technical qualifications. Drawing from our experiences, we thought it would be interesting and, hopefully, useful to a larger audience of users who do not have a technical background. Explained below, are a few Google Analytics concepts with real-life (offline) examples that everyone can easily relate to.

What you know about offline business, also applies to online business…

Analytics System

Google Analytics key termsOffline: Imagine you’re the owner of a retail store where people come and buy different products. To optimize the products, inventory, and look and feel of the store, you need to know where your visitors come from, and what activities they perform in the store. Hence, you appoint a consultant
who will monitor, collect and analyze this information?

Online: For an online business, Google Analytics plays the role of the consultant you’d hire to monitor these activities for your website and/or mobile app. Sheer large volume, complexity, and velocity of data in an online business require a sophisticated tool like Google Analytics.

Google Analytics term definitionsUser Identification

Offline: Monitoring a customer in an offline store is a tedious job. Some retail stores use loyalty cards to keep track of their user’s activities. These cards generate a unique ID for each customer and store the data in CRM systems like HubSpot.

Online: Google Analytics generates a unique cookie named _ga, which stores each user’s unique ID and subsequently, all the activities of the user are attached to this unique ID.

Returning Users

Offline: Once a customer is given a separate identifiable number by way of a loyalty card, the moment he/she returns to the store the next time, the system identifies him/her as a returning customer through the unique ID number in CRM.

Online: Identifying returning users online is very easy. If the cookie is already present in the browser, the user is NOT a new user but a returning user.

Google Analytics training termsSessions

Offline: The period during which your customer remains in the store is a visit or a session. Sounds simple! But now, consider a scenario where he/she gets a call from a friend and stops the shopping activity and resumes after 5 minutes. Would you consider that as two different visits? Of course, no.

Online: Similarly, the time in which a user remains in the system is a session. The session ends when the user leaves the website. However, an interesting factor here is that, by default, Google Analytics sessions continue for 30 minutes on inactivity. So, in case, while shopping online you close the browser and open it again within 30 minutes, Google Analytics is smart enough to record only one visit instead of two. But watch out! Google Analytics ends the session at midnight i.e. at 12 AM.

Google Analytics definitionsHit Type

Offline: Each time a user visits the store, he/she performs activities like viewing the products, comparing them, using signboards, inquiring with a customer care executive, using gift cards, and finally, purchasing the product. He may not necessarily buy though, and may simply leave the store without any transaction.

Online: Similarly, here, the user does a lot of interactions and activities like PageViews, using the search option, using the filter option, using the navigation menu, clicks, mouse hover, and many types of E-Commerce activities like Product Impressions, Product Clicks, Add-to-cart and Purchase. All these individual interactions are ‘Hit’ in Google Analytics. Each of these hit types carries different data to Google Analytics. A user might have one or many sessions during a period and one or many hits in each session, however vice versa is not possible.

Closing Thoughts

Often, using real-life examples makes it easy to communicate ideas. This was a small attempt to start the thought process to understand the technical concepts through real-life examples we generally face. Feel free to add to the list by commenting below & we’ll include your examples in our next series on the same topic (with all the attribution to you, of course!)

Google Analytics Exception Tracking Guide for IOS & Android Apps

Exception Tracking in apps

Google Analytics Exceptions Tracking: Introduction

As an app developer, unexpected production issues can affect your product’s reputation if not resolved quickly.  Suffice it to say, they can ruin your dinner and weekend plans!

Exception Tracking, a method for automatically detecting and responding to exceptions in the target application as they occur, can save you hours (or even days) of troubleshooting! A clear policy on how to track exceptions saves you time in diagnosing, reproducing, and correcting the issues. By using Google Analytics Exception tracking you can spend more time fixing the issue, rather than finding the issue.

This post guides you on how to track exceptions for Android and iOS apps in Google Analytics using Google Tag Manager. After reading this blog, you’ll be able to generate a report called “Crashes and Exceptions” in Google Analytics.

Let’s begin!!
Two major steps to be followed to implement Exception Tracking are:

  • GTM Configuration
  • DataLayer Implementation

GTM Configurations:

The first step includes creating a tag, a trigger, and variables in Google Tag Manager (GTM) Interface. This tag will fire when specified rules are triggered.

Create a GTM tag that fires on “exceptionOccured” trigger.

Note: Tag configuration will be the same for both Android and iOS platforms.

  1. Create 2 variables “exception_description” and “is_fatal” as shown in the following screenshots to collect the exception description and to check whether it is fatal.

Datalayer1
Datalayer2

2. Create a trigger that fires on the custom event called “exception_occured”.

trigger

 

 3. Create a tag with track type “Exception” and add “Exception Description” and “Is Fatal” variables to the same.

tag

DataLayer Implementation:

Once the tag is created in GTM and the container is published, you will need to push a DataLayer snippet from the app. The snippet consists of key-value pairs where the keys are GTM triggers and variables which are defined in the Exception Tracking tag and the values are assigned from the app to specific keys

When an exception occurs in the app, you must be capturing it in the catch block where you’ll also have the description. You’ll need to push a DataLayer from the catch block.

Here’s how it works!

Follow the steps mentioned below to implement the DataLayer snippet in your Android or iOS app.

For Android:

  1. Create a method to push an event and exception to DataLayer.
    datalayer syntax
  2. SetDatalayer event names as “exceptionOccured” & push the two other variables as shown in the above image with the same event.

  3. Call this method (as shown in the below image) inside each catch block of your application.
    calling datalayer push

For iOS:

Push the “exception_occured” event with 2 DataLayer variables from the catch block as shown below:

ios snippet

When the above code executes, you can check that the exception is being sent to Google Analytics in the logs as shown below image.
logs

 

Google Analytics Report Visualization:

Now let’s have a look at the data in Google Analytics.

Open the “Crashes and Exceptions” report by selecting Behaviour -> Crashes and Exception from the left panel in Google Analytics. This report, in a default manner, shows all crashes and exceptions next to app versions.

The GA report will be visible as shown below:

report
So now you can track all of your application’s errors easily and fix them as soon as possible by spending less time finding & more resolving them. 

Google Analytics can also give you different parameters like Mobile Device Brand where these exceptions occur. This will be extremely useful for a developer to regenerate those issues and solve them quickly.

Keep coding. Enjoy 🙂

For any assistance or more details on Exception Tracking, please drop us a message in the comment section below and our experts will be glad to assist you!!

An Exclusive Guide on Building Your First Lead Scoring System

Lead-Scoring-Meme

 

    • Do you keep doing cold calling on your old database with out any directions?
    • Do you have a high flow of leads but struggle at prioritizing them?

 If the answer to any of the above question is yes, the potential solution to your problem could be a lead scoring analysis.

Lead Scoring Analysis helps sales and marketing professionals leverage their new & existing leads and segment them into different groups like warm, hot and cold. This helps them in identifying those people who have shown high interest in their product/service and are likely to convert.

What is Lead Scoring?

According to Sirius Decision, Lead scoring is defined as “A methodology used to rank prospects against a scale that represents the perceived value each lead represents to the organization. The resulting score is used to determine which leads a receiving function (e.g. sales, partners, teleprospecting) will engage, in order of priority.”

To Sales & Marketing teams, it gives a clear idea of how many people are on the top of the funnel (started showing interest in your resources) and how many are ready to be pushed for a sale.

The New Buying Behavior & Why Rethink Your Sales & Marketing Process

Nowadays, most of the buyers make buying decision before getting in touch with a sales rep. With excessive amount of information available online, most buyers prefer to do research first hand before getting in touch with any sales representative.

For example, In a research carried out by Google and CEB it was observed that

[Tweet “57 % of B2B buyers had already completed their sales before getting in touch with any sales rep”]

This is completely opposite to the conventional buying behavior where a buyer gets in touch with a sales rep to research about a product/service and then makes a buying decision.

Today, Buyers do not approach any sales representative unless they have some information about the product/ service. Hence, sales reps need some system that can help them identify the list of potential buyers that have engaged well with their products/service in the past and are now ready to approach them.

The objective of lead scoring analysis is to help drive more revenue through sales in accelerated cycles. Lead scoring helps a marketing team about leads to nurture and that need immediate follow up and engagement with sales or channel partners.

Lead scoring when employed - it can provide multiple benefits that all impact revenue generation.  Firstly, lead scoring helps marketing team to evaluate and improve the effectiveness of a campaign and content strategy.  Scoring helps sales focus on the priority opportunities that have the best chance of closing in the shortest period of time.  Scoring impacts how effective sales forecasts are as well.

In a study by Eloqua, it was found that

[Tweet “Deal closed rate increased by 30 percent when a B2B organization uses a Lead Scoring System”]

Lead Scoring Basics:

Lead Scoring is based on two important data points- Implicit and Explicit. When quantified, both these set of data then can be converted to one single lead score for each given lead.

Implicit Lead Scoring:

Implicit Lead Scoring refers to any type of online interaction that a potential buyer has with your website. Some of the most common interactions  include downloading a whitepaper, watching a webinar, reading a blog post, product page visit or a pricing page visit.

Consider an example of Ryan who visits your website and performs the following actions as shown in the table below. On the right hand side of the table, we have scored each of the interactions (on the scale of 1 to 10) based on how this activity shows his sales readiness. The scoring can be done manually or you can use Google analytics page value metric.

Implicit Behavior

Score

Downloading a Resource White Paper +5
Watching a Webinar +5
Downloading a Product Page Whitepaper +10
Pricing Page Visit +7
Reading a blog post +3
Action Item:

· List down your five important implicit behaviors
· Give them a score depending on their importance.

Explicit Lead Scoring:

Explicit scoring refers to the information that your potential buyer provides you on your website i.e. a potential buyer giving you information through a lead gen form. Information such as Company Size, Industry, Location, and Position are used in explicit lead scoring.

You will need a clear idea about your target customer before you give a score to explicit behavior. You should have a buyer persona in your mind to carry out explicit lead scoring successfully. For instance - your target market is USA, Industry - IT and you offer solutions to companies with size 1000+.

Explicit Lead Scoring

Information

Score(out of 10)

Company Size 700 +7
Location USA +10
Industry IT +10
Position Senior Executive +5

As you can see in the above example, we gave the scoring based on our ideal buyer persona giving Location, Industry the highest score.

Action Item

· List down Your Five Explicit Behaviors
· Take out a potential buyer profile from your database
· Score them based on your ideal target audience.

Best Part of Lead Scoring - How to identify the sales ready lead?

The sexiest part of lead scoring is to identify the sales ready lead. Now that we know how to calculate the implicit and explicit lead scoring we can identify the potential buyers sales readiness through this matrix.

 

Considering the matrix, and the example of a potential buyer that we have taken in implicit and explicit lead scoring. The Explicit Lead Score(Demographic Score) was 42 and the Implicit Lead Score(Behavior Score) was 30. So placing the potential buyer in the matrix, we have a clear idea that he is interested in our service and can be passed on to sales representative.

6 Steps To Set Up Your Lead Scoring System:

Follow the below mentioned steps to build you first lead scoring system. Remember that to execute these steps you may need help of your web analyst team & the developer team.

Step 1: List down your explicit factors

Explicit factors refer to the information that your potential buyers provide you explicitly on your website. It includes Potential Buyers Company Name, Company Size, Industry, etc. A good place to start listing down your explicit factors are generally your resource download forms like whitepaper download forms or contact us forms.

 Examples of explicit factors:

  • Company Size
  • Location
  • Industry
  • Position
  • Budget
  • Purchasing Authority
  • Interest
 Step 2: List down your implicit factors

Implicit factors refer to the interaction of the potential buyer with your website content. Your implicit factors may include whitepaper downloads, webinar registrations, e-book downloads or email link clicks. A good place to start listing down your implicit factors will be to start looking at the Free & Gate Resources on your website.

Examples of implicit factors:

  • Whitepaper Download
  • Webinar Registration
  • E-book download
  • Product Page Visit
  • Email Link Click
Step 3: Capture Your Explicit Data from CRM

We assume that you have a CRM system in place where you store the information of your potential buyers. If you do not have a CRM system, you can ask your development team to create a database to store the data of your potential buyers. Once you have all the required explicit data of your potential buyer in one place, you can export them into a spreadsheet.

Note: Your CRM data should be organized in such a manner that it can be mapped against a single visitor id/ potential buyer. This will make it easy for you when you create your lead scoring analysis spreadsheet in step 5.

Step 4: Capture Your Implicit Data from Google Analytics

Implicit factors such as Whitepaper Downloads, ebook downloads, webinar registrations can be tracked using Google Analytics and can be mapped against a single visitor id/ potential buyer. It is great if you have a tracking in place that provides you with this information or else you can always ask your web analytics team to set up a similar tracking  Setting up a tracking will provide you all the implicit factors in one place, which again you need to export into a separate spreadsheet.

Step 5: Combine all your data into single spreadsheet

Now that you have both the explicit & implicit information available in two different spreadsheets, you can create your Lead Scoring Analysis Template. Following is an example lead scoring analysis template (Download Sample Template)

LSA_Template

(Lead Scoring Analysis Example)

Step 6: Start scoring your leads

Now that you have added the explicit and implicit factors into your lead scoring analysis template, you can start scoring your leads based on this data.  To identify whether your potential buyer is hot, warm or cold, you can create a lead scoring model.

 

Where,

Hot - Potential buyer is ready to be forwarded to a sales rep.

Warm - Potential buyer is still in the nurturing stage

Cold - Potential buyer has just started to interact with your online content and is ready for lead nurturing

Various Lead Scoring Situations:

In the example covered in the blogpost, the potential buyer has a high explicit and implicit score. This is indicative of the fact that the buyer has shown interest in our product/service and is also ready to meet our sales rep. Since, this it covers only one scenario, let us take a look at different scenarios you may face while scoring your leads.(I) If the Explicit Score is High and Implicit Score is High

This refers to a situation where a potential buyer has interacted well with your online content i.e. downloaded whitepapers, registered in webinars as well as shown interest in your product by requesting a demo or clicking the product link in the email. The potential buyer is interested in your product and hence can be approached by a sales rep.

(II) If the Explicit Score is High and Implicit Score is Low

This refers to a situation where a potential buyer has interacted less with your online content but shown interested in learning more about your product/ service by asking for a demo or downloading the white paper on the features of your product. Potential buyer is again clearly interested in your product and hence can be approached by your sales team.

(III) If Explicit Score is Low and Implicit Score is High

This refers to a situation when a potential buyer has interacted well with your online content i.e. downloaded eBooks, attended webinar, tweets/share’s your content but has shown least interest in your product (like no visits on your product page or pricing page). In this case the potential buyer is either in the nurturing stage or may be a potential buyer you are targeting and hence can be ignored.

(IV) If Explicit Score is Low and Implicit Score is Low

This refers to the situation when a potential buyer has just started interacting with your online content and has given you some demographic information via an online form. As he has just started interacting with your online content, you will want to nurture the buyer by offering him content that may help him in his research.

Conclusion:

Lead scoring is an important exercise which can improve your overall sales effectiveness. It helps organizations in identifying potential prospects; prioritize leads based on their fit and interest level and  help you understand if a prospects need to fast tracked to sales or to be nurtured.

We hope that the steps mentioned in this post will enable you to build a lead scoring system of your own. Do get in touch with me on twitter or mr*****@****ic.com for any further information you may need and would be great to help you out further.

Bot Icon
Bot Icon

Tatvic Bot

Explore About Tatvic and Services