What you have looks right to me.

Both _setDomainNames are set to exactly the same string – good.

the fakeTracker._setVar comes before the pageTracker._trackPageview – good.

Doublecheck your code in the page and make sure you have straight quotes and not directional quotes. Load the page in question, and make sure you do not have any JavaScript errors.

Go into your Google Analytics to the Top Content report and look for the URL of that page, and make sure it shows up for a time period after you made the change.

var gaJsHost = ((“https:” == document.location.protocol) ? “https://ssl.” : “http://www.”);
document.write(unescape(“%3Cscript src=’” + gaJsHost + “google-analytics.com/ga.js’ type=’text/javascript’%3E%3C/script%3E”));

var fakeTracker = _gat._getTracker(“UA-1″);
fakeTracker._setDomainName(“.domain.com”);
fakeTracker._setVar(“Payment Method: “);

var pageTracker = _gat._getTracker(“UA-#######-#”);
pageTracker._setDomainName(“.domain.com”);
pageTracker._trackPageview();

Perhaps I didn’t understand your explanation above? I’m thinking that before the setVar is set to the fakeTracker instead of the pageTracker, when the _trackPageview method is called on the pageTracker, it doesn’t read the variables set for the fakeTracker. Any way around this?

I’m not sure what you mean. The call to _trackPageview() should appear on every page that you want to track in GA.

Although there might be cases where you want to use _setVar on a landing page and do not want to track it with _trackPageview(), I’m not coming up with any thing reasonable.

I think the best description of the relationship between “Bounce rate and the _setVar(’…’);” is Pinky and the Brain. They both want to conquer the world, but since they mess up one with the other, things just don’t work…