Analytics
3.1K members online now
3.1K members online now
Dive into multiple domain (Cross/Sub) tracking, implementing Ecommerce and Enhanced Ecommerce, setting up Event tracking, and Universal Analytics code.
 
Guide Me
star_border
Reply

"New session because the campaign changed", while it hasn't!

[ Edited ]
Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

Dear collegues,

 

I'm currently stuck with this issue: I'm having a third level domain (let's call it third.site.com) that sends traffic to a second level (i.e. site.com). Both are tagged with the default UA tracking code, same ID.

 

Everything should be handled automatically, but I'm seeing self-referrals instead (while they shouldn't show up).

 

The cookie is the same and GA Debug reassures me: it's correctly set up at the second level domain.

 

Anyway, Google Tag Assistant record feature says:

This hit starts a new session, most likely because the campaign changed.

 

But it's not changed at all.

 

The link from third.site.com to site.com it's a normal <a href="site.com"> HTML tag. There are no utm_ tags or other link decorations.

 

Other things worth mentioning:

  1. it's a target _blank (it shouldn't be a problem by itself)
  2. the content of the <a> tag is a <button> tag (shouln't be a problem either)
  3. the website on site.com it's a bit slow at loading and sending the pageview (but the problem is in the attribution, so it occurs before the pageview)
  4. there's a 301 redirect from site.com to site.com/it

Anyone's got ideas in where to look to solve the issue?

 

Cheers.

 

Update

Problem solved: third.site.com wasn't in the referral exclusion list.

1 Expert replyverified_user
Marked as Best Answer.
Solution
Accepted by topic author Martino M
February 2016

Re: "New session because the campaign changed", while it has

Top Contributor
# 2
Top Contributor
Hi Martino,

> Problem solved: third.site.com wasn't in the referral exclusion list.

Well done. That's the one thing I just wanted to propose ...

Christoph