Skip to content

Comment on Goodbye Google Analytics. Hello Piwikparent

Comments

Full Disclosure: I am a Piwik Dev

Whenever Piwik gets slow you will have to setup cron archiving: http://piwik.org/docs/setup-auto-archiving/

By default, Piwik will aggregate data when you a) make an API request - b) Load the dashboard (which in fact calls the API). Cron archiving makes this process faster by processing all the data beforehand so that the API can simply request it from the DB.

I just want to mention that Cron archiving really does wonders for performance.

I've got a site that is receiving nearly 10,000 daily uniques since Google's last [panda|penguin|whatever] update in May, and while Piwik's performance was not terrible, setting up the cron a few weeks ago made the whole experience very snappy.

Thank you for your work halfdan!

Apologize for hijacking the thread. I am trying to convince one of my clients to do exactly this. Switch from GA to Piwik for their site which is deployed on Adobe CQ5. I know I can use client side tracking easily (hence my recommendation). However, do you know if there is support for server side CQ5 logs?

I'm tracking sites by loading their Apache access logs into the database. I'm not sure what's CQ5 logs structure is, but it should be possible (tho it might require some modifications).

See here: http://piwik.org/log-analytics/how-to/

Edit: It should be noted that you will get lots of bots requests showing up when you load access logs (the regular tracker relies on javascript, which gets rid of most of the bots). I have a small awk script that cleans the access logs prior to importing them, by trying to detect bots. I can upload that if you're interested.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.