I need help with the following case. My client has a website where the catalog and product informations is on the main domain https://fixed.zone from the product cards links to the eshop which is on the subdomain https://obchod.fixed.zone
I need the person who clicks through from the root domain to the eshop to be a referral in GA4. It now appears as Direct.
Can anyone advise me how to achieve this? The GA4 code is only on the eshop. It is not on the catalog page. I didn't set up the analytics on the main domain but someone else did. However, I can also intervene in the website on the root domain
I tried to google the solution but it seems to be kind of rare set up
Referral attribution is something you typically don't touch. It's something Google comes up with on its own. If this dimension doesn't do the trick, you just use a different dimension, like the actual referrer, or a segment where you select sessions that have both hostnames.
Still, there is a way to trick GA. A few ways, actually. For example, you could have logic in GTM that would run on subdomain that would check user's document.referrer on every hit before sending pageview. Once the referrer is from the TLD, you override the referrer dimension in the call and replace the TLD in it to something else, that way those hits will look like they came from a different TLD and will be treated as referral traffic.
Or you could issue an event every time a user navigates to the subdomain, so you could just look at those events.
Same issue here. Managing a GTM container and GA4 property for a subdomain that is separate from main domain. By default in GA4, it appears as though the main domain traffic is lumped in with direct traffic rather than a referral. We need isolated referral data from main domain to subdomain in GA4. Lumping the traffic into direct will not work for us. The UA property for the same subdomain lists the traffic from the main domain as a referral.
I created a GTM GA4 event tag for traffic tracking.
parameter name: referrer_URL
value: {{HTTP Referrer variable with component full URL}}
trigger: Page View - trigger fires on: {{HTTP Referrer variable with component full URL}} does not contain "my.subdomain" (to exclude self-referrals)
created custom dimensions in GA4 for new parameter "referrer_URL" so it will be visible in reports
After approx 24hrs my new custom dimension started showing up in reports.
In GA4 reports->Acquisition->Traffic acquisition click the "+" next to first column header of "session default channel group" and select custom->"your.custom.dimension" (or search for your custom dimension). Default channel groups should be broken down further into your custom dimension urls.
Related
In Google Analytics, I have navigated to All Accounts-> SomeDomain.
I see a lot of traffic to that domain.
However, most pages listed there are from another domain of mine.
Real-Time for example shows this:
This is hilarious because this page doesn't exist on that domain.
I thought that it shows only traffic to the domain that I have selected above after "All accounts".
Is that not correct?
Or does anybody know any situation where this might happen?
This goes on since months already.
My GA is managed via GTM.
I don't use any CMS.
In GTM, I have a GA Page View Trigger:
I don't see where I could have made a mistake.
Does anybody do?
Thank you.
Create a custom report with dimension Hostname and metric Sessions (for example). You'll see what domains send data to your GA Property.
May be somebody stole code of your site (including trackers).
You can filter alien domains in GA settings for View.
UPD. Lookup table to push GA ID's depending on Hostname.
I have my UA setup across three sites www.aerserv.com, platform.aerserv.com, and support.aerserv.com. I want to be sure I'm tracking users across the domains properly so the analytics don't see each visit from one user as a "new user".
Is there a way to verify that I've setup my tracking correctly and Google isn't mis counting visitors?
Subdomain tracking is done out of the box in GA, and the only thing you need to make sure is that the cookie domain setting is set to 'auto', and that the referral exclusion list includes the main domain. Once you have those set, and if all pages across all applicable subdomains are tagged, then you should not have any issues. If you need to check, then you can look at the client ID (cid) for each pageview hit from one subdomain to the next. The client ID should be the same.
Is it possible to set up google analytics for more domains with one real time monitoring.
I have one main domain and 100 subdomains.
Example:
main.com
sub1.main.com
sub2.main.com
sub3.main.com
...
I want to track visitors in one google account with one real time monitoring. How can I do that?
Thanks
You do that by adding the same Google Analytics tracking code to multiple domains. The base domain from the Property/View settings are not relevant for data collection, so the same code will run on arbitrary domains.
(edited) Even less of a problem with subdomains. The default setting for the cookie domain is "auto", so the same cookie will be used for all subdomains. If you do not want this (e.g. if you want a user who switches between subdomains to be considered a new user) then you would need to set the cookie domain dynamically to the respective subdomain:
ga('create', 'UA-XXXXX-Y', {
'cookieDomain': document.location.hostname
});
However by default the reports displays page paths, so you might not be able to tell from which domain a request originated; to do that you need to add a filter to your view that adds the hostname to the page path. An older but still working tutorial is e.g. here.
Naturally everything that shows up in real time monitoring will later become part of the permanent reports.
I have a web site which has many microsites.
I want to use Google Analytics to track the traffic of each individual Microsite as opposed to tracking traffic of the whole site?
I have looked at Google Tag Manager, but I am not sure if this is the right solution - how can this be done?
Thanks
There's two basic ways in which this can be done:
If you don't care about inter-microsite traffic, you can just create a different GA property for every microsite and use Google Tag Manager to create your GA tracking tag with the right property ID depending on the hostname (using a lookup table variable, for example).
If you want to be able to see traffic flow between your microsites (i.e. not have a visitor navigating from one site to another show up as a referral but as the same session), then you should use the same GA property for all sites and set up cross domain tracking. Then inside your GA property, you can set up different views based on the hostname dimension of the hits.
The set-up:
1 site, 2 domains: = mysite.com and mysite.co.uk
These 2 domains use DNS to point to the same site (IP).
There is 1 snippet of Google Tag Manager (GTM) code just after the opening <body> tag of the site (every page).
In the GTM container, I have added both domains on the "Container Settings" page.
There is one Google Analytics (GA) account which only contains the .co.uk domain. (An analytics account can only contain 1 domain.)
A tag has been set up in GTM with the type of Google Analytics and it has the UA code from the 1 GA account added.
A rule has been added to fire on all pages
Now, I don't care whether someone visits via .com or .co.uk, but I want to capture combined analytics for both. My questions is, with the way I've set things up using GTM, will GA save data for both domains ie mysite.com and mysite.co.uk, or do I need to set things up another way to achieve this? Ideally, I don't want to go down the forwarding route i.e. forward all traffic from .com to .co.uk.
First a bit of pedantry: Google Tag Manager cannot even collect informatiom from a single domain (it's not a tracking tool). And while you can only enter one domain in Google Analytics that domain setting serves no actual purpose; a Google Analytics account can track multiple domains in different "properties" (porperties are sections in an account that each have a unique id) or in a single property via cross domain tracking. Cross Domain tracking is used if you want to treat multiple domains as a single presence on the web (i.e. if you have a website and a shop with different domains, they still belong together).
Now, the way you have set things up data will be collected from both domains. There are at least two caveats:
1) If users can switch between domains inside a session (go from .com to .co.uk and back) their sessions will be interrupted and Google Analytics will register multiple visitors (that's because users are tracked via cookies which are domain specific). To avoid that you'd need to set up cross domain tracking (and how you would do that depends on if you are using Universal Analytics or asynchronous code. Look at your tracking code, if it contains a line that starts "ga("send"...." your are using analytics. If it contains lines that start with _gaq.push you use asynchronous code).
Cross domain tracking documentation for UNiversal Analytics (analytics.js)
Cross domain tracking for asynchronous code (ga.js)
2) By default Google Analytics tracks only the path, not the domain. If pages on both domains have the same path they will be displayed in aggregated form in the reports, that is if you have an index.php on both pages the visits for both will be added up. Maybe that's just fine with you, if they show the same content in any case. Else you'd either have to use "hostname" as a second dimension (which is not a sticky setting, you would need to re-apply that every time you switch to another report), or you create a filter on your view that includes the hostname in the reports.
Those caveats are relevant because data will show up in any case and will look perfectly okay even if it's not (even if you decide that those two things do not bother you you need to take them into account when you interpret the data).