You Ask, I Answer: Screen Resolution in Google Analytics?

Warning: this content is older than 365 days. It may be out of date and no longer relevant.

You Ask, I Answer: Screen Resolution in Google Analytics?

Onurcan asks, “I would like to kindly ask a question about that I’m tracking that one of the mobile native app android version in Google Analytics. Why is Screen Resolution show as (not set) in my Google Analytics reports?”

This one’s straightforward, and it’s likely due to your implementation of GA for mobile apps. You’re an ideal use case for migrating to Google Analytics 4, where stuff like this is handled straight out of the box. Web analytics work poorly, if at all, with mobile apps. You should be using app analytics and the app data stream in Google Analytics 4.

You Ask, I Answer: Screen Resolution in Google Analytics?

Watch this video on YouTube.

Can’t see anything? Watch it on YouTube here.

Listen to the audio here:

Download the MP3 audio here.

Machine-Generated Transcript

What follows is an AI-generated transcript. The transcript may contain errors and is not a substitute for watching the video.

In today’s episode, owner, john, I’m guessing that’s how that’s pronounced in Turkish auto.

JOHN asks, I would like to kindly ask your question about, I’m tracking that one of the mobile native app, Android versions in Google Analytics.

Why is screen resolution shown is not set in your Google Analytics reports? Okay, this one’s pretty straightforward.

It’s because Google Analytics for the web is not suited for mobile apps.

Prior to the advent of app plus web, or Now Google Analytics for you need to use Google’s Firebase Analytics for mobile apps, which contain data like that.

Now, with the advent of Google Analytics for all that information should be centralized within ga for your an ideal use case, actually, for using Google Analytics for for collecting this kind of information, because it really is intended for people who’ve got web properties of some kind.

And also mobile apps of some kind, which increasingly, more and more companies have, and being able to cross match between devices, and see what kinds of devices people are using on your stuff.

So let’s take a quick look at this.

Let’s move over here.

So here’s Google Analytics for and where you would set this up as First you go into your admin, and you are going to go do your property settings go away, I’m sorry, you’re gonna go to your data streams.

And you’re going to set up a data stream for each of the versions of mobile app you have.

So you have an iOS data stream.

If you have an iPhone app, you have an Android data stream.

And then you’re going to deploy your Google Analytics for tracking code inside each of those apps, either using an SDK or using Tag Manager.

So just as an example, let’s do a test.

Let’s see.

Okay, let’s register the app.

That’s going to go through and create all the necessary pieces to build a Firebase database by the way, Firebase is actually what Google Analytics for is underneath the hood.

And then you will go through and implement this in side your mobile app, I’m gonna just cancel out of this because this is not something I need to have set up here.

Once you’ve got your SDK tracker implemented inside of your mobile app, then it’s time to head into Google Analytics for to see how is that data being displayed.

So in Google Analytics for your gonna go to the tech section, one of the things people having a lot of trouble with in in ga four is that things are not necessarily obvious.

at first blush where everything is this is the the technology section, you can see it defaults to things like browsers, scroll down, choose screen resolution.

And then you can start getting, obviously, once your mobile app is all set, you can start getting a sense of what size screen people are looking at your stuff on the web.

Now, you may want to add some additional clarity as to what type of device it is that somebody’s working with.

So let’s go with device category access good device.

I’ve got a bunch of not sets there.

Why? Because it is Firebase Analytics.

And this is I’m using my web stream.

So I’m gonna have a whole bunch of not sets here because it’s not available, however I can for the web, do things like operating system.

And they could not start to see windows, Macintosh, etc.

and go here, go to Device brand, Apple, Google, etc.

So now starting to get a better sense of the different types of technologies.

Remember, because this is Google Analytics, four is a blend of both web and mobile, you’re going to get some data points, some devices and other data points or not, depending on whether you’re looking at at the data from a an app data stream, or a web data stream.

It’s not as you saw, there’s gonna be some things but there’s gonna be gaps.

Things are simply not in there.

And that’s okay.

As long as you understand what you’re looking at is, is the information you need to make choices about how you’re going to track and ultimately, what kinds of technology you deploy to make the best user experience at its core, This is Firebase Analytics, which means that it is well suited for mobile apps.

So to solve that screen resolution, not being shown in ga in your ga switch to ga for and get it deployed.

If you got any follow up questions on this stuff, please leave them in the comments box below.

Subscribe to the YouTube channel on the newsletter, I’ll talk to you soon.

Take care what helps solving your company’s data analytics and digital marketing problems, visit Trust insights.ai today and let us know how we can help you

Machine-Generated Transcript

Comments

Leave a Reply Cancel reply

Pin It on Pinterest