traffic source analysis using javascript, not from URL

[GoogleCodeExporter]

Name of API affected:
Analytics Data Export API

Request summary:
Please implement tracking function to set traffic source like utm_source, 
utm_medium in JavaScript, not parsing those parameters from URL.

Use Cases:
Tracking traffic source is good thing, but URL with those parameters are 
too long and not good for URL canonicalization.
I want to do this:
1. user comes from ad, using URL:
> http://example.com/?page=01&utm_source=ad01

2. I parse URL and if utm_(source|medium|keyword|text) is appended, I put 
those information in user's cookie, and immediately redirect user to URL 
without those traking parameters.
> http://example.com/?page=01
> cookie: prev_url=http://example.com/?page=01
> cookie: prev_utm_source=ad01
> 

3. Each access, I check cookie and if there are prev_utm_* cookie and the 
URL is same as prev_url, I do like: 

var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-******-*']);
_gaq.push(['_utm_source', 'ad01']);  // HERE!!
_gaq.push(['_trackPageview']);

With these, I can canonicalize URLs, users are fine with short URLs.

Original issue reported on code.google.com by hidehisa...@gmail.com on 22 Feb 2010 at 2:06

[GoogleCodeExporter]

This is a feature request for GData apis specifically the Google Analytics Data 
Export 
API.

Feel free to followup on our public forum: 
http://www.google.com/support/forum/p/Google+Analytics/label?
lid=5a6c689030bdafe7&hl=en

Original comment by nickski1...@gmail.com on 11 Mar 2010 at 12:33

• Changed state: Invalid

[GoogleCodeExporter]

Removing an obsolete label that was used when these issues were in the 
gdata-issues project.

Original comment by jrobbins@google.com on 21 Jul 2011 at 10:05

• Removed labels: API-Analytics

[GoogleCodeExporter]

Changing the issue type to match the organization desired in this project.

Original comment by jrobbins@google.com on 21 Jul 2011 at 10:06

• Added labels: Type-Feature