{"id":17275,"date":"2014-10-16T13:41:45","date_gmt":"2014-10-16T17:41:45","guid":{"rendered":"http:\/\/blumenthals.com\/blog\/?p=17275"},"modified":"2014-10-24T10:30:00","modified_gmt":"2014-10-24T14:30:00","slug":"google-local-pages-no-longer-supporting-ga-tracking-codes","status":"publish","type":"post","link":"https:\/\/blumenthals.com\/blog\/2014\/10\/16\/google-local-pages-no-longer-supporting-ga-tracking-codes\/","title":{"rendered":"Google + Local Pages No Longer Supporting GA Tracking Codes"},"content":{"rendered":"

Update 10\/24:<\/strong> I have tested the ? and it now seems to be working. It appears that Google has fixed this. <\/p>\n

Update: Solution found!<\/strong> Tony \u201cTiggerito\u201d McCreath<\/a> has figured out that apparently the problem is caused by the ? in the GA code. If you replace the ? With a # symbol it works, redirects without the ugly error message and still provides the data to GA. <\/p>\n

Historically if you wanted to measure traffic to your site from Plus page for local you could add a Google Analtyics tracking code to your site’s URL. <\/p>\n

Whether this is a bug or not or permanent change is not yet clear but since around the first of the month if your link in the G+ Dashboard to your website includes a tracking code, Google throws off this ugly message. This new behavior was pointed out to me by Alyssa Vanderpool of RedNovaLabs<\/a> in the Local U forums<\/a>. <\/p>\n

\"error-message\"<\/a><\/p>\n

We have inquired of Google whether the action is as intended or is a bug. Until such time though as we find out or its fixed, you should remove any GA tracking codes added to your local listing.<\/p>\n

Update 4:00 PM<\/strong>: Sharon Conner of Sleeptrain<\/a> pointed out<\/a> in the comments that this is not affecting when the listing shows in search results and I have determined that it isn’t a problem from Google Maps either. It only manifests itself when clicking through from the G+ Page. Thus not a bad as originally thought and most likely a bug in G+ rather than some intentional policy change. <\/p>\n","protected":false},"excerpt":{"rendered":"

Update 10\/24: I have tested the ? and it now seems to be working. It appears that Google has fixed this. Update: Solution found! Tony \u201cTiggerito\u201d McCreath has figured out that apparently the problem is caused by the ? in the GA code. If you replace the ? With a # symbol it works, redirects …<\/p>\n","protected":false},"author":262,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[24],"tags":[],"class_list":["post-17275","post","type-post","status-publish","format-standard","hentry","category-google-plus"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t