I'm currently adding some tracking in my app with the Measurement Protocol. When I use it in dev/staging, it works like a charm, however when I am targeting production, it doesn't work anymore.
I've already try a bunch of tests and I know for sure that the problem isn't in my code: When I test with my old id (UA-xxx-1) it doesn't work, but when I create a new app (UA-xxx-2) it does work.
That's why I suspect I may have misconfigured something on the Google Analytics side.
Does anyone has an idea about what it could be?
I don't want to use a new web property since I already have a large amount historic data in the old one.
I've finally found the origin of the missing data: I had an old filter removing all the requests without Browser Size filled in.
Thx for the help.
Related
I have this project where I need to know if a visitor legitimately arrived from a QR code. Document.referrer value from a QR code shows blank. I have looked at some answers suggesting to put parameter in the query string (e.g. ?source=qr), but anyone could easily add the parameter into the URL and my code would believe it is from a QR code (e.g. www.project.com/check.page?source=qr) . I have thought of adding codes to make sure it is from a mobile phone / tablet as secondary way to authenticate but many browsers have add-ons to fool websites.
Any suggestions would be greatly appreciated.
Thanks in advance.
I think the best solution for you is creating your regional QR Codes pointing to:
Region 1) http://example.com/?qr=f61060194c9c6763bb63385782aa216f
Region 2) http://example.com/?qr=731417b947aa548528344fab8e0f29b6
Region 3) http://example.com/?qr=df189e7f7c8b89edd05ccc6aec36c36d
if the value of the parameter qr is anything other than f61060194c9c6763bb63385782aa216f, 731417b947aa548528344fab8e0f29b6 or df189e7f7c8b89edd05ccc6aec36c36d, then you can ignore it and assume the user didn't come from any QR Code.
Of course, any user can remove the source parameter. But at least he can't add a valid one, unless he really had access to the code.
...but anyone could easily add the parameter into the URL and my code would believe it is from a QR code
Well, anyone could also scan the QR code, view the link, and remove the source=qr from it.
Data collection is never 100% reliable. Users can change their browser's user agent, inject cookies with some strange values, open your page through a proxy server, and so on.
You could create your own device or App for scanning the QR-code. If you read the post I've linked, you will see that this is a waste of time and resources.
So, what is left is to make a solution which will work for most of the users. Appending a source=qr parameter to your URL seems to be the simplest solution. You could also link to an entirely different domain and redirect the request, so it would be more fraud-safe. But it will never be 100% accurate.
Goolge very kindly offer a sample dataset of Google Analytics data in BigQuery, so you can run some tests before setting up the actual export to BigQuery.
This is detailed at the following page https://support.google.com/analytics/answer/3416091?hl=en&ref_topic=3416089
However when you try to add the project google.com:analytics-bigquery as shown in step 5 of the guide. The following error is shown:
Project IDs may contain letters, numbers, and dashes, with an optional
"domain:" prefix.
As you can see the project ID conforms to this, but you are unable to submit the form.
Google is this just a bug?
Does anyone else have the same issue?
I am confirming - just tried and got the same.
Some-when recently - this dialog form was changed (added options to choose from - display in nav vs. make a current project) and looks like the bug was introduced. previous versions didn't have this bug.
At the same time - confirming that nothing wrong with project name itself - with the internal tool that I am using - I was able to add this project successfully
You should report this bug in BigQuery issue tracker.
Thanks for reporting this issue. We actually already have a fix checked in for this, but we are currently waiting for an opportunity to push this to production, hopefully soon.
In the meantime, you can try one of these workarounds:
navigate directly to the project: https://bigquery.cloud.google.com/queries/<project_id>
navigate to a dataset on the project, which will display it in the left nav: https://bigquery.cloud.google.com/dataset/<project_id>:<dataset_id>
When initially evaluating Apigee it was showing pretty up-to-date analytic numbers on the API Proxy dashboard. Now that we're doing a trial run in production (and hitting it hard), the dashboard shows all zeros.
When I set up traces for the proxies, there is definitely traffic coming through.
Please help! Thanks! Organization:verba
Two things -- first, make sure you're looking at the right environment. The dashboard reports have a dropdown menu in the upper right hand corner for prod or test. By default your work gets deployed to"test" (yourorg-test.apigee.net) but it seems to switch sometimes from test to prod without specifically being set.
The other thing is that Analytics often take longer to get processed and show up in the free Developer product (which I assume you're using to evaluate Apigee). It's a multi-tenant environment which a huge amount of data that's being digested before being available in the reports.
Hope that helps
Sorry for the inconvenience. We have fixed the issue. Would you please check the reports and let us know if the reports are generated.
I used step by step instruction here :
https://developers.google.com/analytics/devguides/collection/ios/v2/#initialize
But still my hit is not being recorded. I can see in the debugging window its say something about dispatching number and start tracking again.
My another concern it what they assigned to tracker and then never used it.
Am I missing something. Someone please shed some light.
I have looked over the internet, there are all old and referring to old google analytics library which is having only two files. GANTracker.h and libGoogleAnalytics.a
New library got bunch of files hence the way they have implemented.
Code is pretty straight forward I dont know what it is not tracking the hits.
And Yes I have created tracking ID and I am familiar with the Google Analytics as I used it in past to track my websites and blogs.
I would appreciate if someone can give me some right pointers. Thanks.
As log window was having quite a lot info I have created a "paste"
http://pastie.org/7468881
I'm looking for a portlet like-solution that would collect and report usage analytics in Liferay... but google analytics is not an option, unfortunately.
Stats by community, group, session tracking, apart from the usual bounce and exit rates, referrals, origin, etc. I know I'm kind of asking the reinvention of the wheel, but there are plenty of usage data that can be collected by Liferay that google can't. I've already checked PiWik, and it looks very impressive.
Any suggestions? TIA,
As of 2015 there is Audience Targeting plugin, which (at least for Liferay 6.2) comes bundled with analytics-api / analytics-hook modules, which collect some useful analytics data. Mind now:
So far it doesn't look like there is any standalone use for them as they were introduced, I believe, to enable the content visited, page visited and other such rules in the Audience Targeting itself; you can't see the raw events in any of the provided portlets
The events are stored as rows in a SQL database, so I would be concerned about it's performance in the long run (with thousands of clicks every minute etc.), although I say this purely theoretically as I haven't done any tests myself nor checked if there are some performance enhancing measures implemented
What you can do, however, is to put together your own portlet which would create some graphs etc. based on the data stored in CT_Analytics_AnalyticsEvent table.
Right now, I dont think there is any out of the box feature available for this, you might need to create this. There can be 2 things
1) You need to create a javascript library if you need realtime/web analysis (this is same like creating google analytics lib)
2) This option is quite easy. Liferay stores everything in db, you can have a report portlet which will show the report based on the data. We did this for one project where we were tracking the session ids/ip and logged in user details for portlets.
To achieve point 2) you can create new Liferay service, which will be used to store these data and retrieve.
Hope this helps
You already mention Piwik, which is similar to google analytics. You probably have your own theme (almost everybody changes the appearance to look like their own site) and it's quite appropriate to place the relevant piwik-stats-snippet in there.
You can also, as Felix suggests, mine your log files. Liferay stores some data, your webserver access logs also are quite worth to mine. And, of course, you can change your theme to log even more for every page access, just take care that you don't create a performance bottleneck by writing too much during one page request.
So, coming back to your question: Built-in like google analytics: No. Easily integrateable (like Piwik): Yes, of course. Completely customizeable: Yes, of course.
Edit: It just happens that David has created and documented an integration that makes using Piwik even easier