Have a question about CiviCRM? Get it answered quickly at the new CiviCRM Stack Exchange Q+A siteThis forum was archived on 25 November 2017. Learn more.How to get involved.What to do if you think you've found a bug.
My Interpretation- Using UTM tags to determine the source of the visitor (link shared on social media, newsletter ,etc.)In order to track we only need the Google Analytics generated tracking ID (UA-xxxxxxxx-x) For example, when we are creating a new event using CiviEvent we could ask the user to manually input the tracking ID. Now we can simple add the "tracking script" to the page CiviEvent currently generates. Appropriate UTM tags can be appended to the urls which CiviCRM currently generates.
Google provides an API called the "Embed API" this can be used to display Google Analytics Reports from CiviCRM itself.To get the data from Google Analytics we can use the "Core Reporting API (v3)". We can then store and process this data locally in whatever way we want. We can make queries to this API multiple times to obtain information about how many users registered out of the total number of users who visited the page (conversion ratio).
My Interpretation: Allow for A/B testing (as is done for emails in CiviCRM) for web pagesUsing the same example of CiviEvent, when creating an event we could ask the user to input separate tacking ids to different versions of the web page (say a fixed number 3). Now the user could manually activate a particular version for a fixed time (say 3 days) and use the Embed API to see the performance of each. Now he could simply destroy the other versions (space efficiency) and publish the one with the best response.
Regarding you comment on UTM tags. I understand that UTM tags are used for adding campaign parameters. Say for eg. when an user clicks on the share on Facebook icon on an Event page, CiviCRM generates a URL:http://wp45.demo.civicrm.org/event-page/?page=CiviCRM&q=civicrm/event/info&id=1&reset=1For us to trace the source of the visitor we only need to append the UTM tags to this generated URL. For the example for URL above:&utm_source=facebook&utm_medium=share&utm_campaign=fundRaiserEvent
Thanks for pointing out about A/B frameworks splitting traffic rather than time based tests. After referring to the link on Google Experiments you suggested and reading up on A/B testing, I found that Google Analytics actually allows you to do A/B testing. Well not A/B testing exactly but it allows you to run the "multi-armmed bandit experiment" (almost equivalent).This link is a step by step tutorial to set up one: http://www.newmediacampaigns.com/blog/google-analytics-ab-split-test-tutorial
They are js libraries that allow A/B testing, would be great if you could check some and see how it could fit.
Last suggestion for integration with google analytics: instead of relying on civi to track the click and open, use GA to track who open (google analytics can generate 1x1 transparent pixels, aka webbug) or who clicks (using the utm tags), with the api, you can get the result back into civimail.