Is it best to use multiple or a single Google Analytics property if you have a website where people pay to log in and you want to view separate analytics for 1) your marketing site (http://www.example.com) and 2) your paid app (http://app.example.com)?
Asked
Active
Viewed 94 times
0
-
1This question appears to be off-topic because it is not a programming question. – Eike Pierstorff May 26 '14 at 12:51
-
1This is not a programming question and hence off-topic. Having said that: it used to be that different kinds of data (like app data and website data) should be separated in properties. However if you want to use cross-device identification using the user_id feature (important if there is cross traffic between app and website) you have to use a single property. – Eike Pierstorff May 26 '14 at 12:51
-
Thanks Eike - that's useful to know. – Andrew May 27 '14 at 13:38
-
I think it's debatable as to whether this is off-topic or not as good Google Analytics implementation can certainly involve some programming. Eg passing in events and ecommerce goals etc. In fact, I would say that too few programmers know enough about Google Analytics. – Andrew May 27 '14 at 13:40
-
1Possibly :-) My thinking was that the solution does not involve any code - this is about configuration and would IMO be a better fit for webmasters.stackexchange.com. – Eike Pierstorff May 27 '14 at 13:43
-
If the answer was 2 properties then it would involve some code - adding the 2 different snippets and keeping separation between marketing site and app. But, you're right, it's very borderline :) I also thought I would get a better answer here than at webmasters.stackexchange.com where they would probably be less likely to mention things like the user_id feature. – Andrew May 27 '14 at 13:48