Measuring downloads about haxe.org HOT 40 CLOSED

@Merelleya: Could you check if that's possible?

from haxe.org.

Hi there,

Out of the box, Google Analytics can only track websites, but not downloads. In order to be able to track a download you will need to make some changes/use a workaround.

Option 1:
Implement a redirection that directs you users to a "thank you for downloading this" site or something of the like. You will then track the site itself and not the actual download in google analytics (e.g. you will track how often this site is triggered).

Some people find it annoying to be redirected, others actually like to get some sort of feedback. It might be a good idea to give feedback or say "Thanks" to your users. Once you have more content you could even link this with some "Need help? Here's a handy Haxe Tutorial" - Hint.

Option 2:
You will Use Page tracking to track how often the download link is clicked.

Google Analytics allows Event Tracking. In order to trigger an Event in the Account you need to add an "onClick" call to the link you want to track (in this case the download link). Here are two useful tutorials for this:

https://developers.google.com/analytics/devguides/collection/analyticsjs/events

http://wordpress.sph.harvard.edu/web-tech/tracking-pdf-downloads-in-google-analytics/

Note, that the method for doing this is different when you have not switched to Universal Analytics:

https://developers.google.com/analytics/devguides/collection/analyticsjs/pages

This will then trigger an Event in you Google Analytics that you can track using the goals you can set up in the admin panel.

I have a few other recommendations:

1. You still need to link the Google Webmaster Account to the Analytics Account. Unfortunately, I can not do that from here, because you have to own the website you are doing this for.
2. Google Analytics will shift from classic Analytics to Universal Analytics this year. Befor setting up any new thing, I recommend you move the Account to Universial Analytics and implement the new tracking code into the website. It will take 24-48 hours for Google to transfer the data to Universial and give you the new code. The move itself can be done by clicking a button in the Admin Panel.
3. If you are interested in more data about you visitors you might consider including the appropriate code to enable google to track double-click-cookies. Google Analytics will then try to extrapolate information about the user (age, interests, gender) based on the ads that that user is already being shown. I am not sure whether this would be useful as it is generally used for remarketing purposes in e-commerce situations.

The neccesary changes are described in the Analytics account if you click on "audience"->"demographics"

from haxe.org.

RE: Webmaster

You linked it for the old property but not for the new one.

from haxe.org.

@Merelleya I've switched to the new property, can't seem to be able to select two of them

from haxe.org.

@jasononeil I noticed that the download is handled through mod_tora, maybe we could serve the file directly and display a notification page as suggested ?

from haxe.org.

I've set this up, and I think I've added a "Downloaded Haxe version" goal in Google Analytics, though I'm not sure if it's working yet, maybe there is a delay on the data coming in? Or maybe I've set it up wrong.

I agree it could be good to craft some content for the "Downloading now" page. Perhaps installation instructions for each platform? For now I show the release notes and links to the documentation, manual and use case pages.

from haxe.org.

Keeping open until we actually check it's working :)

from haxe.org.

Google Analytics are a bit troublesome atm, because we have both haxe.org (which is actually old.haxe.org) and new.haxe.org. I'm seeing some goals in old haxe.org, but not on new. Maybe we should merge the two ? (a good part of our search traffic still gets redirected to old.haxe.org pages)

from haxe.org.

Can you try renaming the haxe.org property to old.haxe.org? I keep getting weird errors even when just resubmitting the form without changes.

from haxe.org.

Any update on this? The downloads are being recorded in google analytics now, so setting up goals etc sounds smart. I don't have access to the old sites analytics so can't make any changes there.

from haxe.org.

Back from holidays. I'm not sure actually what needs to be done and where.

from haxe.org.

The "download page" (that redirects to the .zip files etc) is now being
tracked in google analytics, so we can get some stats by manually finding
the relevant page in the "Behaviour" tab.

We can set up Google Analytics with "goals" so we can get some better
insights into the path people take on their way to eventually downloading -
I'm not an expert on what to track or what to look for though.

As for the "haxe.org" property and "new.haxe.org" / "old.haxe.org", I'm not
sure what needs to happen either, I can only see the "new.haxe.org"
property, and I don't know what actual issues it's causing for now.

On Sun, Jul 13, 2014 at 9:35 PM, Nicolas Cannasse [email protected]
wrote:

Back from holidays. I'm not sure actually what needs to be done and where.

—
Reply to this email directly or view it on GitHub
#20 (comment)
.

from haxe.org.

@Merelleya: Could you check this again?

from haxe.org.

We're working on cleaning up the mess in google right now. Current haxe.org will be renamed to old.haxe.org and new.haxe.org will become haxe.org.

@jasononeil: Could you find me on #haxe? @Merelleya wants to set up some tag manager things and we'll need you to make a small change to the site.

from haxe.org.

Sounds good.

I'm heading out for the night now but will try be online tomorrow / Sunday
/ Monday or whenever. Feel free to email me otherwise and I'll make any
changes tomorrow.
On 12/12/2014 6:18 PM, "Simon Krajewski" [email protected] wrote:

We're working on cleaning up the mess in google right now. Current
haxe.org will be renamed to old.haxe.org and new.haxe.org will become
haxe.org.

@jasononeil https://github.com/jasononeil: Could you find me on #haxe?
@Merelleya https://github.com/Merelleya wants to set up some tag
manager things and we'll need you to make a small change to the site.

—
Reply to this email directly or view it on GitHub
#20 (comment)
.

from haxe.org.

Hi there,

Here is the Tag Manager Code to be inserted directly after the opening body tag. Please also remove all other analytics-related code.

<!-- Google Tag Manager -->
<noscript><iframe src="//www.googletagmanager.com/ns.html?id=GTM-NXV3XR"
height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-NXV3XR');</script>
<!-- End Google Tag Manager -->

from haxe.org.

@ncannasse We still need to link the webmaster account to the analytics account. Would you mind seeing thet the haxe.org website in the webmaster tools gets linked to the haxe.org property in Analytics? (UA-30943311-2).

Thanks a lot!

from haxe.org.

On an unrelated note, try.haxe.org went down the moment I logged into google. I don't think that was my fault though. :)

from haxe.org.

@Merelleya I think i just did it, but you will have to confirm

from haxe.org.

@ncannasse I can confirm that you didn't get it right^^.

1.Log into your google Acc
2. go to analytics.google.com
3. go into the haxe.org property (either one of the 3 views test, live or backup will work)
4. on the very top of the page...click on "Admin"
5. Under the Porperty tab (the middle one) click on "All Products"
6. scroll to the bottom and click "link webmaster tools"
7. In the View that opens....at the very bottom click "edit" under the "link website"-section
8. If you see haxe.org in the list, choose that. IF not, you will have to add it to the webmaster tools account.
9. Go back to analytics, scroll up to "default view" and select the live view.
10. save.

I think that's it. Its kinda weird to explain remotely >.<

from haxe.org.

@Merelleya that was perfect, it seems to be maybe working now

from haxe.org.

@ncannasse You did it!!!!

from haxe.org.

The new analytics code is up.

@Merelleya is there anything more to do?

If not, feel free to close this issue ;)

from haxe.org.

@jasononeil I am very pleased to say that its working. I will set up events for the different downloads and such today and try to compile some useful reports.

@ncannasse Is there anything specific other than downloads that you would like to know about?

from haxe.org.

I think we could also measure the nigthlies.
@Merelleya, what's the code that should be added to each link?
We could probably get a more detailed report from Amazon, but all I can
find is the entire bandwidth used.
I'll take the opportunity and finally fix that annoying issue of the limit
of entries shown

from haxe.org.

Heya,

I can set up a new property in Analytics (so that the data isn't fed into the website data) and provide you with the tag manager code (similar to the one above) that would need to be added after the opening body tag. I can then set uo events in tag manager to "listen" to the clicks.

If that is not possible, we could use manual link taggin to trigger analytics hits like so:

https://support.google.com/analytics/answer/1037445?hl=en

As this is less flexible, I would prefer to do this via Tag Manager if at all possible.

from haxe.org.

This would be the appropriate Tag Manager code:

<!-- Google Tag Manager -->
<noscript><iframe src="//www.googletagmanager.com/ns.html?id=GTM-M4JZKD"
height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-M4JZKD');</script>
<!-- End Google Tag Manager -->

from haxe.org.

Thanks! I'll change it and let you know

from haxe.org.

Also, The tracking for the site downloads is up and the data should be fine from tomorrow onwards (there is testing data in today's event count that would need to be filtered).

I'll set up a custom report with the relevant info and maybe also a Dashboard. If you like I Can also schedule monthly reports by e-mail...The possibilities are endless.

from haxe.org.

@Merelleya, done! Can you check if it's working alright at http://hxbuilds.s3-website-us-east-1.amazonaws.com/builds/haxe/ ?
@ncannasse , can you update the build.haxe.org / builds.haxe.org website to point to the http://hxbuilds.s3-website-us-east-1.amazonaws.com/builds/haxe/index.html HTML?
I've changed to a static html which will solve a bunch of open issues about the builds

from haxe.org.

@waneck Heya! ITs not working yet. You need to put it after the opening body Tag. At the Moment you got it in the header.

from haxe.org.

@waneck: I've made the change in Indexer.hx, so you should just have to deploy it.

from haxe.org.

just to share the impact of a recent blogpost on a russian site...
according to nadako its a a quite widely read IT blog/site

from haxe.org.

here are the downloads generated:

from haxe.org.

Haha, wow... screenweaver.org is awesome!

from haxe.org.

If you pushed to hxbuilds, next builds will be correct then! Thanks!!
@ncannasse, can you upload the new index.html to build.haxe.org and
builds.haxe.org? Thanks!!

from haxe.org.

@waneck I did a redirection, it that correct ?

from haxe.org.

@waneck: Can you check the tag manager placing again? I see it in the body for the platform selection, but it's in the head for e.g. the windows-installer page.

from haxe.org.

Ooops, sorry about that. It's fixed now.
@ncannasse it's correct! Thanks!

from haxe.org.

It looks like everything works now, so we can finally close this issue. @Merelleya is going to keep an eye on the data so we can identify interesting events.

from haxe.org.