Makes sense, right? Cross-domain tracking for third party shopping carts So, shopping behavior beginning with one domain will carry over to the next domain in Google Analytics. To put it more simply, if we link these domains in Googe Analytics, a user session that starts with a search visit landing on will continue as the visitor lands on the Google Merchandise Store. This way, the original traffic source would get credit for the sale, not the referral between Google properties.
It might be better to track the referring domains in the same analytics property as the Merchandise store. If these sites are primarily referring to themselves (i.e., self-referrals), they can give you an inaccurate picture in your analytics reports. The GMS's highest converting traffic is coming from. We can use the Google Merchandise Store (GMS) analytics account as an example.Īs you can see from the example below, the GMS is getting a lot of referral traffic from sites that Google owns. Let's think about this regarding e-commerce. Cross-domain tracking scenariosīut what if you need to track user behavior across more than one domain? When a user leaves a domain, their session ends. User behavior that occurs on a domain is tracked in Google Analytics using sessions. One domain = 1 Google Analytics property. So, using standard Google Analytics tracking: The default Google Analytics tracking is setup to treat each domain as a property. Most websites, businesses, and blogs only need to track one domain at a time. To unravel the mystery that is cross-domain tracking, we need to start with how standard web tracking works. Why would you need to use cross-domain tracking? * Note: I have no idea if others have mentioned the Spice Girls before in a web analytics article.
We are going to become the first web analytics article to include a reference to the Spice Girls*! If that doesn't make this post worth reading in of itself, I'm not sure what does? That's right we're making history on Jeffalytics. We've included both an Austin Powers and a Spice Girls meme in this post. Quick Navigationįor those of you who were about hit the back button because you heard advanced and Google Analytics. And I'll outline some steps that can make installing this tracking solution easier.
#Master of my domain gif how to#
We'll show you how to use Google Tag Manager to help you set up cross-domain tracking. In the post and video below, we'll take a look at when you need to use cross-domain tracking. Not only that, but I'll give you a set of steps that you can follow to help solve any cross-domain tracking issues that you are experiencing. With that out of the way, I'm going to do my best to explain this advanced concept in Google Analytics. But it's going to take some work on your end. Chances are, the information within will help you solve your cross-domain tracking problems. This is a 2,000+ word article that explores cross-domain tracking from several angles. Now before you get too far into this article, I want to warn you that there's no way I can promise to “quickly solve your cross-domain tracking issues.” There is no simple cross-domain tracking solution The truth is that most Google Analytics users are tracking just one domain name at a time.īut for those who want to track multiple domains in a single property? It takes a lot of problem solving and debugging to make this tracking solution work effectively. It's also not necessary for everyone who operates a website. Now, cross-domain tracking is a pretty advanced concept that is not easily understood. In this post, we're going to delve deep into a topic that keeps analytics consultants in business – Cross-domain tracking.Ĭross-domain tracking is a term we use to describe the act of tracking multiple domains in a single Google Analytics property.
0 kommentar(er)
