This commonly happens when you add a secondary dimension to a standard report or if you apply a segment to a report. Sampling occurs in Google Analytics when there are more than 500,000 sessions (at the Property level) for the date range selected, and you try to pull a “non-standard” report. For help deciding on whether you need cross-domain tracking, follow this easy flow-chart. That’s not all unfortunately, you’ll also have to make sure you follow the steps to make sure cross-domain tracking is set up correctly. That way, if a user starts on one site, then goes to the other site, you will count that as 1 user with 1 session in Google Analytics (as opposed to 2 users and 2 sessions without cross-domain tracking).įor cross-domain tracking to even be an option, both sites need to be in the same Property – which means they both have the same UA tracking id on them. make a purchase, fill out a form, etc.)? If so, you will most likely want to implement cross-domain tracking. Do you expect users to cross back and forth between the two sites? Or will they start on one site, but go to the other to do something important (i.e. This coincides with the reporting requirements, but is important enough to warrant its own section. Think about this new site, and how it relates to your existing site. But why put yourself through that trouble? Cross-Domain Tracking Requirements
Sure, you could use tools like Data Studio, Tableau, or even Excel to combine data from both Properties into one place and calculate the totals. Consider the alternative – if you create a new Property, trying to report on total users, sessions, pageviews, etc. To help you decide which option is right for you, consider the following:ĭo you need to be able to easily report on total numbers for both sites in one single report? If so, then you should track it the same Property. Property – Help Me Decide!Īlthough Google’s help center articles and developer documentation generally advise you to create a new Property for each website or app that you’re tracking, the best solution is usually more nuanced and dependent on the particular organization’s reporting requirements, along with several other factors. And that’s what brought you here – welcome! View vs. So you do what any good web analyst does: you start Googling. If you track it in the same Property, then you could create a new View in that Property to report on this new site by itself.
#Adwords editor restriction code#
use the same tracking code on both sites)? Should you create a new Property (with its own unique tracking code)? Or should you track this new site in the same Property that is already set up (i.e. As a good web analyst, you jump into Google Analytics and start to set things up, but then you’re struck with uncertainty. Now, your boss comes to you and says the company is creating a new site, and you need to track it. Within that Property you have several Views (your main reporting View, and maybe a few others that filter the data in various ways).
You have one Google Analytics Account, and in that Account you have a single Property. Does this sound familiar? Your company has a website, and you are tracking that in Google Analytics.
0 kommentar(er)
