I posted this on Google's help forums, but I still haven't gotten a response, so I thought I'd try it here;
I work for a web development company with 200+ active clients. We are in the process of setting up Google Analytics tracking for each of their websites. We have already created a Google account for each of our clients, and we are attempting to manually sign each one up for GA. We haven't gotten very far in creating new GA accounts, after creating a few accounts, we are required to use text-message verification to create the accounts, and after a few more, we are unable to create any new accounts at all.
We are following the recommendation of Google's Help Article found here:
http://www.google.com/support/analytics/bin/answer.py?hl=en&answer=55601
We are a legitimate business trying to set up analytics for legitimate customers. At this point we can't create a single new GA account, but we still have 182 clients that we have promised to set up with GA, plus any new customers, all of which we intend to set up with GA. We've clearly been flagged as a robot by Google's system, which is totally understandable given the volume of accounts we are creating, but we are not using any robots, we have a person sitting at a computer manually entering all of the information for each of our clients.
Does anyone have any ideas or a solution?
Are you logging in as a different client each time in order to open the new account?
If so, try logging in as yourself and creating each new accounts in your profile. Once created, add your client as a user (report or admin level).
Related
Okay, some heads-ups as I feel I'm an idiot and missing some simple stuff. As far as I understand Google Analytics works with a 3 tiers system: account -> property -> view. and I should be able to manage these 3 levels via the google analytics management api.
For some context as to why I encounter this issue. I am making a CMS in which I want to register a new google analytics account per user, and a property per website this user has. (implementation and usage of views out of scope for now, I will implement those on a later date). To achieve all of this I started following Google's documentation on the Google Analytics Management API (according to Google this is what manages accounts, properties and views). Therefor I have made a service-user-account which should have enough permissions to manage GA-accounts.
However I can't seem to be able to create a new account via the API. Am I missing something obvious? Is it not possible at all this way? If so, how then? Because my goal is to have GA on every website, without the user having to config anything.
You can't do it. The management API only allows for the list operation on accounts: https://developers.google.com/analytics/devguides/config/mgmt/v3/account-management#account_summaries
The only solution would be to use the Provisioning API. It can be used to create new Google Analytics accounts and enable Google Analytics for your customers at scale: https://developers.google.com/analytics/devguides/config/provisioning/v3/
Anyway, the Provisioning API is currently available by invitation only.
I manage a website that sells business cards: Oubly.com
I believe the previous developer did not install the Google e-commerce tracking correctly.
Every single transaction since 2014 has been attributed to
Direct.
Coming from previous experience working with another e-commerce site I know that this is impossible. The previous e-commerce site I worked with had various transactions from various sources.
conversions
The amount of transactions is correct, I just know that they all cant be coming from Direct.
How can the current developer tell if the tracking code was installed correctly?
Right now there's not enough information to tell you 100% what is your problem. But likely you are losing the cookie when tracking the transaction.
The most common cause is that the hostname of the page that tracks the transaction is different than the hostname on your website. Google Analytics stores a unique and random clientId in a cookie when a user visits your website. If your site suddenly changes to a new domain such as a payment partner domain the cookie won't be accessible anymore, so GA thinks this is a new user and recreates a cookie. That starts a new User and a new Session in GA often with the trafficSource of (direct).
The solution is to implement cross-domain tracking for GA. Cross-Domain tracking helps you pass cookies from one domain to another so GA knows that it's the same user.
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'm accessing the Google Analytics API v3.0 with the .NET client adapter.
This is all working very good, but I'd like to get the account owner e-mail address for a given account that I have access to.
The resource description only has Id, Name, create- and update date.
Is there a way to get more detailed data for this account? Ideally the owner e-mail address or user data would be great. I couldn't find anything in the Analytics API docs, also nothing declaring that this information is NOT possible to get...
Google Analytics account doesn't really have an "owner" per se. Each account can have multiple users with different permissions.
Recently, Google Analytics launched a new permissions model (see this blogpost for more info), and it'll be rolled out to all the users in the coming weeks. Currently, this information is not available though the Analytics API, but feel free to file a feature request here.
I am a web developer, and offer the creation of Google Analytics accounts for clients. To save them messing around with veifying email accounts, I like to create them a gmail account, get it all set up then just send them the password.
However, Google is asking for verification by Mobile and I have now reached the "verification limit".
I kind of understand why Google don't want spam accounts, but is there no way to regsiter as a developer and then create accounts for clients? Something like apps for business, but just for standard Google accounts.
Thanks #CrayonViolent it looks like profiles is the way forward
I would be a mistake to use profiles for multiple clients. For one, each client would be prevented from using more than one profile. And there is a limit of 50 profiles per account.