I operate a high-traffic website, where users have a public page (e.g. website.com/users/$USERNAME ) and would like to create analytics for them. Instead of re-inventing the wheel, the best would be if I could leverage google analytics directly.
It's not a problem is users opt-in to this scheme, and give me their google account name. One idea was to create custom analytics views for users, but it seems there's a limit of 25 views per properties.
Another thing I was looking at, is using Google Analytics segments, but it seems that segments are scoped to a subset of users or sessions, while I want it on certain page-hits only.
I could also dynamically use their google analytics code, if it was scoped to a single page.
Is this use-case something that Google analytics supports, or should I develop a home rolled solution?
Related
I have a multi tenant setup using the same HTML but different web urls
eg. tenant1.company.com , tenant2.company.com
since both use the same htmls the analytics code is same. How do i set up different codes for different tenants to get different data in GA
Unless you intend to analytics between the two tenants you should be using a different web property id for each one. There is really no reason to be storing the data in the same Google Analytics account.
Its just a simple matter of changing the javascript snippet on each site.
I have a website where people post items and I want to show some basic analytics in their own user panels, such as how many people viewed the posted item.
I am wondering if I can use a single mothership Google Analytics account across the whole site. Then, in my code for the user area, I have it query Google Analytics for that specific users posts and return the number of visits that specific person has had.
So my google analytics account may say "200 views across the whole site" but within the specific users panel I will be able to say "Your posts received 50 views".
This is the closest bit of documentation I could find on the subject:
https://developers.google.com/analytics/devguides/reporting/core/v3/
It sounds like what you would need is multiple Google Analytics IDs / requests per page. This can be done with the newest version of Analytics, though not with the Classic Analytics.
You can certainly have multiple Google accounts access the single Google Analytics for a single domain. You can certainly split reporting capabilities and access to various Analytics features across multiple accounts.
From the docs:
You can install multiple instances of the Google Analytics tracking
code on your web pages to send data to multiple properties in your
account.
Read: more here.
I'm trying to add recommender systems to an existing website. In particular, I'd like to implement item-item collaborative filtering, to figure out what pages users tend to visit in the same session--much like Amazon's "People who viewed this item also viewed...."
At a minimum, collaborative filtering requires data on each individual viewing session, so that the algorithm can determine which pages get viewed together, rather than just tallying up how many times each page gets viewed in the aggregate.
If I were creating a new website, I could pretty easily add code to collect this data. However, this is an existing website, and has been set up to use Google Universal Analytics.
I have two questions:
Can I get Universal Analytics Data through an API? I need to be able to analyze the data using my own algorithms, not just look at it in a dashboard. I know about the Core Reporting API--but the Core Reporting API doesn't seem to include any extra Universal Analytics variables. I know about the API for sending Universal Analytics data, but that's not what I'm trying to do here.
Assuming I can query an API or otherwise export the Universal Analytics data, will I be able to distinguish individual sessions? The idea here is not to ask questions about individual users (let alone associate their data with some other data), but simply to figure out which pages were viewed in the same sessions.
Thanks for your help.
You can use the Google Analytics Core Reporting API many combinations of the available Dimensions and Metrics. You should check out the Common Queries page to get a sense of how precise you can get in terms of how people might use your application.
Also the Hello Analytics APIs Quickstart guide is a good place to start if you haven't developed an application with Google APIs.
I'm working on the architecture for a project that includes a Android and iOS apps and a web interface with a subset of the mobile apps functionalities. The project is basically a e-commerce solution. In all three interfaces I'm using Google Analytics to track some information. However I'm having an internal discussion about the extent of the information I should send to GA. What should I store in GA and what should I store in my own server?
Let me give you some examples.
Session tracking is clearly something that belong to GA.
ProductDetailViews. Sounds like something that should go into GA, specially considering the enhanced e-commerce module.
Shared item. When a user shares some content over a social network, should I store that information on GA or in my own server? I'm inclined to GA but it becomes more ambiguos.
Do you see my point? Can someone share a general rule or recommendation on what should be saved in GA and what should be saved on the projects own server?
Thanks
For those examples I would generally send all the hits to Google Analytics. Here are a few reasons:
Preventing data silos. You want all of your data in one place and Google provides you with a database reachable via the API where you can keep all your data organised in one place. This is important when you are considering measuring performance, as you want to avoid duplication of conversions or traffic hits
Useage of Google Analytics advanced segments. With all your data in GA, you will be able to create advanced segments for analysis. But the real power is if you are using AdWords or retargeting, as you can send those Advanced Segments to AdWords, and target those users around the web with your custom data
Single point of reference for users All analytics are inaccurate, but you want to make sure they are inaccurate to the same degree. Using GA keeps all your data on the same playing field
Usability and Freedom of information Its easier to serve up your data to users within the GA interface as people are more likely to know how to navigate that than your database. You can also use the GA API to pull out any data you need to push into other visualisation tools.
User session merging With your data and userID tracking in GA, you may be able to track users as they arrive via mobile to desktop and back again, over multiple sessions.
What you need to avoid putting in to Google Analytics is personal info such as names, email address etc. There are against the TOS. But you can capture a unique userID, and match that outside of the tool later.
I am setting up different Analytics profiles. The default one that shows everything, the master one that has the custom filters, and the test one where I test filters before moving them to master.
Should I link Adwords to all profiles or just the master profile? Are there advantages and disadvantages to both approaches?
I'm wondering if having it linked to all profiles will pollute or duplicate the data somehow.
The client is not actively using Adwords at the moment so I can't test this myself. But I'd like to set up the profiles correctly now so it will work when the client starts using Adwords again.
It shouldn't matter. You'd link GA to AdWords for two things: get a more indepth view of your paid traffic in Analytics and have some GA information (mainly conversion related info) in AdWords (if you link the two accounts in AdWords, that is). I'd say you're better off linking it always. There are plenty of segmentation/differation possible within GA regardless.
Edit: if anything, it'd make your data more valuable, instead of have multiple sets with several variants, besides just the filters.