what is difference between unique referrals on Clickmeter and New users on Google Analytics? One of our vendor is using Clickmeter and we are using Google Analytics and the data doesn't match. Any suggestions on tracking unique referrals on Google Analytics?
In ClickMeter a click is unique if is human (it does NOT come from a bot/spider) and if there are no clicks on the same link from the same IP in the 30 mins before this click was made. More info here: https://blog.clickmeter.com/click-types
GA determines unique using cookies (a completely different technique). In order for Google Analytics to determine which traffic belongs to which user, a unique identifier associated with each user is sent with each hit. track all the visits to a specific website https://support.google.com/analytics/answer/2992042?hl=en.
Moreover, GA analyzes all user on a specific website in the same bucket while ClickMeter performs a different count per each link. It may happen that more ClickMeter links point to the same site and a user that click two or three links together is counted as unique three times.
Please keep in mind that GA and ClickMeter are NOT the same thing and are used (together or not) for different reasons. https://blog.clickmeter.com/google-analytics-alternative
Related
I am trying to get to a point where I can identify visitors who are generating website Goals. And identifying them via their Pardot ID-s in GA.
Do you think that's possible?
On the site every visitor gets a Pardot cookie and in that there is a readable Visitor ID which via an API query can be turned into a Pardot ID.
But how can this piece of information get stitched to the rest of the GA parameters? How to push this into GA as a custom data point so I can create a report on who are the Pardot IDs that completed a certain goal this week?
Is there any guidance you can give?
Assuming, that Pardot ID itself is not a Personally Identifiable Information (PII) in terms of Google Analytics, there are several ways to accomplish this.
You could provide this data as User ID, which helps Google Analyitcs to identify users across several browsers and devices. However, this dimension is not exposed on the reporting GUI or the reporting API. (Available dimensions and metrics can be browsed here.)
Instead, or in parallel, you could store this information in a custom dimension, which, can be used in standard or custom reports, or via the reporting API as well. There a couple of things to consider. According to the Measurement Protocoll reference, the maximum length of this field is 150 bytes. You should also decide, if this dimension is most useful for your needs and possibilities on hit, session or user level, about which you can read here.
I am looking to provide analytics for a website which has user generated pages (which would therefore require a unique tracking ID for each page).
Is there a limit to the amount of different pages I can track?
I have looked around documentation provided by Google on data limits but have found no information regarding this.
Thanks in advance
You can create up to 50 propertys per account.
The trackable documents should be unlimited. Only limited by pageviews per month (10 million /month).
limits and quotas
Your assumption that you need to have a different tracking ID for each user generated page is not necessarily correct. You can track the entire website using the same Google Analytics property. I assume you're worried about exposing analytics data about the page generated by user A to user B accidentally. To prevent this from happening, what you can do is configure a custom dimension in Google Analytics that records which user a page belongs to. Then, when exposing analytics data to a specific user, you can make sure to only expose data about pages that belong to that specific user.
I've just set up a tool on a client site that users can use to request a quote from our client. To do this the user lands on a form page, fills in their details, submits and then lands on a thank-you page. Pretty basic.
I set this process up as a goal in Google Analytics, using the destination type goal: "begins with /thank-you" and shared that goal as a conversion in Google AdWords.
I decided to run a few Google AdWords ads to promote the tool. I also wanted to double-check the conversion data that AdWords gives you so I set the destination URL in Adwords to www.example.com/form-page?adsrc=adwords1 (2, 3, 4 etc. for each ad) and I configured the DB so that there was a column that tracked which URL the user was on when filling in the form (this would be the column I counted to get the number of conversions that came from AdWords so I could compare)
Further to this, I made sure that the initial URL parameters that the user landed on were stored in the session so that if the user browsed to other pages and came back to fill in the form later, it would still attribute the conversion to AdWords.
I tested this thoroughly on a staging and production environment and everything was working correctly.
I ran the campaign for a week and when I checked, the conversion results in the Data Base vs the ones coming from AdWords are wildly different. The DB tells me I've had 5 conversions while AdWords gives me 21.
Is there anything in the way Google uses its gclid that may be causing this issue? Or is there a problem with the way I've set up the measurement structure?
This can be caused by few things, but I think this is the GA/AdWords issue, more than your DB/session set-up.
Gclid shouldn't influence your goal, since it is used only for AdWords/Analytics interactions, Goals should not be affected in your set-up.
https://support.google.com/analytics/answer/2938246?hl=en
Probable cause: If your goal set-up only contains "begins with /thank-you", isn't it possible, that you are counting all the sessions which reach thanks-you page? Not just AdWords?
Solution: if you need to count conversions in AdWords (for performance improvements), use AdWords conversion code at the same page, this counts only those users, who clicks an ad and reach your thank-you page in x (default 30) days. Be sure to count only unique conversions (users by cookie).
Differences between GA/AdWords conversion count:
https://support.google.com/analytics/answer/2679221?hl=en
Google attributes conversions to the last marketing channel, where direct visits do not count as a marketing channel (if you look at their attribution flow visualization you see that the penultimate step is to check for existing campaign information for the user). So GA might overcount Adwords visits (or other campaigns) and conversely shows fewer conversions for direct visits.
On contrast your database probably records the last traffic channel without an elaborate attribution model, so it will show less campaign traffic.
Also IIRC the adwords interface records the conversion for the time of the ad click, not the actual goal conversion, so the timeframes for the conversions differ.
How can i track a single users path through the webpage with Google Analytics?
I am not interested in who that user is, only what path the user went.
You can assign a unique value to a Visitor-level Custom Variable when a user visits the site. Then you can filter/segment based on the value that you want to examine to narrow down paths by individual. It's not entirely clear whether or not this violates Google's terms, though. You're not technically tracking an individual, you're just relating the actions of various anonymous users.
Trying to set up Google Analytics to track two language versions of the same site: example.com and example.com.mx. Right now, we have it setup under two different profiles, each with the standard (different numbers) tracking code. That method doesn't seem to track the sites correctly.
My question: is this the correct implementation for the example.com, example.com.mx scenario or does it need to be setup as suggested be Google in the link below?
http://www.google.com/support/analytics/bin/answer.py?hl=en&answer=55503
Thanks in advance for any input...
It all depends on whether you have many visitors visiting both sites - if you use different webproperty IDs (UA-XXXXXXX-Y and UA-XXXXXXX-Z), a user visiting both will be counted as 2 unique visitors, 2 visits, so your unique Visitor count will be inflated.
That is because GA uses first party cookies only for identifying unique visitors, so the cookie is unique to the domain.
If you don't care about Unique Visitor duplication, you can use 2 different webproperty ids, and even just one and separate the sites with profile-level filters.
If you do want to see both sites as only one entity, you should use _setDomainName.
Have a look at http://code.google.com/apis/analytics/docs/tracking/gaTrackingSite.html for implementation advice.