I have two websites with separate google analytics code. I'm curious to know how people get to a specific page in Site A. In GA, if I go to the site content, find the page and then add a secondary parameter for the referer, I can see google, direct, plus some other domains.
How do I see which of my pages people are coming from to view a specific page?
Related
I'm having issues with tracking the UTM parameters in Google Analytics on an iframe.
My website is embedded in an iframe on http://www.blokker.be/inuwkot and http://www.blokker.be/danstonkot. The visitors go straight to the two links (either dutch or french). No visitors go straight to my own domain.
In the overview page form analytics I can view the amount of visitors/views but not the UTM parameters. I can only see it's a referal.
Any ideas on how to get the UTM url's working in the iframe so I can see where my visitors come from?
Since your frame content is located on a different domain you can not track url parameters from the hosting page without support from the domain owners - they would either have to append the parameters to the frame url, or send a message using the postMessage interface which allows cross-domain communication between pages and embedded frames.
So the page has to send the information to the frame, you cannot simply access it (for security reasons). If the owners of the blokker.be domain do not support that then you are out of luck.
This is a question about Google Analytics state 06/2016.
We run a site and have decided to try out Facebook Ads. Now in Facebook ads we have defined a custom parameter src=fb.
I'd like to create a custom Analytics report that shows
How many visitors visited the site via Facebook Ads
and then which pages they viewed and if they clicked on Adsense ads and the usual Adsense statistics like cpc, rpm.
How do I create a filter for this src=fb query string so I can follow what they did on the target site?
Please be detailed, a "create a custom filter" doesn't cut it. How, where, what content? The target uri is /?src=fb.
Edit: More clear information
There is a target site: example.com
There is a Ad campaign. To know that people came to the target site using this Ad campaign there is a parameter src=fb e.g. https://example.com/?src=fb
Because we know the parameter we could filter visitors who landed on the target site through the ad campaign.
GET /?src=fb HTTP/1.1
Host: example.com
This way we know people who clicked the ad came from the campaign.
People who did not click the ad visited the site from other sources. They don't matter in this context.
Now as the first step I'd like to display everyone who visited the site using /?src=fb uri. I could grep server logs but I wouldn't know if they clicked ads on the target site.
First, you should probably be using UTM parameters for offsite campaigns. Google Analytics automatically pulls UTM campaigns into standard campaign reports so you'd have to do only minimal sorting and filtering to analyze your Facebook ad performance.
But since you used a custom query string instead of UTMs you'll probably have to create a Custom Segment: Advanced > Conditions, and Include only Users (or Sessions, up to you) who hit a Landing Page that contains 'src=fb'. Like so:
Save that segment and view your reports through it and as long as your property is configured properly (you may have to define goals), you should see how your users behaved after hitting the ad.
I would like to track visitors sent to a website from different QR-codes. The QR-codes are unfortunately not created with google url builder. The problem, as I understand it, is that these visitors will only show as direct traffic to the different pages to where the Qr-codes points. Is there any good way to segment this traffic from other direct traffic to the same pages?
You will either need to:
Create a unique (sub) domain like qr.example.com/whatever
Create a unique get request like example.com/whatever?from=qr
Assume that everyone visiting your site from a mobile, with no referrer header set scanned your QR.
That's about all you can do.
I have two websites, website A and website B, the website A is a hotsite that is linked to website B, where the sales happen.
We need to know how the user got the website A and turned into a customer in website B(it means he bought something), so we can mesure the good sources to invest.
as the developer, I have access to these two websites source-code and can implement any google-analytic tag on them.
Thanks,
Jonathan
Web browsers generally send a referrer header, which contains the URL of the page which linked to the current page.
You can access this in the HTTP requests made to site B, and track sessions differently when the first page load is referred by site A. You can also access a document.referrer property in JavaScript, and use it to manipulate your analytics.
The correct way to implement this in Google Analytics is to configure the trackers so that they work cross-domain.
This will allow you to see all the information about where the converting visits originally came from and their path to purchase.
If you don’t use cross-domain tracking or you have it improperly configured, you’ll end up with meaningless data that shows self-referrers in the visit reports and a lack of proper attribution towards your conversion points. As a visitor moves from your primary domain to the other, they will start a brand new session in Google Analytics.
...
If a visitor clicks an ad or performs and organic search and ends up viewing a page on the www.3rdpartycheckout.com after viewing pages on www.primarydomain.com, you lose ALL data about how that user arrived and the complete picture of what they did. If they end up converting, you will only know that they came from www.primarydomain.com (which is not helpful at all).
http://www.blastam.com/blog/index.php/2011/02/google-analytics-cross-domain-tracking/
Have the landing page on website B look at the referrer tag and if its website A then use a separate Google Analytics instance on website B for all sessions that were sourced from website A.
We have a dozen or so sites, as well as the occasional subdomains so:
example.com
example.co.uk
us.example.com
etc
We have been using separate GA codes for each site. This works fine, but it means that adding a new site means getting a new code and we can't tell overall stats (e.g. how many people have visited all sites etc). If we went the one code route and set up separate profiles for each domain/subdomain:
1) Should we use _setDomainName("none") or _setDomainName("www.example.com") and _setDomainName("www.example.co.uk") etc
2) Will each domain profile treat the other domains as separate (e.g. will we tell on example.co.uk how many people visited from example.com and completed goals etc)
3) Are there any disadvantages to this method.
This post from the Google Analytics blog details how to set up a GA account for each site, and an overall 'rollup' account which sits on top - this will let you give separate GA admin control for each site, where you can dig deep into each site's account, and show cross-site referrals, and the rollup will give overall numbers (but I don't think it's going to report on unique visitors across the collection of sites).
http://analytics.blogspot.com/2009/09/advanced-structure-your-account-with.html