Blazor with Google Analytics


This is not a post about how to use Google analytics. There are hundreds of books and thousands of articles on that subject. I am going to explain my experience of implementing Google analytics into a Blazor Server application and a Blazor Web Assembly application. The applications are remarkably similar, but there are slight differences that I will point out.

I have implemented Google analytics with HTML/CSS/JavaScript applications in the past. It is straight forward implementation; you place a script on your pages to trigger the events you are interested in tracking. On the main page of the application, you add a script and your Google key to associate the events to your account.

Since a Blazor application is a SPA, Single Page Application, it is a little more involved to set the trigger points in order to log the analytics. Lucky for use there is a NuGet package that will help us with the heavy lifting.


NuGet Package

The package is Blazor-Analytics. It is popular. It adds a component in the application router to manage the trigger requests. In Program.cs you instantiate the service with your Google Analytics Id.

    services.AddGoogleAnalytics("YOUR_GTAG_ID");


To trigger the events, you add a call to your event:

    Analytics.TrackEvent("generate_lead", new {currency = "USD", value = 99.99});

Notice you can provide different properties for each trigger event.

In the _layout.cshtml for Server side or the index.html for the web assembly side, you will need to add a reference to a JavaScript file:

    <script src="_content/Blazor-Analytics/blazor-analytics.js"></script>

I have always stated I want to do everything in C# instead of JavaScript but with several of my recent projects I am starting to understand the power that combining the two technologies can give you. This is a good example. Google Analytics was built with the “normal” web in mind, HTML/CSS/JavaScript, wrapping a C# class around it brings into the Blazor world.


My Implementation

I decided I was going to add Analytics to an existing public web site I had built and published several years ago. I updated it to .Net 6, the latest Blazor release and renamed it to Insprational2. It is a simple web site that is meant to make people smile or think a little. 

I followed the instructions to add the NuGet package to the project. My goal is to capture the page views of the main page. For the Sever Side application I added the following to the index page:

await Analytics.TrackEvent("Inspirational Page View", new {app = "Inspirational", value = "SS"});

The "SS" is to the server-side application.

For the Web Assembly application, I had to move the tracking call to the OnInitializedAsync call:

    await Analytics.TrackEvent("Inspirational Page View", new {app = "Inspirational", value = "WASM"});

For this one, I am setting the property value to "WASM". This should allow me to see the differences between the two applications.


Add Configuration

Once it was published and I verified it capturing data, I decided I was only interested in the analytics information from the production sites. I wanted a configuration value to turn the tracking on or off.

Server-side Application

This was straight forward just using app settings. I used the key:

    "AllowTracking" : true,

Then I added an if check to see if tracking was on before calling it on the OnAfterRenderAsync method.

Web Assembly Application

This turned out to be a trickier since using app settings in a Web Assembly application is not a good security idea. I took the simple path of defining a “Settings” class and adding the property “Allow” tracking. This is a Singleton class that will read in the application settings from the server and be available application wide.

I then added the following code to the OnInitializedAsync method to get the setting, check to see if it is on and if so, call the tracking

    var value = await Http.GetFromJsonAsync<Settings><("data/Tracking.txt");
    if (value != null)
    {
         bool.TryParse(value.Tracking, out allowTracking);
         if(allowTracking)
             await Analytics.TrackEvent("Inspirational Page View", new {app = "Inspirational", value = "WASM"});
    }


Summary

I went through and documented this process because I am planning to using Google Analytics more often moving forward in both my personal applications and customer projects. This provides a sample on how to implement Google Analytics for a Blazor app, Server-side or Web assembly.

This implementation ended up being easier than I had expected mainly because of the nice NuGet package that I am using.


[Blazor-Analytics]

[source code]


Comments

Post a Comment

Popular posts from this blog

Yes, Blazor Server can scale!

Image
From the very beginning of the release of Blazor Server naysayers have incorrectly stated that Blazor Server can not scale.  They usually state that the limit is 5,000 concurrent users. There are several misconceptions and wrong assumptions about their statement.  Let's break it down and get a better understanding of Blazor server-side scaling. What is the "limit" for users When Microsoft talks about the need to scale an application, what they are saying is that when a normal response for any concurrent user is taking longer than 200 ms, the system is not performant and needs to scale. We will accept that definition: If any normal user response is taking longer than 200 ms, the system needs to scale for concurrent users. By a normal response, we are referring to a page get, a post, etc.  Large database access requests would not be included in this measurement. What is scaling There are 2 common ways to scale, scale, out horizontally, and scale-up, up vertically. In our di
Read more

Blazor new and improved Search Box

 Back in March, I posted a new Blazor data grid with a search box ( see post ).  Since then I have found a new and improved search box that I wanted to implement.  The search part is implemented the same.  What I added was the ability for the user to narrow down the search by selecting which field they wanted to search on.  This will help the user find what they are looking for and in a large collection, the search will end up being faster. The goal of making the change was to make the search box a new component and have it handle the UI functionality part. Prep Work Here is the prep work I did before adding the search box: Started with the source code from the post listed above. Upgraded the project to .Net 5 Upgraded the Nuget packages that were out of date. Ensured every build and run. Change to a Component I wanted to create a component for the search box so I could use it in other applications.   1. Create a Folder under UIControls called "SearchBox" 2. Created a new raz
Read more

Blazor Wizard Step Component

Image
 I like using step wizards in my applications, sign-up forms, shopping cart checkout, and complex data entry, but I had not been able to find a wizard step indicator that I liked so I built this one. As it turned out, it was not as hard as I thought it would have been.  There are a couple of key parts you have to keep in mind when using a step wizard, such as: 1. What step am I on? 2. Should the "Prev" / "Next" buttons be enabled or disabled on this step? 3. What kind of visual clues do I show the user? I will walk you through how we answer these questions in this sample project.   HTML The main container has a div that holds the progress divs, one div for each "step" of your process.  Below that we have our "Prev" and "Next" buttons We will need to wire in the on-click events for the two buttons.  The buttons will need to be able to be disabled and enabled via CSS class settings.           <div class="container">       
Read more