I need to set up a filter (or segment) that excludes web app traffic.
On our site we have a button on the top right that takes the visitor to portal.domain.com which is where the web app is hosted.
I need a GA view that shows me traffic in which they have not clicked this button and gone on to use the web app.
Whats the best way of setting this up?
Thanks
Add a filter to exclude, campaign source and set it to your domain. That will remove hits in the view that came from that URL.
You should be able to read the traffic that you want using a filter.
Is that page tracked by the same GA Account? If so, you set the filter to have a condition that excludes that page (although you'd probably identify it using its hostname, and you'd also have to be careful about cookie domains).
Alternatively, you could throw an event that triggers when people depart for that page, and then use that in the segment above.
Related
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.
I am creating a Web Widget, a page that customers can use within an HTML Iframe in order to embed our experience on 3rd parties and vendors.
The site will be public, I am not willing to ask consumers to register in order to have a key or a unique identity to be passed as a query param for example (e.g. ?id=<unique_id>).
On the other hand, I need to track who is using the iframe. What are my options? A colleague suggested using the request headers, such as the origin, to track the usage on the server-side. Is that a good strategy? I'm not sure how much I can trust the origin header.
What if I fire an event (hence a client to server call), at page load (such as analytics) which logs the current page URL? Would that work, from within an iframe?
I am pretty sure I am reinventing the wheel here. What would be some good recommendations?
Thanks!
For others ideating for a similar solution, my fix was actually to simply hook a proper client analytics to the page, and trigger a page load event, upon page load, which would push not just the page, but quite a few other properties to our analytics.
Also, we added a clientId query param to our urls, so that we could identify precisely who was serving the iframe visited by the user.
I have an HTTPS site which runs on SSL since years, also the Google Search Console is configured with HTTPS. If you lookup a page of that site through HTTP, a redirect to HTTPS will take place.
Now I found out, that within Google Analytics > View Settings, the property Website's URL ist still configured with HTTP (in that dropdown menu there). But in Google Analytics > Property Settings, it's correctly configured with HTTPS.
As I don't want to create a negative impact on any data collected within the last 10 years, would the property change have an impact on the data? Why is it important that this property is actually on the currently used protocol? Because data is collected, everything is actually there, so why should I need to change it?
Thanks
That setting has no impact on data. It doesn't change automatically, you have to be the one to set it. It is used, for example, to preview the page by clicking on the icon in the page report.
I don't want to be counted as visitor every time I test my page in the hosting. Does Google know i'm the owner of the site by checking if i'm logged in my Gmail account?
I don't think Google does anything like this automatically. But they do provide instructions for excluding based on IP address (or range) and apparently also now by cookie. If you use a CMS or admin interface, you could put the code they provide in an HTML file that you then include into the admin interface pages by IFRAME (to ensure that the cookie stays set for anyone who uses that interface).
One option is to install Ghostery addon your browser. Ghostery can block trackers and scripts used on webpages likes google analytics, google adword and other adwares.
You can also block or unblock the trackers for a specific site or specific tracker for a particular site.This add on is available for Firefox and chrome browsers. If you have this installed on your browser, your visit wont be counted as google analytic script wont be executed.
You can learn more about ghostery at: http://www.ghostery.com/about
There are also often application specific ways of blocking google from counting administrators. For example I've used a wordpress analytics plugin that would automatically not include the tracking code if the user was logged in as an administrator. If you are application has the concept as admin then you could write something similar that controls when the code is added.
If you visit your site frequently from connections with a dynamic IP address, eg. home broadband, then excluding IP addresses is not particularly practical. To go beyond IP exclusion, you can create an isolated page on your site that only you know about that includes a call to Analytics to label your cookie.
The Google Analytics _setVar() function lets you label yourself with an arbitrary string, eg. 'internal'. You only need to do this once per browser as long you don't clear your cookies.
Having labelled yourself as 'internal', you can create an Advanced Segment within Google Analytics to exclude visitors with that label.
Google Analytics relay on you embedding a call to their JavaScript see this link - do not confuse it with how Google does page ranking.
So the answer to your question is that your pages should be smart enough to recognize when the request comes from you and skip the call to the JavaScript.
I have a site running Google analytics and I end up being a large fraction of the traffic to it (like 1 of the 2 hits per day). Is there any way I can set it so that my browsing doesn't skew the numbers so much? I'd be happy if it just didn't record anything for accesses that are logged in as my Google account.
Use the Filter Manager in your analytics settings
http://www.google.com/support/analytics/bin/answer.py?answer=55481&cbid=-1j8it19c4uzvt&src=cb&lev=answer
You can use filter to exclude
Traffic from a a domain
IP address
Sub directory
or you can use a custom filter. You can edit your site to set a campaign code if you login in and use the custom filter to exclude that campaign code.
You can also try out the ip filter if you use the same machine.
One option would be to use an ad blocking or javascript disabling extension in your browser to prevent google analytics from being loaded.
A neat solution is to simply stop the tracking javascript from being sent to the browser based on a cookie set on your machine. This can be done by simply adding a few lines of code to your page. Take a look at this article for a full explaination.
If you login there logged in as a site user, maybe you basing on this you just do not put the JavaScript for Google Analytics in the output HTML. This is a typical case when you are an administrator and you do not want to mess the results basing on your activities.
If you are able to touch the code that runs your site I think this is the simplest way to go.
If it is not the case, please provide some more details.