I'm running and A/B test with Google Optimize on one of my pages.
This page is shown on multiple website on different domains through an iframe.
So, domain of my page is different from domain of the website hosting the iframe.
I have no control on the website hosting the iframe.
The problem is that I'm not seeing any data collected from the Experiment in Google Optimize.
I suspect that iframe an Google Optimize don't work smoothly together.
I can't find a clear answer on the documentation or in another questions online.
Do you know if is it possible to run an AB test inside on iframe hosted on a different domain?
If Google Optimize is the problem, do you know other tools that work properly in this situation?
I think is a problem with the _gaexp cookie, "SameSite" and "Secure" settings, because your iframe is in different domain
In these threads you can see similar problems with iframes:
Possibility to set cookie flags to _gaexp
https://support.google.com/optimize/thread/75547539?hl=en
Related
I have a main website (e.g. mybrand.com ) with static pages mostly developed on Wix.com and I have a full application hosted on AWS on a sub-domain, e.g. app..com.
For tracking the traffic coming from different social media channels, we are building UTMs. My understanding is that the UTM tracking doesn't work when you hop between the sub-domains. Can you please suggest some clever options?
One option for us is to re-do the Wix website in WordPress and host WordPress ourselves on AWS next to our WebApp to completely avoid the domain hoping. But if we have a more elegant solution while keeping the Website, it would be preferred.
You can use a simple parameter in querystring (i.e. subdomain.com/page?from=domain1) then in Analytics count unique page with that parameter in the URL.
I hosted a website and included a Google Analytic tag in it to count the visitors. The website itself is kinda empty and has no purpose other than trying out Google Analytics.
It seems like Google Analytics can somehow find out if i visit the website via a proxy and doesnt add this visit to the visitorcount. It doesnt matter if i use the proxy directly in the browser or via a java framework like HtmlUnit or Selenium.
The frameworks and proxys themself are working, i checked it at websites like whatismyip dot com. The Analytic tag is also working, since it correctly adds normal visitors to the visitorcount.
So my question is: how does Google Analytic find out someone is using a proxy? As far as i know the only indications someone is using a proxy are in the HTTP-Headers (X-Forwarded-For tag and so on). But the JavaScript which is included in my site shouldnt have access to the HTTP-Request, right?
I used free proxys which can be found if you google "free http proxy list" or similar keywords. Does Analytic automaticly downloads and blacklists those IP-Adresses? Because i canot imagine any other way it can find out someone is using a proxy just via Javascript.
If you tick "Exclude bot" in View settings it may be that Analytics recognizes those IPs as spam sources. Since these proxies are free services they can be used frequently for this purpose by malicious people and Google has blacklisted them.
After using Goole Tag Manager from Goole Analystics it starts to collect the visitor info from other domains that even don't have the tag. These domains share same IP address but it shouldn't be the problem I guess. Any idea?
There can be many problems. Lets look at it:
do you manage the other pages?
is it possible you accidentally deployed the tag to this domains?
is it possible that you maybe accidently didnt change the UA-ID in
the tag you deployed?
check them with Google Tag Assistant extension installed and enabled
in Google Chrome for Google Tag Manager tag, its really on the page? see 3) with what UA-ID?
is there maybe standard Google Analytics tracking left on the other
domains?
Let me know I would like to dig into your problem and help it fix it. It really looks like some previous tag was forgotten on the other domains. There is no way how domain without any tag could appear in your GA, except of course the traffic spam bots, which can be filtered.
In that case refer to this page http://help.analyticsedge.com/spam-filter/definitive-guide-to-removing-google-analytics-spam/ which is kept up to date. Especially focus on Valid Hostname filter, but be careful with the deployment. Always preview, debug and test, before putting in into your main view in GA.
Well, the question is in the title. I searched SO (obviously) but nothing similar came up. Additional reading material (if you happen to know one) will be helpful to solve this mystery for me.
No, not by default at least.
It is technically possible to contrive a serverside solution that measures referenced assets. But usually (i.e. when you use the javascript tracking code) Google Analytics will only measure documents that have the tracking code embedded. Since you cannot embed javascript code in image files they will not be tracked.
If you want to see which images have been called from other domains you can instead have a look in your webservers access logs which keeps track of all requests to your server and usually includes the address of the referring site.
Folks,
I am working on an app that hosts certain pages from a different site in an iframe. Because the site is on a different network, I get prompted to log into their network in order to show the pages. All that is fine (the users of this site will be on the same network, so I'm not worrying about their logging in.)
However, on a different page, same app, I'm trying to do the same thing with a different set of pages from that same site. This time, I don't get prompted to log in, but do get the DNS Error page in the iFrame (I'm doing this in IE9, if it matters.) If I click "return to previous page" on the DNS Error page or right-click and click Back, the home page of the app (on the different network) appears in the iframe. After that, trying to load the desired page in the iframe works. But I'm baffled as to why and would prefer it load the first time I try it!
I'm guessing that the conjunction of the hosted pages being secure (HTTPS), their being on a different network, the iframe, and possibly also IE9 are somehow causing this. Anybody have any ideas?
Thanks,
Ann L.
If you go directly to the url that the iframe is pointing at do you get that same error or does it work? And make sure you go to the page the iframe is looking at and not what you think it is looking at. It may be that at some point in your process the page is generating the wrong url for the iframe.
The other thing is that it may be worth using fiddler to check your traffic to see if these other pages are trying to do some kind of redirect on you - they may be checking referrer and not liking connections from outside their network or similar.