Will changing the property from http to https in Google Analytics affect main unfiltered view?
-
I set my client up with an unfiltered view in Google Analytics. This is the one with historical data going back for years, so I don't want to do anything that will affect this view. Recently, the website moved from HTTP to HTTPS. There's a setting for the property that will allow me to change the property name to https://EXAMPLE.com and change the default URL to https://EXAMPLE.com. Questions:
1. If I change the property name and the default URL, will this somehow affect my unfiltered view in a way that I'll lose historical data or data moving forward?
2. I have heard that changing the default URL to HTTPS will help me avoid a common problem others have experienced (where they lose the referrer in Google Analytics and a bunch of their sessions go to direct / other). Is this true?
-
Hi, I'm so glad i found this. I have a similar situation. We are changing from http to https.
Just to make sure i understand this correctly. We do not need to change anything in GA. But modifying the property name to https will reinforce what we did?
Thank you. Julie
-
I love the professional passion, Verónica and Paul!
Verónica, Paul's response was more specific to my question about Google Analytics, but I appreciate you bringing up related issues with Google Search Console.
-
It clarifies, thanks! That's the info I needed. I appreciate it.
-
"The wrong name in the 'Property name' field or wrong setting in the http_ or https doesn't affect the data collection in your GA account." _I know - which is why I explained that changing the protocol there to HTTPS won't have any effect on the archive View either, which was the OP primary question.
"...verify all the properties and choose the preferred one" will not have any effect on "help[ing] me avoid a common problem others have experienced" as you state. That problem (Referral visits recorded as Direct in GA) is caused by the referral data being stripped out of the request when it travels from an HTTP site to an HTTPS site. There's nothing in GSC that can have any effect on this - it is entirely controlled by the server headers of the connection request.
There's nothing about Kevin's original question that has anything to do with or can be addressed in Search Console.
P.
-
Hi Paul,
The wrong name in the 'Property name' field or wrong setting in the http or https doesn't affect the data collection in your GA account. The data is collected via UA number in the GA tag for your website regardless of the domain your GA tag is on.
Assuming GA is linked to Google Search Console, where it is essential to verify all the properties and choose the preferred one for getting accurate data, plus this will "help me avoid a common problem others have experienced".
Mª Verónica
-
He's talking about the effect of updating the default URL in the Google Analytics Property Settings, Veronica - nothing to do with Google Search Console.
P.
-
Lemme try that again
1. Updating the protocol in your GA Property settings won't have any harmful effect on your archive view (or any other view).
2. Setting the Property address to HTTPS isn't what's going to determine if the incoming referral data is available - that's been determined before the visits actually arrive by the browser connection and server headers. If the visit to HTTP is coming from HTTPS, the referrer data was stripped out before the request was sent. GA just uses whatever it receives. (My point was, even if you don't set the protocol to HTTPS in your Profile, the referrer data will come through anyway. But getting your GA set to the correct HTTPS address reinforces this, so still a good idea.)
Hope that clarifies?
Paul
-
Hi, Paul. Sorry, I wasn't sure from your response...
1. I understand that "updating the protocol to HTTPS won't have any negative effect on your archival GA view." By this, I think you mean updating the actual website protocol (not making changes in Google Analytics.)
So, within Google Analytics, if I change the property name and the default URL to HTTPS, will this somehow affect my archival view of Google Analytics in a way that I'll lose past data or data moving forward?
2. I think you are saying that if I change the property name and the default URL to HTTPS within Google Analytics, I "should" be able to see the referrer properly and not lose the referrer and a bunch of their sessions to direct / other. Is this right?
-
The short answer, Kevin, is no, updating the protocol to HTTPS won't have any negative effect on your archival GA view.
Just having the visitor connection resolve at the HTTPS address "should" transmit the referrer info fully (it's the browser that determines this, not GA), but always good to back this up by having the GA property properly configured for the HTTPS update.
Little sidenote - since your site is now HTTPS, any referrals it sends to other non-HTTPS sites will get stripped. If it's important to you to have those other sites recognise you sent them traffic (this is important in some partnership/affiliate,/advertiser situations for example) you can add a Meta Referrer tag to your site so that it will send at least some of the referrer info even to a non-HTTPS site. You can select how much info gets passed based on your security sensitivities.
That what you were looking for?
Paul
-
Hi Kevin,
Assuming that you set up a 301 (permanent redirect) from the http to the https:
How to do it?:
https://support.google.com/webmasters/answer/6332964?Where?
https://www.google.com/webmasters/tools/What properties?:
http://example.com/
https://example.com/
http://www.example.com/
https://www.example.com/After all those were done:
Into this property only: https://example.com/ (Assuming that you prefer the https non www version)
verify the robot texts
upload a sitemap
fetch as google
You will see data starts to be shown and index within a few days.Forgot to mention the bad news on regard a migration to https, due to Google considers the https a new website, it will crawl all as "a new website".
That is great at first, though any failure from old times will appear with "red flags" because the 2017 algorithms will work. I mean broken links, 404s and so, that you didn´t know those were there, will be shown up.
That is why it is highly advisable to perform an SEO audit and fix up all, before a migration.
Although, in many years of SEO practice, only one client came before the migration.
You do NOT change the Analytics code, therefore it will continously showing old data and new data into the same view. Good luck!
Mª Verónica
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Increase in Direct traffic, drop in Google traffic, after updating Google Analytics settings.
I made some changes to our Google Analytics property settings (see notes in screenshot). As a result, there was an equal drop in Google traffic and increase in Direct traffic. Has anyone else seen something like this before? I'm wondering if I should revert. jE7buO6
Reporting & Analytics | | vcj0 -
How can we stop Google analytics pulling in data from another site?
We have a few accounts under one Google login. They all have separate Google analytics codes but one of the sites is somehow pulling in some data from another site but the other site has not got the same analytics code on it. Not sure how this is happening and what we can do about this, is it a bug in the Google Analytics system? Any help would be appreciated.
Reporting & Analytics | | dentaldesign0 -
No Google Analytics code on page BUT reporting is active
How could Google Analytics be reporting data if my pages don't have the GA code on them? Mike
Reporting & Analytics | | Mike_c0 -
Multiple domains to one payment sub-domain in Google Analytics
Hi Mozzers, I have a series of sites (~25) that are all regional e-commerce sites with the same URL structure eg. www.[region]-product.com as well as a 'master' site (eg www.product.com). I also have a single Adwords PPC account which point to all of the regional sites as well as the master site. As part of the payment/checkout process you only ever get taken to a sub domain of the master site (eg payment.product.com). My question is: Is it wise to use the single PPC Adwords account to set up an Analytics account under which I list all of the regional sites and the master site? Once that's done I'm not entirely sure how I can track sales from a regional site to the payment process of the master site and have sales correctly assigned to the right domain. On the payment process I can only use one site ID tracking code so I'm not even sure I can correctly assign a transaction to a single site if multiple sites use the same payment pages. Example: Visit to region-product.com > Quote form submitted to payment.product.com > Payment completed on payment.product.com > Sale is assigned to which domain? Can anyone who understands what I'm trying to achieve comment on the plausibility of this? Many many thanks!
Reporting & Analytics | | panini0 -
Google Analytics Report throws up Google as a referrer
Good morning from Wet & Windy 12 degrees C wetherby UK... Using Google analytics I've noticed in the traffic sources refferer subsection some traffic is categorized as originating from Google. Whats puzzling me is.... I know a huge amount of traddic stems from Google but as the below screenshot illustrates only 21 visitors come from Google: http://i216.photobucket.com/albums/cc53/zymurgy_bucket/google-refferal-sources-top-levelcopy.jpg And when i drill down some are coming from Google mobile 😞 http://i216.photobucket.com/albums/cc53/zymurgy_bucket/google-referral-sourcescopy.jpg Is traffic categorised as Google referrer down to Google hiding searches via ssl as explained here: http://i216.photobucket.com/albums/cc53/zymurgy_bucket/google-referral-sourcescopy.jpg Any insights welcome 🙂
Reporting & Analytics | | Nightwing0 -
Looking for a solid educational piece for continuing education for our staff on Google analytics.
Particularly, the updates that have been made in the last few months with the new interface. Any suggestions? Book and course are of interest.
Reporting & Analytics | | DavidWolf580 -
How to Turn Google Analytics Into Your Own Rank Tracker Using Custom Variables
I followed the instructions here http://www.seomoz.org/blog/gettings-rankings-into-ga-using-custom-variables, but cannot see the report in Analytics under "Custom Variables". As I dont know JS syntax, I assume the code is wrong. I just added dohertyjf's code under my normal tracking code. Can someone tell me if and where the error is? | | Much obliged!
Reporting & Analytics | | zeepartner0 -
Setting up Google Analytic Goals to a 3rd Party Site
I recently received help on a question I asked on SEOmoz but need additional clarification. I am trying to set up goals in Google Analytics for people who click on a “purchase botton” which sends them to PayPal. I created a Thank You page and tried to get PayPal to redirect to it, however, our customers only get to our site’s 404 page. Here is what I’ve done so far: Went into my PayPal account and turned the “Auto Return” to ‘on’ Under website payment preferences, I added the following URL http://www.teecycle.org/thank-youutm_nooverride1. (I formatted the URL this way because the person who provided me with help recommended using the format ?UTM_nooverride=1. However, our CMS system won’t allow “?” or “=”)
Reporting & Analytics | | EricVallee340