Welcome to the Q&A Forum

Update: I checked the rel=next/prev tags in Screaming Frog and they are not implemented correctly. The homepage is identified in all rel=next/prev tags. Not good.

I'm thinking I'll scrap my rel=next/prev efforts and try a view all option with a canonical tag.

It does not appear to be working from the pagination testing tool. I get a "previous and next URL does not link back" message.

I do believe the problem involves these links being dynamically created, possibly with Javascript. The reason I think this is causing the problem is because when I view the code in Chrome via "View Page Source" the links are empty (href=""); however, when I view the code in the inspector (Developer Tools) the links appear and are correct.

Can I validate link next and prev markup for paginated content?

I'm not familiar with "linkers". How do I make sure GA is using linkers? Thanks.

Using custom dimensions our site tracks logged-in vs not logged-in users on our shop site (shop.example.com). A user can only login on the shop.example.com.

The problem is when the logged in user visits our the main domain (example.com), we lose the custom dimension and the user becomes anonymous. At this point, if the user goes back to shop.example.com, the logged-in custom dimension comes back.

How do I preserve the logged-in user dimension across the main domain?

Example of snippet:

Using the same GA property, I would like to set up three filtered views:

1. Tracking across one subdomain and one primary domain (example: shop.example.com & example.com)

2. Track only primary domain (example.com)

3. Track only subdomain (shop.example.com)

Can this be achieved by using view filters? If so, how do they need to be set?

Also, according to this article: https://moz.com/blog/cross-domain-subdomain-tracking-in-google-analytics, with cross domain tracking, I need to ignore self-referrals, which can only be done at the property level. If set up to ignore example.com referrals, will this cause problems with filter 2 and 3?

I was using Universal Google Analytics, but looking at an old example, so thanks for the heads up on that.

What would this global variable look like?

Would this be something I could detect using developer tools?

How would I ask my developer for this piece of information?

What about ignoring self-referrals, prepend hostname to request URIs, and Ga.js / doubleclick.js only: set domain name?

Do I need to do any of that?

https://moz.com/blog/cross-domain-subdomain-tracking-in-google-analytics

I found an example of the snippet to use:

__gaq.push(['.setCustomVar,
1, // first slot
'user-type', // custom variable name
'visitor', // custom variable value
2 // custom variable scope - session-level
]);

Once the visitor logs into your website, we change this code, accordingly:

__gaq.push(['.setCustomVar,
1, // first slot
'user-type', // custom variable name
'regular-user', // custom variable value
2 // custom variable scope - session-level
]);

How does the code know to change from 'visitor' to 'regular user' once a user logs in?

Is the snippet only placed on the login page?

Our website consists of a primary domain (marketing focused) and subdomain (ecommerce platform). The two sites look and function as one site even though they are using different technology.

I would like to track the primary domain (example.com) and the subdomain (shop.example.com) as a single site in Google Analytics. The subdomain will be set up with GA ecommerce tracking as well.

Can someone provide an example of the GA snippet that each would need?

Update: I checked the rel=next/prev tags in Screaming Frog and they are not implemented correctly. The homepage is identified in all rel=next/prev tags. Not good.

I'm thinking I'll scrap my rel=next/prev efforts and try a view all option with a canonical tag.