I have a site that has cross-domain tracking and recently added new AMP functionality.
I wanted to ask you if next tracker creation is wrong?
ga('create', 'XX-XXXXXXXX-1', 'auto', {'allowLinker': true});
ga('create', 'XX-XXXXXXXX-1', 'auto', {'useAmpClientId': true});
or I should use something like:
ga('create', 'XX-XXXXXXXX-1', 'auto', {'allowLinker': true, 'useAmpClientId': true});
Thanks
The create method
The analytics.js library provides a variety ways to create trackers,
but the most common way is to use the create command and pass the
tracking ID and cookie domain fields as the second and third
parameters:
ga('create', 'UA-XXXXX-Y', 'auto');
Naming trackers
You may also, optionally, name the tracker by passing the name field
as the fourth argument in the create command. Naming a tracker is
necessary in cases where you need to create more than one tracker for
the same page. For more details on why you might need to do this, see
the section below on working with multiple trackers.
ga('create', 'UA-XXXXX-Y', 'auto', 'myTracker');
Creating a tracker without setting the name field is known as creating
a "default" tracker. A default tracker is internally given the name
"t0".
The second way is the rightway i.e.
ga('create', 'XX-XXXXXXXX-1', 'auto', {'allowLinker': true, 'useAmpClientId': true});
and for setup verification refer below link
https://support.google.com/analytics/answer/7486764
Related
currently want to track unique users in GA (remember their session, etc). Having the problem of where to place the userId code inside the tracking code?
Is it correct to place it in between create and send? or does it matter? will it have a negative effect if I place it before create or after send?
ga('create', 'UA-XXXXX-Y', 'auto');
ga('send', 'pageview');
Beginner level with GA.
You can put it in the create command via the optional fieldsObject, or you can set it on the tracker after it's created (but before the pageview is sent).
You cannot put it before the create command, and if you put it after the pageview is sent, it'll be too late and won't apply to that hit.
In other words, either of these two variations will work:
ga('create', 'UA-XXXXX-Y', 'auto', {userId: USER_ID});
ga('send', 'pageview');
or:
ga('create', 'UA-XXXXX-Y', 'auto');
ga('set', 'userId', USER_ID);
ga('send', 'pageview');
We tried to implement auto link cross domain but it doesn't seems to work. Here is the case:
We have 2 different domains:
source.com
destination.com
When user visits source.com and click on Submit button, he is automatically redirected to the destination.com (the redirection is on the server side and not the client).
We want to have the ability to track the user action on both domains and treat it as the same user.
We have the following code on the source.com domain:
ga('create', 'UA-XXXXXX-X', 'auto', {'allowLinker': true});
ga('create', 'UA-XXXXXX-X', {'name': 'newTracker'});
ga('newTracker.send', 'pageview');
ga('send', 'pageview');
ga('require', 'linker');
ga('linker:autoLink', ['destination.com'], true, true);
And this code on the destination.com domain:
ga('create', 'UA-XXXXXX-X', 'auto', {
'allowLinker': true
});
ga('send', 'pageview');
This code is not working. we tried to use the same UA id for both but the client id seems to change between the domains and therefore I move from source.com to destination.com I see in analytics 2 different users.
We also tried to pass ourselves the _ga parameter but it also doesn't seems to work
Can anyone please advice? We can't understand what we are doing wrong.
It can be great if you can show an example code and not just reference (:
I am just looking for some help setting up a single view of all the sites we have. I can find lots of help for the old analytics tracking code but not for the new universal analytics.
I've got 5 sites each with their own tracking code in place but i'd like to create a roll up account that allows me to look at an overview of all the sites in a single view. Just wondering what i need to add to the code to do this?
It's currently;
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-XXXX', 'auto');
ga('require', 'linkid', 'linkid.js');
ga('require', 'displayfeatures');
ga('send', 'pageview');
</script>
And I would just like to know what i need to add in to be able to include the numbers in a roll up account too? I think it's possible to simply edit this code with the UA of the roll up account but I'm not sure of the correct way to format this.
Any help would be appreciated,
Thanks
Roxi
It works rather like it did with asynchronous analytics, only you pass the name of the tracker in the (optional) configuration object:
ga('create', 'UA-XXXXX-X', {
'name': 'firstTracker',
});
ga('create', 'UA-XXXXX-Y', {
'name': 'secondTracker',
});
ga('firstTracker.send', 'pageview');
ga('secondTracker.send', 'pageview');
Any other options (e.g cookie domain, which is the third parameter if you don't use a configuration object) are set as key-value pairs in the configuration object. You find this in the documentation under Advanced Configuration.
I create a google analytics tracking object like this:
ga('create', 'UA-10303525-4', 'auto'); // Replace with your property ID.
ga('send', 'pageview');
Later on, without loading the page, I want to update the tracking object with a userID:
ga('create', 'UA-10303525-4', { 'userId': response.data });
This doesn't seem to work. Is it possible to update or destroy/recreate the tracking object somehow?
You might try the set method.
We have a site that has the same content but available under two domains. Is this is the right code to put on each page to split the domains in google analytics so we can see view the activity under each domain?
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-1234-1' {'cookieDomain': 'domain1.com.au'});
ga('create', 'UA-1234-2' {'cookieDomain': 'domain2.co.nz'});
ga('send', 'pageview');
</script>
Thanks
According to https://developers.google.com/analytics/devguides/collection/analyticsjs/advanced (part Working with Multiple Tracking Objects) you should create a named tracker for the second property, like:
ga('create', 'UA-XXXX-Y', {'cookieDomain': 'domain1.com'});
ga('create', 'UA-12345-6', {'name': 'newTracker', 'cookieDomain': 'domain2.com'}); // New tracker.
and then send the page view for each tracker:
ga('send', 'pageview'); // Send page view for default tracker UA-XXXX-Y
ga('newTracker.send', 'pageview'); // Send page view for new tracker.
There's also other way how to track the same website with 2 domains by using just one property (UA-1234-1) and creating 2 views with each will include traffic only from given domain names (use predefined filter "Exclude/Include only traffic from the domains")
UPDATE
Thinking again about my answer, I must admit that even the original solution in answer
ga('create', 'UA-1234-1' {'cookieDomain': 'domain1.com.au'});
ga('create', 'UA-1234-2' {'cookieDomain': 'domain2.co.nz'});
will work, because if you try to create tracker 'UA-1234-1' on domain domain2.co.nz cookie will not be set (and vice versa creating 'UA-1234-2' on domain domain1.com.au). My solution is technically OK, but then you must take care about sending all pageviews, event trackings and other informations twice - for default tracker and also for named tracker.
Sorry if this is little confusing.