Hi, I'm trying to setup better analytics on a site with subdomains. In order to do that, I followed instructions on this help page: https://support.google.com/analytics/answer/1034342?hl=en On my main site (domain.com) the plugin setups and run smoothly, but every time I try to set it up on a subdomain using the same property ID, I get an error "pick a value not less than 1" (not sure if those are the exact words as I get the error message in spanish). I used the "Auto configure" button on one of the subdomains and it created a new property ID, but again, every time I press "Save Changes", I get the same error. Any ideas on this issue?
It really shouldn't matter if you use the same property ID on multiple sites. Can you post a screenshot of the exact error you are getting by chance? Also, that page you gave is for cross-domain tracking (pretty rare you would actually want to track domain1.com and domain2.com on the same web property). If it's the same sub-domain (on the same domain), you don't need to do anything special.
Thanks for your reply. I'm using the information on the help page mentioned above because I want visits to subdomains tracked as if they were different sites. I'm rather newbie on analytics so maybe I'm doing something wrong. Here is the screen capture you asked for. The meaning of the message is: "choose a value not less than 1". Have a good day.
That's a browser input validation message (it's not coming from the plugin directly). But the only thing that should trigger a message like that would be the setting on the "Advanced" tab. Specifically if the "Sample Rate" is set to something less than 1 (or nothing). In *theory*, it shouldn't even be possible to have been set to 0 or nothing unless something internal to WordPress wiped out the Better Analytics settings since it sets it to 100 by default when you install the plugin. Either way, check that setting and make sure it's set to something greater than 0 (it defaults at 100).
It was that you said. Problem solved!! Thanks a lot! P.S. FYI, the plugin original setting of 100% was kept on the main site, but wiped to zero on the subdomains. I've set it back to 100% and worked like charm.
Good to hear. I've added an internal mechanism that will be part of the next version that should prevent that from happening in the future.