If you want seperate reporting for the main domain and it's subdomains, then the seperate GA properties will be fine.
Keep in mind the subdomain traffic will not report as referral traffic to the main domain, and vice versa, together with traffic moving between the subdomains. This is due to the default behaviour of GA regarding the referral exclusion ...
The simplest solution would be to redirect the user back to the home page with a URL parameter:
Adding a URL parameter to the URL usually shows the same content, but creates a different URL that can be used as a destination goal in Google Analytics.
A different solution would be to send an event from the home page when the ...
You could create public reports within Data Studio using the GA Data and then embed these into a website.
More information on embedding DS Reports here:
Since you are using Google Analytics, Google Tag Manager seems like an obvious solution.
It is free, and it's possibilities are almost limitless, as it can help you track almost anything that a visitor does on your website.
If you want more visual data, checkout Hotjar.
Of course, there are plenty more tools out there, these are just my personal preferences.
While you won't see any changes to your SERP positions or indexing regardless of which path you take here, you're doing the right thing by having internal links open in the same tab. (As @closetnoc pointed out above, including the attribute at all is a bit redundant, since the default behavior of links is to open in the same tab, unless otherwise specified.) ...
Is the GA tracking configured to anonymize IP data?
If so, then IP filtering will not work as expected, as anonymizing IPs masks the last octet of the IP address.
In these instances you have a few options:
Adjust the filter match to that begin with and leave the last octet in the IP address blank. Keep in mind, this may have the unintended result of ...
David is correct. Basically GA records the Session hit only for the Landing Page (first page) of a session and not subsequent pages.
Hence if you are looking for the number of sessions in which a particular page was viewed, one should look at the Unique Page View column.
One can view this by following the below path
Behaviour -> Site Content -> All Pages ...
Create a content group for urls containing /contact, this will preserve the fbclid data in case it is needed for future reference. This method also allows you to create additional content groups for your entire website. Your traffic sources likely append additional parameters on other pages as well.
This can be solved easily in Google Analytics settings. Go to Admin -> View settings and add fbclid to Exclude URL Query Parameters input box:
Analytics will strip this parameter off from now on. As this is a view level setting, you might want to repeat it for all your views, where you find this parameter to be irrelevant.
You probably want to set up cross domain measurement as it is used for the exact situation that you describe.
I'm not sure if Stripe will let you add a your GA/GTM snippet to your checkout page, but I suspect they probably will, the documentation linked above and the related pages will tell you how to set this up.
I don't think that is possible via real time reports. Real time reporting offers a limited set of data and standard ga segments do not work with real time reporting.
To see what is offered by the real time reporting, more specific information can be found on the following page