Google Analytics: Difference between revisions
Jump to navigation
Jump to search
(8 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
* To get useful information from your AdWords campaign in your Analytics account, you must link your accounts. This is not done automatically. | * To get useful information from your AdWords campaign in your Analytics account, you must link your accounts. This is not done automatically. | ||
* Warning: be sure that there is no redirect in your ad target URL. Else the parameters passed by Google can be stripped, thus no reporting is done. | |||
== Edition == | |||
* You cannot duplicate a campaign or edit adwords directly on a table with the normal web interface. For this you need to download a desktop application, AdWords editor. | |||
== Conversions == | == Conversions == | ||
Line 8: | Line 13: | ||
* To view a detailed Conversion report, including segmentation by conversion name (very useful if you have several conversions), you must include the Many-per-click conversion column. Then you can use the segmentation by conversion name (or type) by creating a normal segment. | * To view a detailed Conversion report, including segmentation by conversion name (very useful if you have several conversions), you must include the Many-per-click conversion column. Then you can use the segmentation by conversion name (or type) by creating a normal segment. | ||
== My Client Center == | |||
* To manage multiple AdWords account, it is better to use Google's My Client Center. | |||
= Tracking = | = Tracking = | ||
Line 13: | Line 22: | ||
* With the new asynchronous system, the GA script is loaded asynchronously. There is a queue of commands that can be set; once the script is loaded, they will be executed. Once the script is loaded, any command entered into the queue is also directly executed. | * With the new asynchronous system, the GA script is loaded asynchronously. There is a queue of commands that can be set; once the script is loaded, they will be executed. Once the script is loaded, any command entered into the queue is also directly executed. | ||
* If you give the "_trackPageview" command twice (to the same tracker), two calls to the Google backend servers are made. For custom variables obtained after a first "_trackPageview", it may thus be necessary to issue a second one. The second call may be with a virtual URL, if the custom variable is associated to the entire visit (session scope). | * If you give the "_trackPageview" command twice (to the same tracker), two calls to the Google backend servers are made. For custom variables obtained after a first "_trackPageview", it may thus be necessary to issue a second one. The second call may be with a virtual URL, if the custom variable is associated to the entire visit (session scope). | ||
* To obtain page load metrics, you must add the following snippet: | |||
_gaq.push(["_trackPageLoadTime"]); | |||
It is currently not tracked by default. | |||
== Bounce Rate == | |||
* If you send to the GA servers first an event call, even with the non-interactive flag set, and a pageview, this session won't be counted as a bounce session. The reported bounce rate will then be false. I consider this as a bug. The workaround is to make sure you send the pageview call first. | |||
== Data sent == | |||
* utmhid: a random number, different on each page view, that seems to be linked with AdSense processing. | |||
= Back Office = | = Back Office = | ||
Line 43: | Line 63: | ||
== Misceallenous == | == Misceallenous == | ||
* | * To visualize custom variables values or data in the standard GUI, use Standard Reporting -> Visitors -> Demographics -> Custom variables. | ||
* You can share custom reports! Very useful, especially for Kameleoon Analyst. | * You can share custom reports! Very useful, especially for Kameleoon Analyst. | ||
== Custom reports == | |||
* When importing a shared custom report, it automatically creates it in your first account/profile. However, you can edit this report later and change the profiles the report applies to. This requires a bit of work so is not optimal, but allows you to properly import stuff. | |||
* When using a custom report with dimensions corresponding to events and metrics corresponding to conversions (Goal completions, etc), there are never any goals fulfilled. This is a big problem, and I don't understand why this is the case. I would expect conversion values from visits associated with an event, that later trigger a conversion. | |||
= Limitations = | = Limitations = |
Latest revision as of 15:54, 10 March 2014
Google AdWords
- To get useful information from your AdWords campaign in your Analytics account, you must link your accounts. This is not done automatically.
- Warning: be sure that there is no redirect in your ad target URL. Else the parameters passed by Google can be stripped, thus no reporting is done.
Edition
- You cannot duplicate a campaign or edit adwords directly on a table with the normal web interface. For this you need to download a desktop application, AdWords editor.
Conversions
- A conversion (1-per-click) means only a single conversion is reported for a single visitor / customer; this is true even for multiple conversion goals. On the other hand, conversion (many-per-click) reports the total number of conversions for a visitor, following 30 days of an AdWord click.
- To view a detailed Conversion report, including segmentation by conversion name (very useful if you have several conversions), you must include the Many-per-click conversion column. Then you can use the segmentation by conversion name (or type) by creating a normal segment.
My Client Center
- To manage multiple AdWords account, it is better to use Google's My Client Center.
Tracking
- With the new asynchronous system, the GA script is loaded asynchronously. There is a queue of commands that can be set; once the script is loaded, they will be executed. Once the script is loaded, any command entered into the queue is also directly executed.
- If you give the "_trackPageview" command twice (to the same tracker), two calls to the Google backend servers are made. For custom variables obtained after a first "_trackPageview", it may thus be necessary to issue a second one. The second call may be with a virtual URL, if the custom variable is associated to the entire visit (session scope).
- To obtain page load metrics, you must add the following snippet:
_gaq.push(["_trackPageLoadTime"]);
It is currently not tracked by default.
Bounce Rate
- If you send to the GA servers first an event call, even with the non-interactive flag set, and a pageview, this session won't be counted as a bounce session. The reported bounce rate will then be false. I consider this as a bug. The workaround is to make sure you send the pageview call first.
Data sent
- utmhid: a random number, different on each page view, that seems to be linked with AdSense processing.
Back Office
Concepts
- It is important to understand the difference between dimensions and metrics. Dimensions allow you to select only part of the total data available (for instance: I want data corresponding to page titles), whereas metrics represent the results of the data (how many pageviews, which conversion rate, etc). A good way to distinguish dimensions from metrics is to remember that metrics will always have number values, whereas dimensions are usually text.
- In custom reports, the Explorer choice allows you the full data visualization (with graphs). The flat table choice only reports data in a plain looking table.
- You can plot almost everything over time by using Motion Chart instead of default Line Chart. You have to choose Time as x-axis, with a spanning period (range) of more than one day. To get a meaningful graph you have to check "Trails" checkbox, then play over the motion chart. It would be actually way better if you could just have the graph plotted out without having to check the play button (which does not add anything useful).
Main Interface Entry Points
- Home:
- Real-time: very useful real time data.
- Intelligence: useless, allows you to define automatic alerts.
- Dashboards: contains your dashboards (which is a collection of shortcuts). Not very useful.
- Visitors: information about visitors (browsers, capabilities, country).
- Traffic sources: very important, can help you understand where your visitors come from.
- Content: which pages are viewed.
- Goals: user-defined goals.
- E-commerce: track transactions and items sold.
- Custom Reporting: contains a list of custom reports, and allows you to create new ones.
- Advanced segments: crucial, allows you to set custom segments.
Misceallenous
- To visualize custom variables values or data in the standard GUI, use Standard Reporting -> Visitors -> Demographics -> Custom variables.
- You can share custom reports! Very useful, especially for Kameleoon Analyst.
Custom reports
- When importing a shared custom report, it automatically creates it in your first account/profile. However, you can edit this report later and change the profiles the report applies to. This requires a bit of work so is not optimal, but allows you to properly import stuff.
- When using a custom report with dimensions corresponding to events and metrics corresponding to conversions (Goal completions, etc), there are never any goals fulfilled. This is a big problem, and I don't understand why this is the case. I would expect conversion values from visits associated with an event, that later trigger a conversion.
Limitations
Goals
- Goals can not be set retroactively; you must set them and only once they are set, data is collected.
Custom variables
- Only 5 custom variables. To overcome this, you can put data in the URL (maybe with virtual page views?).
- 50 variables are available in the Premium version of Analytics.
Sampling
Questions
- What's the difference between "Organic" and "Referral" ?