I am creating a simple mobile app for testing Google Analytics system.
It consists of 1 Activity
And i am installing Google Tag Manager SDK.
It's work.
But i want to configure and testing source traffic.
What i must change in code?
AndroidManifest? Main Activity? How?
And how i can testing to ensure what it's good work
For example:<> user came from FaceBook, and i want to see in Google Analytics report
utm_source - FaceBook, utm_medium - cpc
Thanks!
Related
I am new to Google Analytics.
I added Google Analytics to my hybrid app built with react native. I used "#react-native-firebase" to implement GA into my app.
When I added my app to internal testing release on "Google Play Store Console", immediately after some time there were more than 30 plus users showed up on Google Analytics console. This is highly unlikely considering I didn't share the link. Also all these users were in United States with the event first_open_time using wide range of os version and device model.
So my suspicion is Google is internally testing my app before actually rolling out the application.
Has anyone else faced this or something similar to this before? If yes, is there any workaround on how to identify these fake triggers and not log them to Google Analytics? (I assumed that for the proper workflow with the GA these fake triggers would be hindrance, right?)
I'm going to implement Google Sign in my app to let the users log in with their google account. This app doesn't allow registration, as the users are created in a web portal.
The web also have google sign, except that it does uses it for registration.
So, what I want is to only use this in the android app to log users who has already registered at the portal. Is that possible?
I'm following the android docs, which says I need to configure a Google Api console project, do I need two (one for the android app and the other for the web), or it can be managed with just one? Also, I'm wondering the same question having two apps (android and iOS).
I'm trying to understand the logic of the process. Google docs explain how to do it, but I wanted to know a little more about what's happening.
If I understand your question correctly then you need to implement the google authentication process in your application that can be used in all the platforms (Web, iOS, Android).
Google has a platform Firebase Authentication solely for this purpose.
https://firebase.google.com/products/auth/
Here you create a project in the firebase console and then use it for all the 3 platforms.
You can go through the google documentation, it is easy to understand and use.
Or you can go through this link to understand how to implement it on Android.
https://medium.com/#valokafor/working-with-firebase-authentication-8f7dcb016e84
How my app was installed, how to track where the downloads are coming from, through which partner (advertising publisher)?
For example, I created ads in Facebook or in AdMob. User saw the ads, clicked on them, was redirected to the Google Play Store where he downloaded my app. How can I know that this user downloaded my app by clicking on the Facebook or AdMob ads? Does Google Analytics track and show this info?
You can easily set up install tracking for Mobile Apps:
Enable app install tracking in your account.
Install tracking is automatically enabled in Google Analytics for Android apps. You don’t have to do anything!
Update your Google Analytics SDK.
You need to change a few lines in their manifest file. Refer to the Developer Guide for Android for specific example on how to do this.
Set up Custom Campaigns.
Custom Campaigns are a Google Analytics feature that add parameters to the URL of your marketplace page where users download your app. It’s these parameters that tell Google Analytics what marketplaces your traffic comes from. Get an overview of Custom Campaigns in Google Analytics and how they work. You must set up Custom Campaigns for each platform you’re using.
Analyze your data using the Mobile App Sources report.
If you complete the steps outlined above, your data will appear in the Mobile App Sources report. Use this report to find out what brings users to your download page in each marketplace.
Reference: https://support.google.com/analytics/answer/3389142
The facts:
My company has developed an Android app.
My company has NOT developed an iOS version to this app in anyway.
I have created a Google Analytics account, opened a mobile app tracking ID, and connected it to my Android app using the SDK (this was not done by me, rather by our developer).
Our app launched and has some users according to both our Google Analytic's account and the Google Play Developer Console account.
In the Google Analytics if I examine the operating systems of my users my operaiting split is:
Android - 91.69%
Macintosh - 8.05% (Macintosh 10.10)
iOS - 0.26% (iOS 8.1.2)
How is this possible? We haven't developed for iOS.
This is so-called referral spam. I won't go into details here as there're lots of good sources on the net about the issue(e.g. this, this and this one).
I've handled this issue like this:
Go to your app view in the Google Analytics.
Open the 'Admin' tab.
Click on 'View settings'.
There will be section called 'Bot Filtering', check the 'Exclude all hits from known bots and spiders' option.
From now on Google will remove the spam hits from their analytics. This solution has two issues, though:
Historical data will not be affected by this option, i.e. spam hits which were made in the past will remain in your data, Google will only filter your future hits.
Google promises to remove hits from known bots, which means that the time from the new bot appearance to the moment when it will be included in the Google filter list can be indefinitely long. I use this solution for the last week though and didn't find any new bots breaking through the filter.
In iOS, we have provisional profiles to setup device UDIDs. So, our app will install on devices only which UDIDs are added to provisional profile at development stage. We generally added only customer device. So only customer can install the app. The build will not install any other device.
Is there any feature like above in Android?
NOTE: I knew we have feature in Google Play. But, I need this feature while development.
You can filter which users (not devices) can install your app.
In order to do that, use Google Play Developer Console to publish beta application APK - it can be installed only once user joins specific Google+ community or Google group.
So you have to create such a group or community and make it private - this will allow you to filter out which users can join.
After those users join, you will send them test URL and app will be installed on their devices.
Have a look at this Google Play Help article for more details.
The Play Store's method of doing this is via the new beta-testing feature. You add your testers to a Google+ community, and they get access to your application via the Play Store.
If you don't want to use the Play Store, you can implement a restriction within the app itself to accomplish this. The Identifying App Installations Android Blog post has some great information on how to uniquely identify devices. You can use one of these methods to check the device's identifier against a list of "approved" devices in your Activity's onStart(), and simply call finish() if the user is not "approved."