analytics

So normally I would use the s.getQueryParam(); to parse out my URLs for query strings that I've been using. s.eVar8=s.getQueryParam('cid,pid,eid',':'); s.prop28=s.getQueryParam('Role'); But since DTM has that all built into it, how would you really define that? I know I can set a page load rule using the campaign variable, but what if I have multiple parameters separated by ":" www.domain.com?cid=blah1:blah2:blah3&pid=blah4:blah5:blah6&eid=blah7:blah8:blah9 Is there something that I'm missing when using this approach? Should I be capture these values into a data element then passing the data

How would I go about this, I have files which I have sorted the information in, I want to compare a certain index in that file with an index in another, one problem is that the files are enormously large, millions of lines. I want to compare line by line the files I have, if they match I want to input both those values along with other values using an index method. ======================= Let me clarify, I want to take say line[x] the x will remain the same as it is formatted uniformly, I want to run line[x] against line[y] in another file, I want to do this to the whole file and output every

I am building web analytics tools which deal with tracking the click events and mouse movements , For this, I don't want to send the data to the server for every mouse move or click , instead I planned to save locally and send the data to the server at session time out or while closing the browser or tab (closing the web site). Note: Large amount of data is to be stored locally. I know some possible ways to store the data locally. 1.LocalStorage: Drawbacks: Domain Specific so i can't rely on this. 2.Cookie Drawbacks: 1.Analytics fails if cookie is disabled 2.Not possible to store large amount

I'm trying to fetch some data using the analytics API, the example i have is this: function getResults(&$analytics, $profileId) { // Calls the Core Reporting API and queries for the number of sessions // for the last seven days. return $analytics->data_ga->get( 'ga:' . $profileId, '7daysAgo', 'today', 'ga:sessions'); } and the function in the Analytics.php file is: public function get($ids, $metrics, $optParams = array()) { $params = array('ids' => $ids, 'metrics' => $metrics); $params = array_merge($params, $optParams); return $this->call('get', array($params), "Google_Service_Analytics

Universal Analytics在2014年4月初完成了公测，抛掉了beta版的帽子，官方也提供了从Google Analytics升级为Universal Analytics的通道。在UA Bata公测一年多的时间中，我设置了传统GA与UA两套跟踪方式并用，在正式版发布以后也把原来的传统GA的网络媒体资源也升级为了UA。目前传统的Google Analytics仍然是可以使用，Google官方说原来的GA在未来非常长的时间内还是可用的，但停用GA全面转向UA是必然的，在停用GA之前也会在后台界面上显示停用和升级的提醒。如果你还没准备好升级你的GA，那目前继续用着也没有任何问题。但如果你要使用UA新增的一些高大上的功能比如自定义维度和自定论指标、跨平台跟踪、在线/在线数据同步、简化的配置控制功能等等，这时你需要把你的GA升级为UA。 为了减小升级的风险和简化升级的步骤，这里有几点建议： 1. 如果担心升级为UA后数据丢失，可以新建一个UA媒体资源与原来的媒体资源并行运作，检查两个媒体资源的数据是否一致。新建的媒体资源的跟踪代码配置也应和原来的媒体资源的跟踪代码配置一致。 2. 建议使用Google Tag Manager进行新建UA媒体资源的配置。这样可在大大简化代码配置的工作。并在GTM中设置一个媒体资源ID的宏