Not well thought out
-
We moved to a new theme which did not include a Google Analytics option; the old one did and we had eight years of continuous user data. So we added this plug-in to restore the GA data, then configured the plug-in. The newly activated plug-in did not automatically inherit the GA code to allow dual tracking, so we lost the data for another few days until we added the code in again. There was no warning that we needed to do this.
Shouldn’t dual tracking be the default, with an opt-out, rather than the other way around?
-
> The newly activated plug-in did not automatically inherit the GA code
Plugins and themes don’t store GA codes in a standardized place, so there’d be no way for us to import your old code or know you had one unfortunately.
> dual tracking be the default, with an opt-out, rather than the other way around
So our dual tracking feature is designed to allow users who have an existing GAv3 property to see the analytics/reporting of their existing property while they also track into a new GAv4 property. There isn’t a way to make this a default persay, as a user would have to manually configure whichever property they want as the secondary property. We have been working with Google’s team on new automation APIs to make GAv4 secondary tracking a one click operation for users to make the process simpler, but we’re constrained by the Google APIs that currently exist in terms of what we can currently do.
- The topic ‘Not well thought out’ is closed to new replies.
