The Official Google Website Optimizer Blog - The most up-to-date product news, industry insights, and testing strategies

New Year, New Asynchronous Tags for GWO

Wednesday, January 05, 2011 1/05/2011 12:27:00 PM

12 comments:

Brighter Blooms Nursery said...

Since the new code went live, i have been unable to start any tests. The preview does not show the changes on the different variations. could you look into this?

Trevor Claiborne said...

We're looking into the issue you're seeing. Would you mind sharing the website you're seeing the problem on?

Wear said...

How does asynchronous tagging improve data accuracy? Does it mean the previous data is not so accurate?

Anonymous said...

This is awesome but a few tweaks please:
- Fix the "&lthead" (add semi-colon).
- Provide a link to the "setup wizard" that contains Step 2 so I can see the new snippet.

Thanks.

Trevor Claiborne said...

@Wear,
Since the code executes faster, it prevents any tracking issues that occur when the code is not fully loaded prior to action. These tend to be edge cases. One scenario where this might happen is if you are tracking a click on a link as a conversion. If the conversion script hasn't fully loaded before the user clicks the link, then the conversion won't be recorded. We're talking on the order of milliseconds here, but with asynchronous tags these issues becomes even more rare.

@anonymous
Thanks, the head tag rendered fine in Chrome and Firefox, but I had not checked Safari, fixed.

There's not a way to link to a generic Step 2 since links are experiment specific, but you can see the new script throughout the Help Center. For example: http://www.google.com/support/websiteoptimizer/bin/answer.py?hl=en&answer=117912 (linked in the post) has the new Tracking and Conversion Scripts. Note that the lines in bold are additions made for that particular customization.

Sarah said...

How can I validate the "old" conversion script? When I use the validate in step 2, I get errors since the "old" conversion script is on the page and not the "new" conversion script.

Thanks!

Trevor Claiborne said...

@Brighter Blooms
The page you're running an experiment on currently has Website Optimizer code for two different experiments. That's the issue you're seeing. The async tags are working normally.

Trevor Claiborne said...

@Sarah

I just tested a page with the old experiment tags and it validated without any problems. I'm guessing there's something wrong with how the tags are installed on your page that's causing validation to fail.

Sarah said...

@Trevor -

Okay, I found the issue.

The issue is with the value in the gwoTracker tag.

The validation is looking for the number to in in "-2" but on the page the value ends in "-1". The 7 digit number after the UA- is the same in both places, it is just that last digit.

Is this truly an issue? Or can I run the test with this single digit being different?

validation: var gwoTracker=_gat._getTracker("UA-xxxxxxx-2");

my page: var gwoTracker=_gat._getTracker("UA-xxxxxxx-1");

Thanks so much for the help -
Sarah

Trevor Claiborne said...

Hi Sarah,

If the UA number on your page doesn't match the UA number that Website Optimizer provides then you won't get data. This includes final -X part. I'm not sure how you ended up with a different UA number. The move to async should not have had any effect on that.

Sarah said...

Trevor -

Thank you so very much for the quick and understandable responses - I really appreciate it!

Is there a survey I can fill out saying how helpful you were so your boss can know?

Thanks again -
Sarah

Trevor Claiborne said...

Hopefully he reads the blog ;-)

Post a Comment

You are welcome to comment here, but your remarks should be relevant to the conversation. We reserve the right to remove off-topic comments, or self-promoting URLs, and vacuous messages. Please keep your comments relevant, friendly, and respectful.

We moderate all comments so you may not see your comment show right away.