Google Analytics with Single Page Application(SPA) in VueJs

Google Analytics with Single Page Application(SPA) in VueJs

Google Analytics with Single Page Application(SPA) in VueJs.Google Analytics can be great if you want to know how your SPA is being used. Here's how to integrate it into your Single Page Application.

In the past I used to use the right tool for the right purpose. This led me to employ a lot of tools, and with most turning out to use subscription-based billing, increasing our costs much more that I would have hoped for. So, I adopted a new strategy:

Use as few tools as possible, but use them as much as possible.

When I got to the “How are users using our brand new web-app?” question, the obvious answer was to see how we can use Google Analytics. Their variety of tools and experience in tracking web usage felt impossible to ignore. To top it all off, Google is great with security and performance, and costs are near zero (at least for now).

But how do you track a Single Page Application built in VueJS with Google Analytics? For them, it’s all about page views, referrers and bounce-rate — not really suitable for what we have.

Enter Google Analytics Events

Google Analytics events tracking was pretty obvious, as any kind of interaction with the app was more or less an event.

However, how would we know on which page (or screen) the user triggered that event? One way was to name or categorize the events on the pages that they’re triggered on, but that felt unnatural and prone to issues later down the line.

So, one way was to simulate page views when the user was browsing from screen to screen. This meant that the initial tracking code had to specify that it was not to send a page-view request when the initial application was loaded in the user’s browser.


<!DOCTYPE html>
  <!-- Global site tag (gtag.js) - Google Analytics -->
  <script async src=""></script>
    window.dataLayer = window.dataLayer || [];
    function gtag(){dataLayer.push(arguments);}
    gtag('js', new Date());
    gtag('config', GA_TRACKING_ID, { app_name: 'Monitive Web App', send_page_view: false });
  <meta charset="utf-8">
   . . . . . . .

The important part above is the send_page_view: false bit. This causes the GA code not to send a page view when the app is loaded in the browser window. And we want this because we’re going to send view from our screen-rendering code.

For VueJS, since we’re using vue-router, all we needed to do to send page views when the user was browsing the app was to add an afterEach() event handler:


router.afterEach((to) => {
  gtag('config', window.GA_TRACKING_ID, {
    page_path: to.fullPath,
    app_name: 'Monitive Web App',
    send_page_view: true,

I saved the tracking ID into a global window attribute, so we could define it in one place and use it all around. This also helped set the corresponding tracking ID for development and production environment at deploy time, so that whenever we played around in the development, testing or staging deployments, metrics for production wouldn’t be affected.

There! Now we have page-views in our VueJS SPA.

Next, events. But how do we categorize events? How do we identify which events are more important than others? How do we track error messages that the user is getting, in the context of what a user is doing?

After a few days of brainstorming, the following event categories emerged:

  1. Engagement — Events where the user actually did something in the app: signed in, added a new monitor, updated their profile information, etc.
  2. Navigation — These are events that caused the web-app to navigate to another page: tapping the logo, sections in the sidebar menu, going back from a details page, etc.
  3. Interaction — These indicate user interaction with an element on the page, which doesn’t update any data in the backend. For example, the user expanded a section, toggled a checkbox or opened the sidebar menu.
  4. Experience — These are events that the user experienced, usually after something they did. An example ‘experience’ event is when the user received a validation error, or a pop-up question came up asking for confirmation. These don’t fall on any of the above categories and we’re sending them to Analytics mentioning that they’re non-interaction events.

Since these were going to be added all over the place in our code, we crafted a set of four helper mixin methods, to be easily used anywhere:


const helpers = {
  methods: {
    gaNavigation(action, label) {
      gtag('event', action, {
        event_category: 'navigation',
        event_label: label,
    gaEngagement(action, label) {
      gtag('event', action, {
        event_category: 'engagement',
        event_label: label,
    gaInteraction(action, label) {
      gtag('event', action, {
        event_category: 'interaction',
        event_label: label,
    gaExperience(action, label) {
      gtag('event', action, {
        event_category: 'experience',
        event_label: label,
        non_interaction: true,
  }, // §.methods

Because most of the events where navigation clicks on various links or buttons, we also have quick helper methods for these:


gaClickLink(label) {
  gtag('event', 'click_link', {
    event_category: 'navigation',
    event_label: label,
gaClickCta(label) {
  gtag('event', 'click_cta', {
    event_category: 'navigation',
    event_label: label,

Now, if we need to track a navigation event, we could just do this in any Vue template like this:

<router-link to=”/dashboard” [@click](”$root.gaClickCta(‘open_dashboard’)” />

Or in a method, with something like:


methods: {
  submit() {
    // ...submit code

What I actually did was to first list all the events that I wanted to track for each screen, and then add them into the code. Having a list first helps answer the question, “What do I want to track?”

Screen View Events

Although I haven’t found much documentation on this subject, it seems Google Analytics has some support for tracking SPA by sending a special kind of event called ‘screen_view’. For me, it wasn’t clear where exactly I could see screen view information and what the difference was between page view and screen view, so I added the screen_view event along with the page view event, in the afterEach() event handler:

gtag('event', 'screen_view', {

My purpose with this was to see in a few weeks or months if this brings valuable information, or if it is in any way better than the pseudo-page view events.


Having all this set in place brings great value in learning how users use our application. Google Analytics does a wonderful job at segmenting visitors and users. It is providing lots and lots of useful information such as geographic and technological statistics about visitors and users.

This type of information never replaces a good, healthy chat with the customers, but it does help identify what features or interface elements they’re using or not using, what devices are they using Monitive from and how much they engage with the app.

This is especially useful when deciding on what to remove from the app, which buttons or links aren’t visible enough, and what repetitive tasks they are performing, thereby allowing us to improve the interface and the whole user experience altogether.

What are the differences between the various JavaScript frameworks? E.g. Vue.js, Angular.js, React.js

What are the differences? Do they each have specific use contexts?

What are the differences? Do they each have specific use contexts?

Ember.js vs Vue.js - Which is JavaScript Framework Works Better for You

Ember.js vs Vue.js - Which is JavaScript Framework Works Better for You

In this article we will discuss full details and comparison of both Ember.js and Vue.js

JavaScript was initially created to work for web applications. But today they have become the favorite of mobile app developers. Most of the developers prefer to work with frameworks based on JavaScript. It simplifies coding. You can use JavaScript with almost any framework.

The use of a particular framework will decide how easy and fast it is to create the app. So, you must choose the best one suited for the app that you are planning to build. You must make a wise choice so that you benefit in the end. Among the crowded market, two of the frameworks stand out. We will make a comparison between Ember.js and Vue.js.

Why Do You Select A Particular Framework?

Before we start comparing the two frameworks, we should understand the factors that lead to the choice of a framework. Each developer chooses a framework before he or she goes to work on an app. Let us see the reasons for the selection.

● The codes must be easy to understand and transparent.

● The framework should give the maximum power with the least amount of coding.

● The framework should provide a well laid out structure to work on.

● Does the framework support an in-built router or an external plug-in router?

● The framework should be able to transfer more data on a full page-load so that it becomes a single-page app. A single-page app is more beneficial for the application.

● In single page architectures if there is a need for users to share links to sub-screens within the interface, then the framework should have the capacity to route based on the URL.

● A tighter template option can help in enabling two-way binding.

● The framework should not conflict any third-party library.

● Testing the codes inside the framework should be easy.

● The framework should provide the HTTP client service for AJAX calls

● The documentation is essential. It should be complete and up-to-date.

● The framework should be compatible with the latest version of the browser.

● The framework has to fulfill the above conditions for easy construction of the app. You must ensure that the framework you choose meets the conditions.

Vue.js Explained

Developers are always looking at new frameworks to build their apps. The main requirements are speed and low cost. The framework should be easy to use by even new developers. You should be able to use it at low cost. Other considerations are about simple coding, proper documentation, etc.

Vue.js combines a lot of good when it comes to software language for web app development. The architecture of Vue.js is easy to put in use. The apps developed using Vue.js are easy to integrate with new apps.

Vue.js is a very lightweight framework. It makes it fast to download. It is also much faster than other frameworks. The single-file component nature of the framework is also beneficial. The size has made it very popular.

You can further decrease weight. With Vue.js you can separate the template-to-virtual DOM and compiler. You can only deploy the minified and zipped interpreter which is only 12 KB. You can compile the templates in your machine.

Another significant advantage of Vue.js is that it can integrate easily with existing applications created with JavaScript. It will make it easy for using this framework to make changes to applications already present.

Vue.js also integrates easily with other front-end libraries. You can plug in another library and make up for any deficiency in this framework. This feature makes this tool a versatile one.

Vue.js uses the method of rendering on the streaming-side server. You can render your component and get a readable stream. You can then send this to the HTTP server. It makes the server highly responsive. Your users will get the rendered content very quickly.

Vue.js is very SEO friendly. As the framework supports server-side rendering, the views are rendered directly on the server. The search engines list these.

But the most important thing for you is the ease with which you can learn Vue.js. The structure is elementary. Even new developers will find it easy to use it to build their apps. This framework helps in developing both small and large templates. It helps to save a lot of time.

You can go back and check your errors very easily. You can travel back and inspect all the states apart from testing your components. It is another important feature as far as any developer is concerned.

Vue.js also has very detailed documentation. It helps in writing your applications very quickly. You can build a web page or app with the basic knowledge of HTML or JavaScript.

● Vue.js has pure architecture. It helps in integration with other apps

● Vue.js is lightweight and fast. It can be made lighter by deploying only the interpreter

● You can separate the compiler and the template-to-virtual DOM.

● Due to smooth integration, you can use this to make changes to existing apps

● To make up for any shortfall, you can plug-in any library and makeup.

● As Vue.js uses streaming-side server rendering, your users can get quick responses.

● The server-side rendering also helps in being ranked higher by search engines.

● It has a simple structure. Easy to use for any new developer

● You can go back and check and correct your errors.

● You can check all the existing states.

● Detail documentation also helps build the web page or application very quickly.

Ember.js Decoded

Ember.js is an MVVM model framework. It is open-source software. This platform is mostly used for creating complex multi-page applications. It maintains up-to-date features without discarding any of the old features.

With this framework, you have to follow the architecture of the framework strictly. The JS framework is very tightly organized. It reduces the flexibility that other frameworks might offer.

There is a very refined and developed control system for its platforms and tools. You can integrate it with the new version with the tools provided. There is strict guidance about avoiding outdated APIs.

You can understand Ember’s APIs easily. They are also easy to work. You can make use of highly complex functionalities simply and straightforwardly.

The performance is better as similar jobs are processed together. It creates batches of similar bindings and DOM updates to improve the performance. It means that the browser needs to process them in one go. It will avoid recomputing for each task, wasting a lot of time.

You can write the codes in a simple manner and modules. You can use any of Ember’s APIs. It is possible due to the presence of Promises everywhere.

Ember comes with a well-written guide. The API is recorded in a useful manner. It is a front-end framework that is loaded. Ember has a router, pipeline, services, etc. of its own.

The basis for views, controllers, models, and framework is the Ember Object Model. All components come from the same objects. The framework is firm and steady. The reason is that all elements have similar jobs and characteristics.

Ember has made the general application, organization, and structure clear so that you don’t make any mistakes. You will have no chance to complicate the application unnecessarily. If you have to go out of the defined limits, you will have to force your way out.

The language used for templating in Embers is Handlebars. This language helps Embers to keep its logic out of view. The clean syntax of Handlebars makes it easy for you to read and understand the templates. Handlebar templates are faster to load.

Another advantage you gain from Handlebar is that you don’t have to update your template every time you add or remove data from the page. It will be done automatically by the language itself.

A community that is continually improving the framework supports Ember. They are updating the framework with the latest technology. They also make sure that backward compatibility is possible.

● Ember.js is an open-source MVVM model framework suitable for complex multiple-page applications.

● It offers both the latest and old features.

● It has a very tightly structured framework which doesn’t offer much flexibility

● A very refined control system helps you to integrate with new versions without any problem.

● There is strict guidance about avoiding outdated API versions.

● Ember’s APIs help you to use complex functionalities in a simple manner

● There is no recomputing for each task as the framework allows the browser to do similar functions together.

● Promises allow you to write modular and straightforward code using any API of Ember.js.

● Ember.js is a fully loaded, front-end framework.

● The framework is stable because all components have the same functionalities and properties.

● It has well-defined limitations which will prevent your complicating your application

● Handlebars, the language used by Ember.js allows you to read and understand templates easily. It also helps to load the templates faster.

● Handlebars will ensure to update the template every time you add or remove data.

● Ember.js has an active community that updates the framework regularly and facilitates backward compatibility.

A Comparison Between Ember.js And Vue.js

This article intends to compare the features of both frameworks. Let us see how the characteristics of these frameworks compare. It will help you to make use of the right framework for your web application.

When you need a modern engine for an old application, it is Vue.js which will help you. It combines the best properties of other frameworks. Vue.js is a developing framework. A ready-to-use library of interface elements does not exist. However, many third-party libraries can help you.

Ember.js offers you a well-organized and trustworthy framework. When the development team is big, this is the framework that suits best. It allows everyone to understand the written code and contribute to a common project. The technology will be up-to-date, and the platform will be stable.

Vue.js can help you use the syntax of different kinds. It helps in writing the codes with ease. It is also an SEO friendly framework. Ember is a fully loaded front-end framework and can help you develop the applications very fast. But it is not suitable for developing small projects.

It is not easy to say this is better than that. It will depend on what kind of project you have undertaken. Both have their pluses and minuses. The below table will help in a better comparison.

Final Thoughts

It is not easy to conclude as to which is better. It all depends on the application that you want to develop. Both frameworks are developing. Both are getting updates. Both the communities are working on the frameworks.

While Vue.js is more comfortable for writing codes, Ember is a full-stack framework allowing the development of apps very fast. It is suitable for big projects. It is too complicated to be used for smaller projects.

We hope you had a great time reading this article. If you’ve any questions or suggestions related to this blog, then feel free to ask them in the comment section. Thank You.!