Skip to main content

Application Insights and behavior analytics

Azure Application Insights allows us to understand better how does our application behaves and what is our users behavior. 
Many times you want to know what are the pages that attract users the most, what is the user flow inside your application and that is the retention level. All of this can be gathered using Application Insights that has some key features that enable this.

(1) Session, Events and Users 
Once you activate Application Insights in your application you have a dedicated dashboard where you can have a strong overview related to users (e.g. no. of users), sessions (e.g. pages visited during a session) and events (e.g. how often a certain page was visited). 

(2) Funnels
Used when you have flows and users need to navigate between different sections to be able to accomplish a task (e.g. product ordering). You can define a custom funnel and analyze the users patterns (e.g. how long it took to do a specific step, no. of users).

(3) Cohorts
Are used when multiple events, sessions, or users have something in common. They are grouped together under the same cohorts, enabling us to get more insights related to them. They are build using custom analytics queries, providing us more flexibility from the way how we build and use a cohort. 

(4) Impact
The conversion rate of users can be affected by multiple factors (e.g. load time). These views are created using multiple dimensions like user country, browser, load time to generate reports related to what is the impact on their behavior. 

(5) Retention
Especially for web applications the retention level of users is important. These tool allows us to specify from code events that could help us to identify what does affect the user retention. For example, displaying specific content or adds in different ways or winning a virtual gift (e.g. 5% discount for your next order)

(6) User Flows
Creates a virtual map of how does users navigate inside the application, covering the full lifecycle of the session. You can identify what are the most common flows and users find the content that they are looking for. 

(7) Usage analytics
It is the main entry point when you want to execute queries that combined all other metrics (e.g. counters, sessions, visited page). You have the full ability to write your own custom query that combines all the metrics that are stored by Application Insights, including custom events.

As we can see, Application Insights is not a tool used only to collect metrics, events, and user behavior. Can be used with success to visualize data and understand the behaviors. Even if it has strong integration with PowerBI, from 14 projects where I'm using Application Insights for web solutions, in only 1 case we need to use PowerBI for data visualization. 
The top 3 features of Azure Application Insights that shall be used more are Funnels, Cohorts and User Flows. If you did not have the opportunity until now to play with them you should give them a try!

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...