Welcome to the Q&A Forum

David,

No it would not, UNLESS the user doesn't click on any more links on the homepage. Really, a bounce is calculated based on whether or not there was more than one pageview of a site in a single session, not whether or not the user left. GA (without doing some custom work) doesn't even know the user has clicked on an external link.

Edit: My apologies. I misread your question. I thought you were saying that the banner click was a click off to another site. Still, the answer stands.

As long as the GA snippet exists on the 2nd page, it will trigger a pageview and look like the 2nd pageview in the session, meaning it's not a bounce.

I wouldn't expect UA to be the catalyst for having this behavior changed in the future (based on what I know about how Google separates data amongst property/profile - those concepts aren't changing in UA).

This isn't possible, and I've heard no whispers of it being in the works.

No. Provided you have the code on every page and it's properly firing, the disparity should not be very high at all.

Perhaps you have filters in your GA profile that are blocking traffic? Like, say, an internal office IP filter?

Another thing to consider:

• If the user clicks 2 links in the email, that will register with Silver Pop as 2 clicks, but in GA as just 1 visit (as long as the clicks took place within 30 minutes).

I'm not sure what your email template looks like, but if it's a design that lends itself to multiple clicks, this could account for the disparity?

I would be a little wary of combining hit-level dimensions (page) with session-level metrics (conversion rate). A better option would be to look at a hit-level metric like Page Value. More info here in this great post by Avinash:

http://www.kaushik.net/avinash/hits-sessions-metrics-dimensions-web-analytics/

Yeah, I'm about 99% certain that this is not possible. Filters are essentially evaluated at the hit-level. There's no way to exclude a full session according to one hit characteristic.

Usually the question is asked the other way around (multiple AdWords one GA), so I had to do some research. Seems to me that this may not actually be possible.

Diego,

It's rather simplistic, really. GA will look at all conversions that had the direct channel within the user's conversion path. For any that has at least one occurrence of 'direct', it will apply the full value of that conversion to the tally of "assisted conversion value". It will only apply that full value once, say, if direct appears 10 times within that single conversions path.

direct -> organic - > direct -> ppc leading to sale of $100 product

would give direct $100 of credit in assist.

To add another reason that this is possible:

GA Goals only count once per session. So in the event that someone purchases twice in one session, that goal will only have registered once.

Rich,

Because responsive design inherently only uses one html file, what you're describing isn't so simple. Obviously, you only want to include 1 GA tracking code, but you COULD include some logic that fires a different one on page load depending on detected screen width. I think your best bet is to just use the standard GA code in your HTML, then include some JS that detects which of the layouts are displayed on load, and sends it in a custom variable. Alternatively, GA, by default, will capture screen size as a data point, so, as long as your responsiveness is working properly, you can just create segments in GA based on those and view site behavior accordingly.

Mike

Completely inaccurate.

The Google search ranking algorithm is completely separate from that of Google Analytics. The search algorithm's definition of a bounce is based on when a user comes back to the SERPs after visiting your page. That metric wouldn't change no matter what you do to your Google Analytics (unless you somehow muck up the GA snippet so much that it causes page load delays and actually affects user behavior).

Jim,

There is a call within the Google Analytics eCommerce tracking snippet specifically for this.

See: http://code.google.com/apis/analytics/docs/tracking/gaTrackingEcommerce.html

Within the _addItem call you see this line:

'Green Medium',  // category or variation

Most people leave this blank as it is not required, but it can be great for categorizing your transactions. Once you start passing data there, you'll see your "Product Category" reports start to fill up in eCommerce reports.

Mike

Leslie,

Indeed KTaylor is on to something. There is no 301 redirect, but instead there is a JavaScript redirect in place. Using Firefox with JavaScript disabled the site does not redirect.

The GA snippet is likely firing in some cases before the redirect happens.

1. Yes. Use individual profiles. Not web properties.

2. I would suggest using just one profile #. As you said you want to have a raw data, the main site, and the mobile profile. It's easy enough to use the same UA number for all three, then filter into 3 separate profiles.

3. No. In fact, you're actually not making any changes on Google's end by making that switch in the admin. That's really just a tool that generates a different code for you. It's all front-end. As long as you implement properly, you shouldn't lose any data to your main profile. Any new profiles that you create will, of course, start from scratch.

4. Yes and no. I'll explain below.

5. This isn't ideal, but isn't overly concerning. First of all, there is ZERO benefit to splitting the code. The async code does not block other code from loading, meaning it will have no effect on page load speed. By moving the whole code up into the head, you're just ensuring that the best, most honest data is being captured. Still, splitting the code is a common practice that yields fine results.

So, as I mentioned in answer three, I think you first have to understand that it's not a 'switch' in GA's admin that makes the change from single to multiple-domain. The only thing that actually changes in the admin is the way the snippet is written. And I'll tell you that the only thing that will change is that the _setDomain line will be added. So if you properly add this new line into your GA code, you'll be set up to capture all data into your raw profile. From there you can create your two separate profiles using the same UA code, with a custom filter based on the hostname.

Mike

Actually, Google will shorten the displayed URL to just the domain, regardless.

When the user hovers over the URL they can see the tracking parameters, and when they ultimately land on the page, the URL bar will include your tracking parameters.

Without adjusting something on either site it wouldn't be possible, but it IS totally doable if you can edit the sites.

The way I'd approach it is by adding a query string or identifier to the referring URL.

So on site A, instead of just linking to siteb.com/landing-page, link to siteb.com/landing-page?ref=newsletter.

That page should appear in your content reports. Then you can set it as a goal.

Would that work?

Yeah, I'm about 99% certain that this is not possible. Filters are essentially evaluated at the hit-level. There's no way to exclude a full session according to one hit characteristic.

I would be a little wary of combining hit-level dimensions (page) with session-level metrics (conversion rate). A better option would be to look at a hit-level metric like Page Value. More info here in this great post by Avinash:

http://www.kaushik.net/avinash/hits-sessions-metrics-dimensions-web-analytics/

From what I understand, the # doesn't ever get sent to the server, so it would be impossible to include it in a rewrite rule.

Awesome use of the new Q&A Rand!

One of my biggest content sites actually has seen an increase in traffic since the "farmer" update. The content on it is definitely a tick above content farmed crap, but it's also not 5-star.

For what it's worth, it's monetized with AdSense ads and there's really no branded traffic to speak of naturally.

fgqqY.png