I'm currently working on a project where we've created a single-page website that contains a number of resources and information (including e-mails and external links to departmental sites, etc) - the site (page) will live on a USB which we will hand out to our customers over the summer.
Naturally, it'd be great to see if this campaign is successful by tracking whether or not folks are opening/using the USB site. My first thought was to alter all the out-going links to track folks via the Campaigns in Google Analytics; but since we do not own or have access to all of the various departments, this isn't an ideal solution.
My next thought was to add click events and track things that way - this would give us a nice snapshot of what folks viewing the USB were doing on it (provided they were connected to the internet at the time - we're not tremendously concerned with the accuracy of the stats, just a jist of usage). But since the site lives on a physical drive...and you can't set up a tracking account in GA without an address it seems this won't work.
My question is...is there a way around this? It almost seems like app tracking is a mix of what we need, but without being an actual app. Anyone have any advice?
Worse case scenario we just go with option 1 - best case scenario someone out there is more brilliant than I.
Related
Pls apologize if I'm not clear enough, i'll try to be as concise as possible.
I'm working on a a company that created it's own competitors, each has it own website, all share the same GA through GTM. Cross-domain tracking is implemented and working.
I want to know if users do actually visit these different sites, which is very likely because there is a lot of research before buying what this company offers.
I understand User Id's will not do the trick because I want to track them before visitors identify themselves through a form. There's no login.
Initially I thought I'll be able to create a segment to narrow down to users with more than one of this company's domains in their history, but that is not working. Should that do the trick?
Thanks.
In the view that get all data you have to create a segment to show users that visited first and second domain. If it is greater than 0 means the cross domain is set correctly.
For good implementation see Troubleshooting Cross-Domain Tracking in Google Analytics: https://www.google.com/amp/s/www.simoahava.com/amp/analytics/troubleshooting-cross-domain-tracking-in-google-analytics/
I'm very new to online analytics. I just deployed a site a few days ago, told no one, and Google Analytics is saying I have hundreds of users and sessions all over the world.
Even if events are logging from my own development, there shouldn't be so many users (and so many sessions...I'm not developing THAT vigorously.)
Also, my server logs indicate the level of activity I expect: ~0. So it's not like I'm magically getting traffic somehow. It really is nonexistent.
What could be going on? I can understand seeing a few sessions here and there, for web crawlers, but I don't understand why the numbers are so high.
Any common gotchas?
I realize this is a vague question, but I'm not sure what other information to provide, so please let me know what I can do to help.
Traffic source
First check, if traffic comes through your website (through your analytics.js library). To do this, just remove analytics.js for a while and check, if traffic is still going into Google Analytics (e.g. Realtime report).
If is still going, maybe somebody use Measurement Protocol to spam your account.
To prevent this, add, for instance, custom parameter into your call and create filtered view only for this. All without this param, throw away.
Check sessions and returning visitors
Check, if the traffic is random (usualy one pageview per session) or if the behavior of users is normal.
Custom client ID
Check if you dont play with client ID in analytics.js configuration. IF you dont have random number generator there.
Check traffic source (referal), browsers
If there is one significant, or there is some pattern in versioning (absolute randomness is pattern too)
Preventing random access through website
For every visitor who is first-time on your page, set up a cookie with current timestamp. If cookie is not older than e.g. hour or day, do not track this user. Or buffer hits and fire them later after you prove the user is real.
Anyway, if you have some new hints or information from your analysis, we should help you better. This is still like reading a magic sphere :-)
We have been using Google analytics for awhile now. It has been great for both live traffic and historical reporting.
Suddenly on Sept 5 our reporting shows zero traffic (using the standard reporting overview tab).
This seems really strange as you can see there is near constant traffic in the real-time tab.
Has anybody else experienced this problem when integrating Google analytics? We had a filter that only traffic from our main domain (app.domain.com) would show. Even after removing this we get nothing in the reports.
Check the filters on that profile. Go into Admin on the top right and check the Filters tab on the profile.
Filters are not applied to real time data.
So what you're seeing here is data being filtered out from the profile, but still showing up in the real time.
This could be a few different things
A temporary glitch by Google - this happened to me (which is how I got to this page). I could see traffic in the real time view but nothing in reports. To fix: be patient - this resolved itself after about 12 hours.
profile issue - you may have a profile set up that has filters which are blocking more traffic than you were expecting. To fix: Try setting up a separate profile (if you don't have one already) that has no filters applied. Remember- profile filters work by stripping or manipulating traffic before they reach your reports. The answer above is incorrect- the real time view does take filters in to account. You can easily test this making a filter change and you'll see it take affect in the real time view
tag has dropped off your pages To fix: if you're using GTM you should be able to check this. Or if not check HTML page source on one of your pages you know is getting traffic
finally - you may not getting any traffic :)
I'm using both on a site and getting very different numbers from each. Why is this?
The discrepancy is also mentioned in a Quora answer (Which is better, Facebook Insights or Google Analytics?)
Footnote: if you decide to use both, do not report them side-by-side,
and never expect them to match. Trying to explain the differences will
drive you mad.
Could someone explain?
This problem is quite common, and very hard to explain to clients why numbers do not reconcile amongst different analytics platforms.
Firstly, I believe that because there are remote connections to google or facebook some user sessions will get lost (What happens when they hit stop on the Browser page before the .js downloads for instance).
Secondly I believe ad blocking software may stop the file from being downloaded therefore the session is not captured.
Most hosting providers will have their own analytics platform with your hosting package. This is what I rely on as a true indicator for actual page views etc. These are usually generated directly from your web server logs so they are more accurate. Sadly I've never seen one of these packages have as many features as google or facebook.
There are tons of possible reasons. They might identify returning visitors in a different way or users might block scripts from a specific domain (e.g. *.facebook.com but not *.google.com). In general, ignore the discrepancy. Just pick one solution and use it. You'll always have visitors blocking all such scripts or just one or two specific trackers. The only (almost) 100% accurate way to do it, would be using local scripts, but even those could be blocked. You could as well look at open source solutions such as Piwik
Different web analytics products use diferent methods to track data on the site.
These differences between them is the reason why is hard do do a side-by-side comparison.
On the two links bellow you can find more info about that:
Why does Google Analytics report different values than some other web analytics solutions?
Using Google Analytics & Facebook Domain Insights to Track Social Actions on Your Website
In addition to the notes above, I also wanted to mention Google samples data when there are large volumes & dimensions. This may be a contributing factor.
Facebook reports on clicks and Analytics reports on pageviews.
The amount of pageviews might be less than the amount of clicks for a number of reasons:
There are filters on your Analytics that are blocking the pageviews from being recorded
The user left the page before the Analytics code could be recorded
Or the ads being clicked by bots and the Analytics isnt recording them
This seems to be a big problem with Facebook ads. I run a number of campaigns with facebook and I only see 30-50% of the reported traffic actually make it to the site. I cant believe this is due to only the first two reasons.
I have gone into more details on my blog http://www.bradtollefsen.com/facebook-ads-adding/
I have a web app that I deployed in AppHarbor with Google Analytics. Development is still ongoing and I test it very often live to checkout for example stuffs I did with the CSS, etc.
Everything is working fine but I'd like to know how many times I am accessing the website apart from the rest of the visitors who visits it. When checking the reports in Google Analytics it only shows me the ISPs of the visitors. I'll need something more drilled down like an IP address, but this seems to go against Google Analytic's policy and I do not know if this is even possible still.
Like right now I have 72 visits. But I have been testing so a lot of those could just be me. Would be good to know the actual visitor count.
I know this is probably a little late but you can set a filter to ingore your own traffic from reports. Here is how you do it.
In addition for adding a deprecated variable and using filters, you can build the code so that it only prints the tracking code if e.g. an identifier cookie is not found. Other common option is a URL parameter.
You can then set this cookie for your browser and be excluded from traffic.