New answers tagged tracking
You need to fire an event (or a fake pageview using trackPageview) after the form has been validated, ie when the content dynamically changes. Do not add this code on submitting the form alone, as that will count any clicks that fail your validation.
There are two ways to do this - Using Events in Google Analytics, and then configuring the Goal on that Event being fired. In the form URL, add a specific URL parameter which you are sure does not do anything (yes, you read that right). Typical flow would be ... user lands on landing page, submits form, ends up on the same page (except with an additional ...
The simplest way to do this is to fire an event when the form is submitted. Then in analytics configure a goal based on the triggering of the event. (Event based goals is just another type of goal.)
Unfortunately, it seems as though different browsers will act differently. Firefox: Will send the header X-moz: prefetch whenever a page is "pre-fetched." Chrome: You're out of luck, simply because it forces you to use the Page Visibility API, which is JS-based. The term "pre-rendering" applies exclusively to Chrome, as Google seem to be doing their own ...
Developer Evangelist at Marketo here. I can confirm that it's not the Marketo Munchkin tracking code that is loading New Relic.
The b. bit is for if you have multiple trackers on the site. The "b" is just to identify it as different from any other tracker, but that could be any text at all. For example: _gaq.push(["hello._setAccount", "UA-XXXXX-X-2"]); _gaq.push(["hello._setDomainName", "none"]); _gaq.push(["hello._setAllowLinker", true]); _gaq.push(["hello._trackPageview"]); ...
You should not include UTM codes for outbound links. Stephen already pointed out the main issue in that you don't know how they tag their campaigns and therefore without working directly with them it's impossible to provide them good tags (even if you can guess how they're doing it now they may change it). Also you don't have to include UTM codes for them ...
I can think of several reasons why I might be unhappy to have the links to my website from yours include utm parameters that you have chosen for me: You don't know how I set up my other campaigns. Your choices for campaign name and source are unlikely to match what I use in other places. It will add noise to my Google Analytics campaign report I would ...
The simplest solution for cross-site tracking is to set session information for both domains when the user visits either site. This is normally accomplished with a tracking pixel, which is loaded in the first site as an external resource from the second. The tracking pixel is often a 1 X 1 transparent GIF image generated by a server-side script which ...
Top 50 recent answers are included