{"id":257,"date":"2010-11-04T11:54:11","date_gmt":"2010-11-04T09:54:11","guid":{"rendered":"https:\/\/webanalyst.ro\/2010\/subdomenii-asincron-google\/"},"modified":"2013-05-23T09:28:19","modified_gmt":"2013-05-23T06:28:19","slug":"subdomenii-asincron-google","status":"publish","type":"post","link":"https:\/\/webanalyst.ro\/blog\/2010\/subdomenii-asincron-google\/","title":{"rendered":"GAnalytics: Subdomenii multiple cu cod asincron"},"content":{"rendered":"

Despre configurarea Google Analytics pentru statistici de la multiple subdomenii<\/a> am scris deja, dar \u00eentre timp cei de acolo au actualizat codul de tracking cu o versiune care lucreaz\u0103 asincron (cite\u0219te despre codul asincron pt Google Analytics<\/a>). Problema este c\u0103 dup\u0103 trecerea la aceast\u0103 versiune de cod se schimb\u0103 \u0219i toate celelalte configur\u0103ri. A\u0219adar, dac\u0103 a\u021bi r\u0103mas la versiunea veche de cod urma\u021bi pa\u0219ii din primul link, dac\u0103 ave\u021bi cod asincron citi\u021bi \u00een continuare ce trebuie f\u0103cut pentru ca Google Analytics s\u0103 m\u0103soare \u00eempreun\u0103 performan\u021bele subdomeniilor!<\/p>\n

Modificarea de cod<\/h2>\n

Pa\u0219ii sunt aceia\u0219i ca la prima variant\u0103: prima dat\u0103 facem o modificare \u00een codul de analytics introdus \u00een pagini pentru a indica domeniul parinte, dup\u0103 care aplic\u0103m un filtru sau mai multe.<\/p>\n

Codul ar trebui s\u0103 fie de forma:<\/p>\n

<script type=”text\/javascript”>
\nvar _gaq = _gaq || [];
\n_gaq.push([‘_setAccount’, ‘UA-000000-1<\/span>‘]);
\n_gaq.push([‘_setDomainName’, ‘exemplu.ro<\/span>‘]);
\n<\/strong>\u00a0\u00a0\u00a0\u00a0\u00a0 _gaq.push([‘_trackPageview’]);
\n(function() {
\nvar ga = document.createElement(‘script’); ga.type = ‘text\/javascript’; ga.async = true;
\nga.src = (‘https:’ == document.location.protocol ? ‘<\/span>https:\/\/ssl<\/span><\/a>‘ : ‘<\/span>http:\/\/www<\/span><\/a>‘) + ‘.<\/span>google-analytics.com\/ga.js<\/span><\/a>‘;
\nvar s = document.getElementsByTagName(‘script’)[0]; s.parentNode.insertBefore(ga, s);
\n})();
\n<\/script><\/span><\/p><\/blockquote>\n

Practic, linia \u00eengro\u0219at\u0103 este cea care se adaug\u0103 la codul pe care \u00eel ofer\u0103 contul de GA. Am scris cu ro\u0219u lucrurile pe care va trebui s\u0103 le modifica\u021bi (codul contului\/profilului \u0219i domeniul site-ului).<\/p>\n

Filtru pe profil<\/h2>\n

F\u0103r\u0103 ad\u0103ugarea unui filtru pe un profil nou, traficul de la subdomenii va ap\u0103rea ca fiind reffering<\/em> (de la un site extern).<\/p>\n

Set\u0103rile filtrului:<\/p>\n

Filter type: Custom<\/p>\n

Advanced<\/p>\n

Field A -> Extract A\u00a0\u00a0\u00a0\u00a0 Hostname\u00a0\u00a0\u00a0\u00a0 (.*)<\/b><\/p>\n

Field B -> Extract B\u00a0\u00a0 Request URI\u00a0\u00a0\u00a0 (.*)<\/b><\/p>\n

Output To -> Constuctor\u00a0 Request URI\u00a0 \u00a0 <\/b>$A1$B1<\/strong><\/p>\n

Yes<\/p>\n

No<\/p>\n

Yes<\/p>\n

No<\/p><\/blockquote>\n

\"filtru-subdomenii-asincron\"<\/p>\n

Acestea au fost setarile pt a avea statisticile domeniului \u0219i subdomeniilor la un loc.<\/p>\n

OP\u021aIONAL: Se poate merge mai departe, pe l\u00e2ng\u0103 a le avea la un loc, putem s\u0103 cre\u0103m c\u00e2te un profil cu statisticile fiec\u0103rui subdomeniu. Pe fiecare dintre acestea ar trebui aplicat urm\u0103torul filtru:<\/p>\n

Filter type: Custom<\/p>\n

Include<\/p>\n

Filter Field\u00a0 Hostname<\/p>\n

Filter Pattern\u00a0\u00a0 subdomeniu\\.exemplu\\.ro<\/b><\/p>\n

No<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"

Despre configurarea Google Analytics pentru statistici de la multiple subdomenii am scris deja, dar \u00eentre timp cei de acolo au actualizat codul de tracking cu o versiune care lucreaz\u0103 asincron (cite\u0219te despre codul asincron pt Google Analytics). Problema este c\u0103 dup\u0103 trecerea la aceast\u0103 versiune de cod se schimb\u0103 \u0219i toate celelalte configur\u0103ri. A\u0219adar, dac\u0103 […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,12],"tags":[111,175,230],"class_list":["post-257","post","type-post","status-publish","format-standard","hentry","category-google-analytics","category-technical","tag-asincron","tag-filtre","tag-subdomenii"],"_links":{"self":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/257","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/comments?post=257"}],"version-history":[{"count":3,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/257\/revisions"}],"predecessor-version":[{"id":1042,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/posts\/257\/revisions\/1042"}],"wp:attachment":[{"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/media?parent=257"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/categories?post=257"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webanalyst.ro\/blog\/wp-json\/wp\/v2\/tags?post=257"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}