Ati-ati tina Ngunggah Sababaraha Skrip Google Analytics

ga

Kalayan seueur integrasi alat pikeun seueur sistem manajemen eusi, urang ningali seueur langkung seueur klien kami anu gaduh masalah sareng skrip Google Analytics dilebetkeun kana halaman sababaraha kali. Ieu bakal ngarusak anjeun analytics, hasilna ageung teuing ngalaporkeun pangunjung, halaman per kunjungan sareng ampir teu aya tingkat bouncing.

Ngan dinten ieu urang gaduh klién anu ngagaduhan 2 plugins anu dimuat sareng ngonpigurasi pikeun nambihan skrip Google Analytics kana blogna. Sareng plugin sanés leres-leres mariksa naha parantos aya skrip anu dimuat! Hasilna nyaéta kunjungan éta dilaporkeun-dilaporkeun sareng tingkat mumbulna sakitar 3%. Upami tingkat bouncing anjeun turun ka handapeun 5%, yakin anjeun ngagaduhan masalah sareng sababaraha skrip dina halaman anjeun.
laju mumbul

Kumisan ti Analytics, kumaha anjeun tiasa terang upami anjeun parantos ngalakukeun ieu? Hiji metodeu ngan saukur pikeun ningali sumber halaman anjeun sareng milarian ga.js. Komo upami anjeun hoyong ngawas situsna sababaraha akun Google Analytics, kedahna ngan ukur hiji skrip.

Cara sanésna nyaéta muka alat pamekar anjeun dina panyungsi anjeun sareng ningali komunikasi jaringan saatos anjeun nyegerkeun halaman. Naha anjeun ningali skrip ga.js dipénta langkung ti sakali?
ga js

Google Analytics tiasa dianggo ku ngamuat skrip anu ngempelkeun sadaya inpormasi, nyimpen inpormasi ka cookies browser sareng ngirim kana sérver Google ngalangkungan pamundut gambar. Nalika skrip dimuat langkung ti sakali, éta sakapeung nimpa cookies, sareng ngirim sababaraha pamundut gambar ka sérver. Kusabab kitu teh laju mumbul handap pisan ... upami anjeun nganjang ka langkung ti hiji halaman dina situs, anjeun moal mumbul. Janten… upami skrip na némbakan langkung ti sakali nalika anjeun nganjang ka hiji halaman, hartosna anjeun parantos nganjang sababaraha halaman.

Pariksa halaman anjeun sareng anjeun analytics pikeun mastikeun Anjeun analytics skrip dipasang leres dina situs anjeun, sareng pastikeun anjeun henteu ngahaja ngamuat skrip langkung ti sakali. Upami anjeun ngalakukeun, data anjeun henteu akurat.

2 Komentar

  1. 1

    Thanks, I’ll take note on this. I think this is the reason why my ecommerce site doesn’t have really traffic going on its analytics report. the google script is different from the tracking code present on its google analytics report. thanks mate.

  2. 2

    Hi Douglas, great insight. I had a similar drop since I started some experiments on Google Tag Manager few weeks ago: 4 Page/ Visits 🙂 and bounce back of currently at 0.47% 😀

    Following your post, here my result:

    1.Scripts: There is 1 ga.js (I pasted only the code of Analytics and Tag Manager into my site). I cannot see in the second script (Tag Manager) any reference to ga.js but only gtm.js . I have no big code just those 2 pasted together (first analytic, then T.M.), so I don’t even need to use an application, however I checked with firebug too.

    2. In the Tag manager Console I created just one event (same time of creation, same time of start b.r. dropping). This event basically works as Link click listener for Outbound Links and it is the same as the one advised by James Cutroni into his blog. But I made a slight modification: One is the Non-Interaction Hit set to True (that shouldn’t be hit bounce rate?) but then I added a Label=referrer instead of leaving it blank, because I wanted to know there the clicks where from. (Anyway I removed it today as It is not so useful as I thought)
    3. I still have some few outbound links with old onClick=”_gaq.push()” embedded but all of them have been set the Non-interaction click to True.

    Hatur nuhun,

    Donald

Naon anu anjeun pikirkeun?

Situs migunakeun Akismet pikeun ngurangan spam. Diajar kumaha komentar data anjeun diolah.