I have cross domain tracking set up on my site, A.com so I can track conversions in my other site B.com in the GA for A.com .
But I have an iframe that I need to put on my site. It will embed a form that people will use to get to a link to my other domain (the one that is connected with cross domain tracking). That form is embedded from another domain, example.com. I was able to go into my dashboard on example.com and place my GTM code in the iframe.
Since that link will be embedded, it will no longer pickup the user, since the user will be technically coming from example.com and not my site anymore.
How can I track the users that go from A.com through the embedded form (example.com) to my other site, B.com?
Mainly I just want to be able to track user interactions on the embedded form, and conversion events on B.com.
If you can add your own code to the iframe (example.com), you can get it to talk to the parent domain (A.com) using the postMessage API:
https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage
If you set this up, you'll be able to track events on A.com as normal and then set up cross domain tracking with B.com.
Related
I have a small but not insignificant segment of traffic coming from a third-party landing page creation tool. The pages live on their servers and ultimately drive users to pages on our site.
All the URLs of these landing pages start with a subdomain of the platform, i.e., view.platform.com. The source should be that subdomain, and that's correct.
Referral paths however should start with "/our-account" and then whatever we set as the URL slug for the page, so the referral path of anything coming from these landing pages should only be paths like /our-account/july-sale, which some of them are, but the bulk (40%) of the traffic with a source of view.platform.com has a referral path of just " / " (or Full Referrer Path of view.platform.com/ if you use that dimension).
I should mention that we only have a handful of these landing pages right now (like 3) so we know for sure that the traffic with no referral path is coming from 1 of 3 places, we just don't know which one in the case of 40% of the total landing page traffic.
view.platform.com just forwards to the main website for the tool, and there's no way any of this traffic would be coming from there naturally.
Why would anything after view.platform.com be stripped from Google Analytics? Anyone have any thoughts?
The landing pages are HTTP, and they're linking to our site which is HTTPS, but I read that shouldn't be a problem. It's only an issue the other way around.
The landing pages are also not traditional regular HTML pages, but rather generated by JavaScript.
The landing pages also use symlinks if that matters. Users navigate to them as view.platform.com/our-account/landingpage/ but then it turns into view.platform.com/our-account/landingpage/p/1
You can consult this https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy and double check which policy is applied in the originating document.
You can also check the requests in the network tab to check which referrer is set in the request headers
You can inspect the requests that Google analytics send to its server to check what is being sent.
I have a GoDadddy account with hosting and domains (I know,,, GoDaddy sucks...), but I currently have multiple domains pointing to the same folder, and it has a single PHP page with the GA tracking code for a single domain. Because all the domains point to the same folder in the hosting, I see all visits for all domains as they are for a single domain in the GA panel. Is there a way to find out which visits come from what domain?
Currently GoDaddy has 3 hosting plans. The only two that allows you to have multiple domains are Deluxe and Ultimate.
How you conduct the implementation will affect the way GA reports the data. Now I am going to make the assumption that you have access to all the domains you said you currently have.
This is what you need to do to track your traffic
Check if you are allowed to have multiple Domains.
If Domains are not registered in Godaddy, make sure that all domains and the Primary Domain are pointing to Godaddy DNS or nameservers.
Add all domains as 'addons' domains or additional domains to your hosting account making sure you have a separate folder for each domain.
In each Domain Folder, create a basic HTML (index.html) page and paste the Google Analytic code in the Head section. Repeat this for every Domain.
Create 301 redirects to your PHP page that has the same Google Analytic code that you used for all the pages in 4.
IN Google Analytics Report you should be able to see all the redirected domains show as 'referral'.
Note: Sometimes the redirect might take place before the GA script is loaded and therefore you will not be able to track the referral. If you really care about absolutely all the referral traffic data, I will recommend you to not use 301 redirect but let the pages load and place a JavaScript redirect with a 5 second delay.
I have a share point website running on a server, and have a asp.net website that that is configured to run attached to the share point site. This this not exposed as a domain site( i.e. with .com or .in or .nl etc), i access this site in my development and test environment using a URL something like
https://www-dev-myname.domainname.local/
In google analytic i am not able to add this as default URL for an account, it does not allow me to save it.
Is there a way i can create a account with a URL of this type and setup analytic for my site.
You can simply enter a valid url - it does not need to be that actual url of your website, the only consequence is that you cannot user inpage analyses (that and the little icon in the page content report that allows you to launch a url in a new window).
Wrong domain name nonwithstanding Google Analytics will work on any domain where it can set a cookie (and if it can't you can set the cookie domain to none, in that case you need to provide a client id yourself to maintain session tracking).
We have Urchin installed for the server statitics. Our server has an intranet subdomain (of course, banned to the outer access). When I look for the referal of any intranet page, I found that almost half of the access are from "direct[(none)]" and "google[organic]":
"direct[(none)]" access includes bots, direct keyboard access,
pdf/documents links... and all of these have the acces banned, and
"google[organic]" access are done through the serach engine
that can't acces to index the page nor redirect to that
So, I must conclude that the statistics of Urchin are not faithful.
Can anybody confirm that terrible conclusion? Or can anybody explain and correct it?
There are several ways to install Urchin. In this response I assume you use the tag method.
Urchin will create traffic sources based on document.referrer, it doesn't guess, it uses real data.
When you install Urchin one of the options you need to set is the domain name. This setting is used to store a first party cookie that will hold session information including referral info.
Let's say your intranet site is intranet.mycompany.com, this subdomain is private to your network but maybe the cookie setting in Urchin is set to mycompany.com, this will create a cookie in that domain and this cookie will apply to all subdomains.
Maybe this hostname has other subdomains, some that might be accessible outside your corporation and since they share the same cookie, they will share the same traffic source as well.
google/(organic)
Imagine this scenario:
User Looks for Company in Google
User arrives at the main public site at www.mycompany.com. Urchin registers this as a new visit from google/(organic).
User opens the intranet website
Urchin uses the same cookie and this is seen as a continuation of the visit that already has a traffic source
Urchin just reuses the google/(organic) traffic source defined in the cookie.
Also Urchin can share cookies with Google Analytics, so if you are not using Urchin, but instead Google Analytics the scenario above is also possible.
direct(none)
Now about direct/(none). This is used everytime urchin can't determine a better traffic source. In other words when the javascript variable document.referrer is empty.
This can happen in a variety of moments, including but not limited to:
Clicks on a pdf document
Clicks in a Microsoft Office document
Directly typing the url in the browser navigation bar
Clicking in a bookmark
Going from an HTTPS to an HTTP webpage
I have a website subdomain.domain.com. I created an analytics account for this and included the tracking code. Later I registered a new domain xyz.com and pointed to the same website subdomain.domain.com. In Google analytics report, will the analytics display the traffic from both domains or do I need to make some alterations?
Google Analytics tracks website traffic no matter what hostname is specified in the page URL. You can use the Hostname dimension in the content report to find out.
In your case, depending on the type of hostname redirection you may or may not see the xyz.com in your reports. When you navigate to the xyz.com in browser, pick any page and can see in your browser xyz.com - it will be tracked. If you can see subdomain.domain.com - the last will be tracked.
If you website is accessible via subdomain.domain.com and xyz.com - you may have an issue with cross-domain users and duplicated (inflated count of) users since GA cookie in a browser is set per hostname
I have the same situation where our URL has changed and we are now in a crossover period while both URLs are active.
Without changing the tracking code I am getting our stats as before but I cannot tell in the analytics reports which URL the visitor used to access the site. If that is not of concern to you then you don't need to update your tracking code.
There is a secondary dimension under Content called "Hostname", this will break out your traffic by whether or not it was visited from subdomain.domain.com or xyz.com