# Verwenden Anyone Cloudflares Google Analytics App?

**URL:** <https://meta.discourse.org/t/anyone-using-cloudflares-google-analytics-app/76464>\
**Category:** Data & reporting\
**Created:** [20. Dezember 2017 um 02:42 UTC](https://meta.discourse.org/t/anyone-using-cloudflares-google-analytics-app/76464 "2017-12-20T02:42:00Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Johani](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/johani/32/176920_2.png) [@Johani](https://meta.discourse.org/u/Johani)\
**Post date:** [20. Dezember 2017 um 03:30 UTC](https://meta.discourse.org/t/anyone-using-cloudflares-google-analytics-app/76464/5 "2017-12-20T03:30:00Z")

</div>

I think this occurs because the cloudflare app injects the Google analytics script in the `<head>`.

This works well if you’re on a regular website where new html pages - and new `<head>` elements - are loaded on navigation, but it does not work well with apps like Discourse.

Discourse as a Single Page Application only loads the `<head>` once and swaps the `<body>` content on subsequent navigation.

This results in Google Analytics thinking that only 1 page has been viewed and the behavior you described

> [@SouperC](#):
>
> After digging around today, all I can say is that for some reason the GA code delivered by Cloudflare was only picking up (and was stuck on) the page url that a visitor landed on.

Discourse has it’s own method of letting Google Analytics know that the page has changed on user navigation, and has it’s own Google analytics fields in the admin to ensure proper implementation.

---

_[View the full topic](https://meta.discourse.org/t/anyone-using-cloudflares-google-analytics-app/76464)._