I have a GA custom dimension ("Byline") to capture the author's name for each article on my site. However, applying Byline as a secondary dimension on a report for a page drastically reduces the pageviews for no apparent reason. Specifically, one page had 21,479 pageviews in the past week. With "byline" added as a secondary dimension, the total pageviews decrease to 13,398 -- it doesn't introduce a "null" or "not set" as an option, it just doesn't seem to track those pageviews.
The custom dimension is based on a GTM variable (DOM Element, CSS Selector) that is part of the Page View tag, so it should fire on all pages. Why is that not the case? The report has the same date range in both cases.
There appears to be a similar discussion here but it wasn't answered. Any advice is appreciated, thanks!
(edit: misspelled "custom", naturally)
Related
I created 3 custom dimensions through Google Tag Manager (added them as Data Layer Variables). Then, I added custom fields to my pages for these 3 custom dimensions.
After waiting about 24 hours, I checked the three custom dimensions on Google Analytics and two of them have showed up for all of the pages. The last one is showing up for maybe 4-5 pages, but not all of them. It's now been more than two days and the other pages still haven't populated with the last custom dimension.
Is there a quicker way to see if this third custom dimension is showing up for all of the pages with the designated custom field?
Since this is being done on a test site, most pages have not been visited a ton. Not sure if this can also matter for how long it takes Google Analytics to populate the data.
Get the chrome extension 'GA debugger' and go yourself to the site. On the console you ll see each hit sent to GA and all the fields that are being populated.
PS: Custom dimensions ll show up as 'cdX' where X is the number of the dimension.
I think you are passing the custom dimensions along with pageveiw. you can check the GA tags that are firing in network tab of your browser only to validate
In your browser access inspect element by right cliking on website and select network tab you can check the screenshot mentioned in the below URL to make all setting required to see GA tags in network tab
http://imarunkumar.blogspot.in/2016/08/blog-post.html
And then reload the page and you can see the Google analytics tags firing, check your tags if custom dimensions are being sent in the tags.
I hope you have provided the right custom dimension index number in GTM while creating the tags. Assume you are sending data to custom dimension 1,2,3 the in tag you can see the values sent.
cd1:xxxxxx
cd2:xxxxxx
cd3:xxxxxx
This confirms that Custom dimension tags are being captured on the page and sent through GA tags to Google analytics.
What if you can see these custom dimension beign sent through the tags but you cannot see the same in reports.
Here the custom dimension configuration you did on the analytics property needs to be reviewed.
As you are collecting all the custom dimension at every page the scope for these custom dimensions should be set at "HIT" level.
Let me know if you are facing any issue in checking them according to the instructions provided above.
I'm just getting to grips with Google Analytics for a site I'm doing some content management for, and want to know how to look at the traffic for pages created recently/in specific timeframes.
Anyone got any ideas?
You would need to log the page creation date as a custom dimension. Then you'd need to select your timeframe, and filter by your custom dimension (via regex, since you cannot apply the date filter to a custom dimension).
If the page does not have any hits in the selected timeframe it will not show up at all. And in any case you will see only metrics from the hits in the selected timeframe, even if the page has been created before that.
So this is sort of possible, but rather more complicated than one would assume.
I've been looking around and also played with custom reports but I don't find it: how to set up a custom report that shows the number of conversions in Google Analytics where the visitor has visited a particular page?
The idea is to gauge whether a particular page is increasing the likelihood of conversion.
So far, I've tried looking at conversions with a dimension of 'Page' and also the various levels ('Page path level n')
What you're looking for is "Advanced Segments":
Google's Docs: http://support.google.com/analytics/bin/answer.py?hl=en&answer=1033017
in GA if I create a custom report filtered by a specific page or source/medium I see an incoherent number of visits, in particular unique visitors are higher than visits.
If I remove the filter visits become coherent with visitors and page views!
I found what I believe is the answer in the link below.
http://www.michaelwhitaker.com/blog/2010/04/23/unique-visitors-0-visits-and-pages-in-web-analytics/
To detail the answer is quite lengthy, but in summary - for purposes
of attribution, google credits a visit at the page level to the first
page visited in a single visit. However it credits every page viewed
to a unique visitor.
So basically what the visit metric stands for in the report you showed
is how many visits started their visit on that page. To find out how
many actual VISITS went to a particular page use unique pageviews
since it counts pageviews only once, for every visit.
Confusing...yes. However it appears to be the reason.
Source: https://webmasters.stackexchange.com/a/27276
I'm developing an E-Commerce site and I want to set-up a Google Analytics Goal for whenever a user visits any product page. However, the product pages are all in different categories and have different urls.
There are 2 approaches you could take.
The preferable way is for you to unify the product page URLs to meet a particular pattern, so that you could configure the goal to be a Head Match on that pattern.
ie, if your gimzo product URL is domain/products/gizmo, and your widget product URL is domain/products/widget, you could set the goal to trigger for viewing /domain/products as a head match.
Or, you could just set a new pageview/event for every product pageview. ie, on the product page, set an additional event to lock the goal against. (The drawback to this approach is that it messes with bounce and exit rate numbers.)
Now, the one caveat with these approaches is that a single goal can only trigger once per visit, so, your "Goal" will only trigger once, even if I view 4 product pages in my visit.