Keep a reference to your history object. i.e. import { createBrowserHistory } from ‘history’; var history = createBrowserHistory(); ReactDOM.render(( <Router history={history}> […] Then add a listener to record each pageview. (This assumes you’ve already set up the window.ga object in the usual manner.) history.listen((location) => { window.ga(‘set’, ‘page’, location.pathname + location.search); window.ga(‘send’, ‘pageview’); });
Putting it at the end of the <head> section helps ensure the your metrics are tracked even when a user doesn’t let the page finish loading. They used to tell you to put it at the bottom of the page, before they added support for handling partial loading of pages. Directly from Google: One of … Read more
This should do it: ^(?!.*details\.cfm).*selector=size.*$ ^.*selector=size.*$ should be clear enough. The first bit, (?!.*details.cfm) is a negative look-ahead: before matching the string it checks the string does not contain “details.cfm” (with any number of characters before it).
I had this problem too. I fixed it by adding the email address for my service account to the Google Analytics profile I wanted it to access. I got the email address (something like xxxxxx@developer.gserviceaccount.com) for the service account by looking under the “API Access” tab in the Google APIs console. Then, I followed Google’s … Read more
Content Experiments for mobile apps are DEPRECATED and it is removed.
I like the simple approach of using javascript. It works anywhere. <script type=”text/javascript”> if (document.location.hostname.search(“myproductiondomainname.com”) !== -1) { //google analytics code goes here } </script>
Google used to recommend putting it just before the </body> tag, because the original method they provided for loading ga.js was blocking. The newer async syntax, though, can safely be put in the head with minimal blockage, so the current recommendation is just before the </head> tag. <head> will add a little latency; in the … Read more
EDIT (2019): The below answer predates GDPR and likely requires revision. Google Analytics has a new set of APIs to assist with compliance with a cookie opt-out. Here’s the documentation, and here’s their help docs. There has been some ambiguity as to whether the EU Cookie Regulations (as implemented in member countries) require that passive … Read more
The async support as specified by google is achieved using two parts: using script on your page (the script is supplied by google) to write out a <script> tag to the DOM. that script has async=”true” attribute to signal to compatible browsers that it can continue rendering the page. The first part works on browsers … Read more