• Resolved Joe Alberts

    (@joe-alberts)


    It’s definitely active on the site, but Google Analytics won’t seem to validate the tracking code change. Has anyone else seen this occur?

    To be more specific, the proper require is set via:

    ga('require', 'displayfeatures');

    It also occurs in the proper position (after the create call, and before the send one). I haven’t found any indication that its order relative to setting forceSSL should have an impact.

    When clicking on Validate tracking code in Analytics Audience > Demographics > Overview (note, it has been enabled), it simply fails to validate.

    Any thoughts?

    https://wordpress.org/plugins/google-analytics-for-wordpress/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Same thing here. I can see it in the HTML, but GA just won’t validate it.

    Same problem here.

    Remember to clear your cache (for your site) if possible before trying (I didn’t, unfortunately).

    I’m also seeing the proper code in page source, so I don’t think this is a plugin issue, but a Google issue.

    If it makes you feel any better, I’ve had LOTS of these kinds of problems with Google authenticating stuff in general. I even sat on their support one time for nearly an hour, while the tech tried to fix it. The tech indicated he could see the codes, but the system just wouldn’t. It worked after waiting several hours.

    So far, no luck with this one though, and I know it’s been at least a few hours. I’ll try again tomorrow.

    Enable Universal tracking will disable Demographics: Overview.
    To view Demographics: Overview, you have to uncheck on “Enable Universal tracking…”

    Just wanted to report back that after a day or two, it validated just fine (no change on my end). So, I’m pretty sure it’s just a typical Google-side issue.

    Thread Starter Joe Alberts

    (@joe-alberts)

    Thanks for reporting back. You prompted me to give it another go, and I got the same result you did. No changes made, but it suddenly validates fine.

    Weird.

    I’ve had this happen for other kinds of Google authentication as well. My guess is they have caching on their own end that the systems that check this stuff can’t work around.

    Yeah it’s an issue on Google’s side that’s very annoying to us, as we can’t do ANYTHING about it…

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Demographics & Interest Reports don't validate’ is closed to new replies.